Re: coreaudio-api digest, Vol 2 #139 - 4 msgs
Re: coreaudio-api digest, Vol 2 #139 - 4 msgs
- Subject: Re: coreaudio-api digest, Vol 2 #139 - 4 msgs
- From: Joshua Strickon <email@hidden>
- Date: Mon, 27 May 2002 21:08:01 -0400
On 5/27/02 3:00 PM, "Scott Ruda" <email@hidden> wrote:
>
On Sunday, May 26, 2002, at 10:05 PM, coreaudio-api-
>
email@hidden wrote:
>
>
> simply moving the
>
> mouse after it hangs is sufficient to kickstart it (at least on my
>
> system).
>
>
Wow, this actually worked! I'm using CodeWarrior, not PB. But if I
>
wiggle the mouse during application startup, it all works! In fact,
>
wiggling the mouse seems to make the whole app start, and even quit
>
faster! I'd never actually release the code this was to my customers,
>
but at least it has allowed me to finish my port and test my code.
>
Thanks!
>
>
> First, the static method MIDIData.newMIDINoteMessage() does not work. I
>
> could not get MIDI Monitor to detect any NoteOn/Off outgoing packets
>
> when I had my app trying to create them with this call. Use
>
> newMIDIRawData() instead.
>
>
I am always using newMIDIRawData, since the write through to the OS is
>
abstracted into the lowest levels of my transport code and doesn't
>
'know' what message it is writing at that level. But thanks for that
>
warning.
>
>
I do seem to get corrupt incoming packets sometimes. It seems the status
>
bytes sometime come in wrong (I get 0x90 status when I should be
>
receiving 0xF0 status). Hopefully this will be resolved by the new
>
release also.
>
>
Plus the MIDISport drivers available on the MIDIMan website are still
>
spitting out Debug Messages galore to the Console. I hope MIDIMan posts
>
some new drivers before the next round of Apple Java updates get to my
>
customers.
>
>
>
> From: Bill Stewart <email@hidden>
>
>
>
> These are some known problems with the Java VM on 10.1
>
>
>
> There is an update available for Java (that also includes an updated
>
> CAJava)
>
> to work around these problems - you should definitely be running with
>
> that
>
> Java update
>
>
I don't think that update is up on the seed server. at least not for my
>
ADC Select Membership status. Maybe it will be on the next seed CD that
>
is apparently on the way. (I hear baby cats are being sent in the mail
>
too! ;-)
>
>
Thanks all,
>
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.
>
I have been having similar problems with this through jni. I am writing my
gui in java but using coreaudio and midi natively through jni. The data
never even makes it into java as part of my application. I keep that all
separate. The illegal monitor exception has to do with the CarbonLock. It
seems that java is doing some nasty stuff once you bring up a window. The
trick that got everything to work was to put any native routine that opens
or closes a midi port into a new thread. I am not sure why the carbonlock
should effect coremidi, but it does. The problems go beyond core midi and
core audio and even include creating sockets in a jni library. Hopefully
some of the threadlocking issues will be cleared up in future releases.
-Josh
_______________________________________________
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.