If you verify this step works - let me know and we can go onto to the next step. If they are - you sending device is sending it correctly and logic is receiving it correctly.
#Snoize sysex librarian software
Let's first verify that Logic is in fact receiving the sysex correctly and there is data integrity from the sending device to Logic itself.ġ/ create a new project and add 1 software instrument track.Ģ/ Set the track header to to "No Output" - this is very important as it will ensure there is no midi thru and the sysex data is not being echoed or sent back to the sending device or for that matter any device.ģ/ make sure the track header is selected (there is no record enable button)ĥ/ go to the device which is sending the sysex dump and execute it - so that logic records the sysex.Ħ/ when done press stop, open the even list and examine the sysex's ( are they intact and appear to look correct). Why can't Logic handle SYSEX Thru in cases like this? It should be able to act as a hub for an entire system and handle whatever is sent to it in accordance with the MIDI you want to know for sure what it going on - you need to break this down into a few discrete steps and confirm each step is working.
#Snoize sysex librarian drivers
I suspected the Unitor-8 drivers but they are okay as there is no problem when using the utility program MIDIPATCHBAY to do the routing. I have also tested this on Logic 9 and it is the same problem there. You can plainly see that the messages are filled with incorrect 7F's and invalid data.
0 kommentar(er)
