just wanted to send this to the list too, like i should in the first  
place (i am subscribed now).
jan

Begin forwarded message:

> From: Jane <[EMAIL PROTECTED]>
> Date: 19. Oktober 2008 23:01:37 MESZ
> To: Roger Dannenberg <[EMAIL PROTECTED]>
> Subject: Re: [Media_api] different midi responses for linux and mac
>
> hey roger,
>
> i did the loopback test in the same way you did:
>
> MIDI input devices:
> 0: CoreMIDI, E-MU XMidi1X1  Midi In
> Type input device number: 0
> Midi Monitor ready.
> F07E4C06 System Exclusive
> 02180000 System Exclusive
> 04040500 System Exclusive
> 00322E00 System Exclusive
> 3236F7 System Exclusive
>
> ...and i get the same result as i get in my application on the real  
> module. the XMidi1X1 its plug&play on every platform, no drivers  
> needed at all. pretty neat and works well in linux.
>
> i also ran the loopback test and i get only errors:
>
> Sending 399 byte sysex message.
> Error at byte 6: sent 6 recd 0
> received 531 byte sysex message.
> Sending 115 byte sysex message.
> Error at byte 6: sent 6 recd 0
> ...and so on
>
> most likely there have been some changes in osx 10.5.5, which runs  
> on my macbook (early 2008, the one before the current)!?
>
> whats next? thanks a lot,
> jan
>
>
> On 19.10.2008, at 20:48, Roger Dannenberg wrote:
>
>>  I tried to reproduce your error and couldn't. Here's what I did:
>> 1) create a file with the sysex message:
>> F0 7E 4C 6 2 18 4 4 5 0 32 2E 32 36 F7
>> 2) run pm_test/mm to monitor input
>> 3) run pm_test/sysex
>> Use send (s) to send the file
>> 4) look at the data printed by pm_test/mm:
>> F07E4C06 System Exclusive
>> 02180404 System Exclusive
>> 0500322E System Exclusive
>> 3236F7 System Exclusive
>>
>> I tried over the IAC Driver Bus and through a loop out and back  
>> into a USB MIDISport 2x2, and also sending with 0 latency and non- 
>> zero latency. It is still possible that some other driver is  
>> forming packets in a different way and PortMidi is not interpreting  
>> them correctly. Can you try this loop-back test on your hardware?  
>> You could also run pm_test/mm to receive the Proteus sysex message  
>> to make sure that at least 2 programs (yours and pm_test/mm) agree  
>> on what data is actually delivered by PortMidi. I'm running OS  
>> 10.4.11 on a MacBook Pro.
>
> Durch Pubertät zum Erfolg






_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api

Reply via email to