|
|
MIDI note follower Hi, using KnM Midi note follower plugin in my app, i occasionally run through this problem: " Initialization Failed" and lead to the comp no starting at all (black screen). see attached console snapshot. (- sorry i just noticed my snap is kind of "obstructed" , but relevant info is still visible) It is very difficult to reproduce this bug, as it happens really once in a while. Is there any workaround ? Is this a bug - or a problem maybe with my computer - ? thanks for your patience.
|
Interesting... from the source code, that doesn't seem possible. init can't fail unless it's out of memory, but it's allocated a pointer already from the log line, so that's not it. setup can't fail because it ends with "return YES;", so that can't fail...
I'll try to check this out, but nothing obvious is jumping out at me :/
to me it seemed like the same issue that hit Spooky 0.1 - as discovered by Toby -
I just realized that we haven't had an update to midi tools since feb 2008 (over a year!) -- it's possible that our internal build fixed that a while ago, but it never made it into an update.
I've spent a bit today doing some cleanup/modernization of MIDI Tools, and released a beta. Please let me know if this fixes the problem (and if it introduces any others -- I don't have an MIDI gear handy, so I couldn't do any meaningful testing).
Will try out beta this weekend. Cool thanks!!! Kineme rox!
Just curious, did you do anything along the lines of: hold note gate til the next frame?
Is for quick-release drum pads that send note-on/note-off so quick (between frames) that QC triggers based on midi-note changing/gating were sometimes (mostly) getting lost. just curious
thanx again!!!! jd
unfortunately, we haven't added any latching yet :(
thank you very much Chris. I'll test that and report if anything goes wrong.
Hi, it's been a while since anyone looked into the MidiTools patch I guess.
I am experience something strange with the Global Midi Note Follower. It looks like the higher a followed channel # is, the more it gets prioritized and shadows out any previous channel #.
e.g. only channel 3 plays every beat -> gets detected. additional channel 5 plays every 4th beat -> channel 3 is not recognized every 4th beat.
Seems like all the "note on/note off" values overlap and only the latter channel comes through. I am experiencing this with the new electribe 2 and QC running in 32bit on Mavericks (MIDITools version from 2009)
Any ideas on how to solve this?