Support
Looper's Delight
|
Support |
|
|
that right, Andy! sorry, Fred, since we have a very old processor (like a Mac Plus!) in the EDP its audio DSP part stops when it has to deal with Sysex. Usually thats not a problem because Sysex is used to change parameters while not playing, and a single command hardly creates an audible interruption. but if you send Sysex streams meant for other units to it as well, it hicks up. to select different channels does not solve the problem, because it needs to analyze the data anyway. Sysex does not differentiate channels but IDs so I dont think it does much with the stuff you send to the 99 anyway, but just to figure out that the data is not aimed to it, takes proc time... I suppose you will have to either command the 99 some other way or filter the Sysex stuff so it does not go through it or filter it in a separate midi box between 99 and EDP... there are many options, probably... good luck! Matthias On 24 Aug 2009, at 04:56, andy butler wrote: > > > Fred Fata wrote: > >> While in Control Change mode I record sound into the EDP, >> I return to Sysex mode and change patches on the 99 via the 300, >> an audible thump is heard in the recorded info in the EDP. > > that's the edp trying to deal with all those sysex commands. > > Are you using a different midi ch for the EDP? don't > know if that would help, but edp may not read the sysex if it's > on a different channel. > > You could try chaining 300>>99>>edp so edp doesn't get sysex, > but beware added midi latency. > > andy >