Hi MattAll this is true, but SysEx is specific to a 'Device Number' IIRC. Thus if you only want to send a new bank to your Korg M25, set it to a different device number from your Yamaha A23 etc. I don't know whether you can change device numbers for the EDP / Axe-FX though - you might have to RTFM! If the EDP is set to a different device no. it shouldn't receive the SysEx stuff, but should still receive the Midi channel data.
hth Dave On 01/07/2014 08:08, andy butler wrote:
hi Matt, Pers right.I can confirm that the EDP audio will be glitchy when you sen a load of sysex.I expect that's just because it's a massive amount of midi data. andy On 30/06/2014 23:09, Per Boysen wrote:Your guess is correct: MIDI SySex does not support MIDI channel number. Sysex data is not good for music, in fact it it was designed for sending non timing critical data (like patches and global settings). Sysex events are very long and do not fit in between clock data in a MIDI stream so therefor it wrecks havoc with the timing. Maybe you can use separate MIDI out ports to address the Axe and the EDP directly? Daisy-chaining is bad when Sysex is in the house. Giving Daisy a separate room will cut MIDI some slack. :-)On Mon, Jun 30, 2014 at 11:16 PM, Matt McCabe <firstname.lastname@example.org> wrote:I’m having a strange problem with my Axe-Fx and EDP. Realtime SysEx data sent from the Axe-Fx (set to MIDI channel 1) is causing audible glitches on my EDP (set to MIDI channel 3). I’ve recorded the SysEx data into a sequencer and it is showing MIDI channel 0 - which seems strange...but maybe SysEx data doesn’t confirm to the channels 1-16? Anyway, am I missing a parameter on the EDP to filter out SysEx messages or is there another solution?Matt
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4592 / Virus Database: 3986/7788 - Release Date: 07/03/14