Author |
Topic: Sysex problem on beta (Read 3100 times) |
|
Viccot
New Member

 MIDI-OX Rules!

Gender: 
Posts: 1
|
 |
Sysex problem on beta
« on: Oct 11th, 2010, 2:22pm » |
Quote Modify
|
I have just downloaded and installed version 7.0.2.372. I have successfully taken a memory dump from my electronic organ to a sysex file using the sysex view but when I attempt to use: File/Send sysexfile I get the sending indicator but the organ does not receive data. I have to go into Midi Devices, highlight the Output,open up system and highlight sysex. Then do the send and the organ then recognises the input. When I first set this up I coupled the MIDI OX events to the Output port and it worked, but it will not work a second time without going through the above procedure SYX is on, Memory buffers set to 16x2048 Is there a problem or is it meant to be this way?
|
|
IP Logged |
|
|
|
Lynn4510
New Member

 MIDI-OX Rules!
Gender: 
Posts: 1
|
 |
Re: Sysex problem on beta
« Reply #1 on: Mar 29th, 2011, 9:38pm » |
Quote Modify
|
I have the same bug: MidiOx will not pass SysEx again. On the same Ver. but not Beta (not identefied as such when I downloaded and installed again today) After a couple of days of joyfully passing sysex (GS reset-sent by my midi file player) to my synth, Now curiosly, MidiOx Will Not Pass Sysex. -Any more. Yes, have enabled: Options > Pass SysEx. Uninstalled/Reinstalled MidiYoke&MidiOx with same results. Have set Midi file player Output port to bypass MidiOx then my player App>PC>USBMidiport>Synth will Pass SysEx, no problem; my player will reset my synth. I can successfully send that GS reset via the MidiOx Send SysEx Window or the Menu command. Rebooting PC/Closing/Reopening MidiOx yealds no change. It Maps Correctly to controller msgs. sent in Hex as sysex data in a translation map, but to "pass sysex"; the standard "F0,F7" string, It's a no-go. Thanks for any help LP
|
|
IP Logged |
|
|
|
|