Re: wow, this actually works!
Re: wow, this actually works!
- Subject: Re: wow, this actually works!
- From: Scott Ruda <email@hidden>
- Date: Wed, 29 May 2002 23:20:17 -0700
On Wednesday, May 29, 2002, at 10:07 PM, Kenneth Welch
<email@hidden> wrote:
Actually, my experience has been that any and every call that is either
MIDISetup.RestartMIDISystem, getDevice, getEntity, getDestination,
getNumberOfSources, getNumberOfDestinations -- basically anything that
has to query the hardware -- needs to be run from the separate thread
every time you want to use it. Whereas .send(packetlist) and so on
always work fine from the app's normal threads regardless
Yes, my confirmed experience also. Unfortunately (?), my calls to MIDI
services are spread around quite a bit in 'nicely' encapsulated narrowly
focused objects and not just done all at once inline in one 'initter'
object at startup time. There are user choices that have to be allowed
dynamically etc. Sounds like to do this right I might have to create a
helper thread (maybe a SwingWorker.invokeLater type interface...).
Bill - did you mean to imply in a previous post that a fix for this
might not get into the final Jaguar release? I've got the Jaguar
pre-release ADC CDs now, but I haven't gotten a chance to test this out
yet. I'd probably only go through the extra work of creating a formal
workaround if it was needed for real customers. My ship date for the
next version of our product (www.emu.com/support/eloader.html) is 'late
summer', so Jaguar might be out in time for my customers. I can handle
developing with the 'mouse-wiggling' workaround. But if you think I may
need to, I'll code in a real workaround that I could ship if I had to.
(Obviously you can choose to make no commitments ;-)
Scott
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.