I think the "correct" thing for MIDI applications is to close the port
when not playing or recording.
One way to work around this might be to use a third-party virtual MIDI
device driver such as MIDI Yoke and MIDI Ox. I think you can have your
applications open separate virtual devices and merge these into a single
physical/hardware port. -Roger
Jane wrote:
hehe, can this "feature" *bows down* somehow be disabled? the thing
is, my application (sysex editor for a synth) really is no fun when
you are unable to use it together with a sequencer application like
cubase... :>
On 06.11.2008, at 18:02, Roger Dannenberg wrote:
This is a "feature" of Windows. -Roger
Jane wrote:
hello,
using portmidi in windows i cannot open a device that is in use by
cubase. OTOH, when i first start my application and then cubase,
cubase cannot send on that device (device is still listed though
and i get no error. it seems like cubase beliefs that it is
sending on that device but the synth doesnt receive any note
events). so, either way, once the device has been opened it seems
to be blocked for other applications.
i dont have this problem in linux where a sequencer and my
application can use the same device.
any ideas? ty, jane
_______________________________________________
media_api mailing list
media_api@create.ucsb.edu
http://lists.create.ucsb.edu/mailman/listinfo/media_api
_______________________________________________
media_api mailing list
media_api@create.ucsb.edu
http://lists.create.ucsb.edu/mailman/listinfo/media_api
