I want to start taking advantage of the many free patches out there. That is why Midi-Ox is very attractive as a tool to load third party sysex files.
#Midi patchbay pci upgrade
An upgrade to their XL version (pricey) allows for file importing as well as file conversion to. I am running MidiQuest 9, which unfortunately doesn't allow to import or open generic sysex files. "why not just use MIDI Quest to do SysEx sends and dumps?" Is this using the exact same hardware as MIDI-OX?" "it is interesting that MIDI Quest seems to work properly. If you are unwilling/unable to re-cable to troubleshoot, then there is little else I can offer. Is this using the exact same hardware as MIDI-OX? If so, why not just use MIDI Quest to do SysEx sends and dumps? If not, try attaching MIDI-OX to that hardware. SysEx takes a very different form from standard MIDI messages, so it probably matters not that 'everything else' is working although it is interesting that MIDI Quest seems to work properly. I was trying to help you figure out why your SysEx sends are failing. I wasn't suggesting it as a permanent solution. Post by Jamie OConnell on Feb 6 th, 2008, 3:03pm However, if Midi-OX has an issue with my patchbay, then the patchbay stays and Midi-Ox goes!! ) The keyboard also repsonds to Cubase as always so I am very confident that the patchbay is not interfering with data. BTW, just to remind myself that everything is indeed working as should, I did some quick sysex dumps to and from the keyboard using MidiQuest and all is working as should. I am exploring other settings in the meantime. I think this is nothing more then a "handshake" problem between Midi-Ox and the Roland D50. Having said that, all other programs are working correctly including Cubase, SoundQuest Patch/Librarian and a number of midi utilities, all of which go through the patchbay. My studio is a turnkey operation and moving cables around is not easily done. I anticipated your suggestion regarding the patchbay. "try taking the Patchbay out of the equation. Check that the data received matches the data sent. If it still doesn't work, try making a hardware loopback with the MIDI Sport and send SysEx from One MIDI-OX instance to another. Post by Jamie OConnell on Feb 5 th, 2008, 12:25pmĪ useful experiment to determine the solution might be to make the System as simple as possible: try taking the Patchbay out of the equation. Midi routing through Roland A-880 Midi Patchbay. MidiSport 2X2 USB Interface at the computer. What type (Brand, Model) of MIDI Interface are you using? Is it USB or PCI or Serial? Post by Jamie OConnell on Feb 4 th, 2008, 5:12pm I have tried dozens of different buffer/delay settings with no luck. Try increasing the delay times more, although you probably shouldn't have to go above 120 milliseconds.
Post by Jamie OConnell on Feb 2 nd, 2008, 5:15pm Title: Re: Sys-Ex loads not working.almost there. Can anyone take me through the usual commands used when sending Sys-Ex files to a device? TIA
I have tried lowering buffers and raising delay times to no avail. OK" When you click OK, the window disappears and you are back to where you started. Wait until the data has been transmitted and try again. When trying to send a sys-ex file to any of my keyboards, the load begins, then stops after a moment with the error message: "SysEx Output Devices: The port is transmitting data to the device. Midi-Ox is connecting with keyboards in the studio as I can see data appearing at the midi out ports, my DX7 for example responds (but without success) when sending sys-ex loads and the Roland D50 doesn't respond at all.
#Midi patchbay pci pro
I'm a newbie with Midi-Ox, running V7.O on a XP Pro Computer. Title: Sys-Ex loads not working.almost there. (Message started by: tonyg on Jan 31 st, 2008, 7:45pm) MIDI-OX > Questions and Discussion > Sys-Ex loads not working.almost there. MIDI-OX User Forum - Print Page MIDI-OX User Forum ()
0 kommentar(er)
