problem with local off/midi loop back...

I recently purchased a Moog Little Phatty analog synth keyboard which I'm attempting to use with X1a. I want to use the LP as a master keyboard, but I want to control it with X1a (obviously). I set the LP to transmit and receive on Midi Channel 1 and set the keys to Local Off (so the synth only gets midi from X1a). Everything works until I try and send realtime controls (pitch wheel, mod wheel, etc), the LP locks up and I have to reboot the LP and stop and start X1a for things to work again. I was not sure if the Moog was the problem so I tried the same setup with Tracktion 3: everything worked exactly as expected, no problems.
 
I looked around in the Midi setup under preferences, everything seems to be as it should. Any ideas? thanks...

more tests...seems Sonar 8.5 and X1 both have problems (from what i can tell) getting large midi streams while a sequence is playing...again, testing with Tracktion 3 was flawless...

ba_midi

ross g2


more tests...seems Sonar 8.5 and X1 both have problems (from what i can tell) getting large midi streams while a sequence is playing...again, testing with Tracktion 3 was flawless...

You might want to double check in the Global Options of Sonar that you're not sending Aftertouch (that eats up a LOT of space/cycles/dataflow); and check to see if you have sysex enabled (try unchecking it).
 
I don't know if this will resolve the issue, but it's worth looking into.
 
Are you 100% sure you're in Local Off when you start up Sonar with the LP connected?
 
 

aftertouch and sysex are both off, Local Off engaged...another test: my "master keyboard" can send pitch and mod wheel and the Moog will receive ok, but then i can't use the Moog's other realtime controls (like filter cutoff/EG/etc), so it sort of defeats the purpose...the only thing i can think of is Sonar doesn't like the USB interface on the Little Phatty, but again, this defeats the purpose as i got the Stage II model specifically for the USB interface (my Cakewalk UM-G3's ports are all being used)...
 
i understand some midi issues are being dealt with in the next X1 version, i can only hope mine will be resolved...i otherwise like X1 for the most part, fingers crossed...

bvideo


Watch out for the MIDI merge function on that keyboard (separate settings for USB and DIN). Merge ON would cause the problem you are seeing.

Bill B

good looking out, but turned off...
 
again, just to point out the weirdness: the old, not updated in a long time (but current) Tracktion 3 DAW I still own and use works flawlessly...

bvideo


There's a midi monitor tool called midiox . It can be used to show you what midi events are coming in on any given midi interface. Maybe it can show you the contents of those large midi streams and whether or not there is excessive data going through your system.

Unfortunately, the different behavior of Tracktion is not making me think of any special clue, because of any number of possible differences in the setups.

Along with midiox, in the interests of diagnostics, maybe you could set up your keyboard & Sonar so that your keyboard is transmitting to your PC on channel 1 and Sonar is transmitting to your keyboard on channel 2 (.e.g). If you can arrange that, you might be able to tell which end of the chain is originating excess data.

Bill B

i did try that already, no change...i'm going to try using the Moog with my midi interface and not USB to see if that's the problem, and i'll try midiox as well...

Did you have both the DIN and USB ports connected to your DAW at the same time. MIDI Crosstalk between ports receiving data on the same channel is the main MIDI fix that's in X1b. Use just one or the other.