Closed txus closed 13 years ago
Hi,
Thank you! I hadn't seen niki before but it looks great. I'll post it around. I actually have started something similar (but different)
Unfortunately, I don't have a computer with Lion yet. although I might get one soon.
Do you have any way of testing without IAC, just using standard MIDI output? Just trying to isolate the issue
I'll do some research...
Yeah, I don't see any posts or anything about changes to IAC or coremidi in Lion.
Technically, it can be your MIDI setup since Unimidi and Archaeopteryx don't share configuration. In other words, you may have made a mistake setting up Unimidi on your laptop but not Archaeopteryx. That said, please just confirm that this isn't the case before we go further
If that's not it, and you can, test to see if regular hardware MIDI output works without IAC.
If you're not familiar already...
You can use MIDIMonitor to "watch" the outputs instead of having to hook up a synth or something like that http://www.snoize.com/MIDIMonitor/
MIDIMonitor is a nifty tool! I'll take a look tomorrow and see what I discover :) I'll keep you posted!
Yeah, let's see what you find. I'd like to avoid the trouble of tracking down a Lion setup if at all possible :)
Thank you much for your help
Confirmed as of today, in Lion, MIDIMonitor seems not to track anything with Unimidi, but it does with Arx(archaeopteryx) :S And in Snow Leopard, everything fine. So frustrating! This is hard to debug, but I can help, having the two machines (snow leopard at work and lion on laptop).
So, whatever log dumps/stuff you want me to do, I'm happy to do it! After all I can't really develop niki on my laptop without listening to the songs! hehe together we'll hunt this bug down.
This test was doing direct output without IAC?
Unfortunately no, I haven't got my soundcard with real midi inputs/outputs with me and can test only with the virtual devices :/
Any chance that you could make that happen at some point? I can try and walk you through debugging but I think it would be better not using IAC to debug without first ruling out that it's contributing to the issue. It may just create a ton of work in the wrong direction. But if that's the best option available, I guess it will have to do
I'm trying to find a friend who has Lion installed...everyone who I've asked so far is sticking with 10.6.
If you don't mind, try testing again now with the newest versions of unimidi and ffi-coremidi. I don't yet have Lion, but I did make a bunch of other bug fixes that could have subsequently fixed this
Unfortunately it doesn't work with the newest versions either...
Ah, ok. Well, thank you for trying. I will get my hands on a Lion laptop in the next few weeks and update here when I have it working.
I have the Lion setup now. I am seeing the same behavior. Strangely, sysex messages work but short ones don't. Will let you know when I have a fix ready
Well, good that you could reproduce! That means it's solvable :) Really appreciate your effort, thanks!
No problem!
Should be fixed. update both your unimidi and ffi-coremidi gems
Hi Ari!
I'm the author of niki, a DSL to write songs, which from v0.1.0 depends on Unimidi rather than Archaeopteryx. First of all, congratulations for such a great gem! And of course the FFI gems you wrote for it to work :)
Just a heads up, today I tested my gem with unimidi in a Snow Leopard machine, worked flawlessly. Now I'm on my laptop (which has Lion) and apparently the messages get sent (no error or anything), but my host program (Reason) doesn't seem to receive anything through IAC.
If I change to my gem version prior to 0.1.0, using Archaeopteryx, the IAC driver works as expected, so it can't be my midi configuration :S. In the Snow Leopard machine, it works both with Archaeopteryx and Unimidi without problem.
Do you have any machine with Lion to confirm this is not only happening in my laptop?