search

arirusso / unimidi

Realtime MIDI IO for Ruby
Other
255 stars 27 forks source link

No input using IAC on OS X 10.6 #4

Closed tomekwojcik closed 13 years ago

tomekwojcik commented 13 years ago

Hi, I've been playing around with UniMIDI and encountered a problem. UniMIDI doesn't receive messages on input.

My setup is:

  1. MidiPipe for routing and monitoring MIDI events (also checked with MIDI Patchbay),
  2. Cubase LE 5 for clock source and synthesis :),
  3. Mac OS X 10.6.8,
  4. UniMIDI 0.2.1,
  5. Ruby 1.9.2p290.

MidiPipe shows incoming events and when I hooked up Garage Band to the virtual input it was receiving messages sent from Cubase (in other words - both Cubase and GB played the same notes simultaneously), so I guess everything's OK with my setup, however UniMIDI inputs don't receive those events.

I'll be thankful for any advice.

arirusso commented 13 years ago

Hi, I won't have a mac setup until tomorrow but I'll do some tests then.

One thing that I noticed when testing IAC was that you could only use the first virtual input in MIDI patch pay. Were you doing that?

Is there any way you can test without using MidiPipe/Midi Patch Bay, for instance just using a MIDI cable connecting your hardware MIDI input and output?

tomekwojcik commented 13 years ago

Hi, I was trying to use the first (and only for that matter) virtual input defined in MIDI Patch Bay or MidiPipe but nothing worked.

I haven't got the idea of connecting my audio interface's MIDI IN with OUT :). Guess I'll try just that and see if it works. If I understand correctly I won't have to mess around with MidiPipe/MIDI Patch Bay, right? Also (just for the record) I tried creating a patch in MIDI Patch Bay for my card's MIDI (pretty much the same way I'd do that for IAC) ports but it didn't work either.

Thanks for info and have a good day.

arirusso commented 13 years ago

Yeah, I'm thinking that by using the MIDI cable between your interface's IN and OUT, we will temporarily remove IAC (MIDI Patch Bay / MIDIPipe) from the equation, ruling it out as part of the problem... assuming the problem still occurs.

I will have a 10.6.7 setup that I can work with tonight to try and get it figured out.

Thanks for reporting this

arirusso commented 13 years ago

OK, the MIDI cable method worked for me but there was some strangeness with IAC. I believe I found the bug. It's actually in this library

http://github.com/arirusso/ffi-coremidi

Should have a fix sometime this week

Thank you again

tomekwojcik commented 13 years ago

OK, thanks for your support. I'm currently unable to play with the Ruby MIDI thingie due to other responsibilities.

Anyways, I'm watching ffi-coremidi repo so I don't miss any changes in it.

Thanks a lot for your work on those gems.

arirusso commented 13 years ago

There's never enough time for music, is there? :) I'll ping this thread as well when the fix is in place.

arirusso commented 13 years ago

Give it a try now. You'll need to update both unimidi and ffi-coremidi.

You should now see IAC devices listed for all of the ones in MIDI Patch Bay/ MIDIPipe

If you don't, one thing you can try is enabling the IAC device in your Audio/MIDI Setup utility application. (select IAC and do "get info" then check "online")

tomekwojcik commented 13 years ago

Works like a charm. My Ruby sequencer is now fully sync with Cubase :).

Thanks a lot for your support.

I think we can close the issue.

arirusso commented 13 years ago

No problem. Would love to see the sequencer!