Older versions of Midi communication plugins, as well as the Windows version, upon sending the Sysex receive 1 Sysex response from the Midi device.
However, using a new, non-deprecated set of plugins, when I send the Sysex I receive thousands of responses, which continue endlessly until a new Sysex is sent, whereupon it switches the output to respond to the Sysex but continues in an endless loop, sending thousands of outputs.
Has anyone had a similar issue? I don't understand why the device would send one Sysex response normally, but now, it clearly understands the Sysex (as the output corresponds), yet it insists on sending thousands of messages (including some that weren't specifically requested). If nobody can relate to the problem, is there a MIDI command that will tell the device to stop sending System exclusive messages?
The photo below shows an example of the frenetic activity of the device.
However, using a new, non-deprecated set of plugins, when I send the Sysex I receive thousands of responses, which continue endlessly until a new Sysex is sent, whereupon it switches the output to respond to the Sysex but continues in an endless loop, sending thousands of outputs.
Has anyone had a similar issue? I don't understand why the device would send one Sysex response normally, but now, it clearly understands the Sysex (as the output corresponds), yet it insists on sending thousands of messages (including some that weren't specifically requested). If nobody can relate to the problem, is there a MIDI command that will tell the device to stop sending System exclusive messages?
The photo below shows an example of the frenetic activity of the device.
This sounds wierd, and totally useless. As you describe it.
It sounds like a DUMP REQUEST. Such a SysEx instruction would normally include a memory range, i.e. a start address and an end address, and the device would send all the data between the two addresses, and if there is a LOT of data then this could be a large number of packets.
Have you checked that your initial REQUEST SysEx command has not got a memory address messed up so that a small range has become a massive range?
The data you show on the screen does not seem to be repeated - I'll need to try to download something and study your snapshot more closely, if that is possible.
I assume you could just turn the 'device' off?
Once a BULK DUMP has been set in motion, it may not be possible to enact a further SysEx command??
Update - looking again at the data showing in the .PNG, there is a lot of evidence of repetition although the data is nothing like complete. There may well be a pattern of a number of lines being repeated, but the repetition may well be a LOT of data??
Geoff
It sounds like a DUMP REQUEST. Such a SysEx instruction would normally include a memory range, i.e. a start address and an end address, and the device would send all the data between the two addresses, and if there is a LOT of data then this could be a large number of packets.
Have you checked that your initial REQUEST SysEx command has not got a memory address messed up so that a small range has become a massive range?
The data you show on the screen does not seem to be repeated - I'll need to try to download something and study your snapshot more closely, if that is possible.
I assume you could just turn the 'device' off?
Once a BULK DUMP has been set in motion, it may not be possible to enact a further SysEx command??
Update - looking again at the data showing in the .PNG, there is a lot of evidence of repetition although the data is nothing like complete. There may well be a pattern of a number of lines being repeated, but the repetition may well be a LOT of data??
Geoff
The device immediately responds to further Sysex commands, it just responds to changing the output to endless loops of the action of the new Sysex.
I think it is a problem with the plugin I am using (MBS for Xojo), as using the CoreMIDI API on Swift/Xcode to send the same instructions has normal behaviour. As such, I don't think this forum can help much.
I think it is a problem with the plugin I am using (MBS for Xojo), as using the CoreMIDI API on Swift/Xcode to send the same instructions has normal behaviour. As such, I don't think this forum can help much.
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!
