Freaky Glitches

Marv_Incredible

Has anyone else ever experienced freaky goings-on with Mix Emergency? I've had them for a while now and even a fresh install didn't seem to help (I'm using 2.7.0). Here are some examples: * Cross-fade button randomly un-latching itself * Mysterious channel FX appearing on deck when none are selected (only solution is to restart) * With Mixer FX, I can map knobs separately but even if I program both FX slots differently (both sets of two I mean), both knobs will use the first set of FX * After setting transitions to 'random', they would keep switching out of random to a static transition for no reason * Rogue midi messages being sent to / from / via ME. can't narrow it down yet. All I know is I've had to disable Mix Emergency In from teh MIDI menu * I'll click one of the 16 segments in the FX sequencer window but all the segments activate. In other cases, clicking one will cause a group of four to activate. It doesn't seem to have aything to do with the global rate either because I can program other FX within the same preset just fine With the possible exception of the rogue midi messages, none of this seems to be as a result of anything I'm doing wrong and there also doesn't seem to be anything I can do about it. But it's making the program unreliable and almost unusable because I never know if, when or how it's going to freak out on me. Any ideas? Nick?

Nick

It sounds like there are some MIDI conflicts happening, or something like this. What are the "mysterious channel FX"? Is it an actual effect plug-in? Perhaps you could grab a screenshot? As for the FX Sequencer window activating more than one button, this is related to the number of Beats that you have selected for the FX animation.

Marv_Incredible

Thanks Nick. Yes it's an actual effect plug-in (can't remember which ones) and I'll grab a screen shot the next time it happens. It could be a rogue message causing it but when that's happened in other cases, the corresponding button has been active (or inactive, as is the case with the transition button) as if indeed a MIDI command was being sent to turn it on or off. But in this case, the effect was on with seemingly no buttons being activated and no way to turn it off. The FX sequencer thing makes sense now you've explained it. Thanks. As for the rogue messages, I'm glad this seems to be the issue as it means resolving it will resolve many issues. Tracking down what's causing it however, may be tricky.

Nick

Unfortunately, tracking down issues with MIDI messages can be quite difficult sometimes. Do you have the load/save effects preference enabled in the first screen of MixEmergency's Preferences?

Marv_Incredible

Both enabled by default

Marv_Incredible

Just to let you know a bit more about y setup. I'm running M/E 2.7 on a 2011, 2.2 Ghz, 8GB, i7 MBP. I'm using a Rane 68, APC40, DDJ-SP1 and a pair of Dicers. With the exception of the 68, all other devices (including my external mouse and keyboard) are running through a 10-port USB hub. It runs fine, but there must be some sort of issue with it as it 'resets' itself every now and then as if I've disconnected and reconnected the cable. All the devices are mapped to M/E in some way, shape or form.

Marv_Incredible

Some more info. I've narrowed it down to the 68. After running the MIDI log I unplugged and replugged all other devices one by one and then the actual USB hub. No change. As soon as I switched off the 68, the incoming MIDI messages stopped. I switched it back on and tried activating and deactivating the 68 in both the MIDI In and MIDI Out prefs. No change. The only thing that stops the flood is deactivating Mix Emergency In from the MIDI In pref. Also ran MIDI Monitor to see if any bleed was being picked up but I got nothing until I actually pressed some controls. So this conflict with the mixer appears to be strictly M/E related. I even tried changing the MIDI ports on the 68 but even after turning them off entirely I was still getting the flood. Here's an example of the message I'm getting. 17487757343150 0x9B 0x41 0x00 (Note On (Off)) 17488000591515 0x9B 0x41 0x7F (Note On) 17488254151400 0x9B 0x41 0x00 (Note On (Off)) 17488509553560 0x9B 0x41 0x7F (Note On) 17488753589860 0x9B 0x41 0x00 (Note On (Off)) 17489003051800 0x9B 0x41 0x7F (Note On) 17489256453370 0x9B 0x41 0x00 (Note On (Off)) 17489500176515 0x9B 0x41 0x7F (Note On) 17489751660380 0x9B 0x41 0x00 (Note On (Off)) 17490008504915 0x9B 0x41 0x7F (Note On) 17490260443564 0x9B 0x41 0x00 (Note On (Off)) 17490502006649 0x9B 0x41 0x7F (Note On) 17490754997489 0x9B 0x41 0x00 (Note On (Off)) 17491007428394 0x9B 0x41 0x7F (Note On) 17491258019129 0x9B 0x41 0x00 (Note On (Off)) 17491502698079 0x9B 0x41 0x7F (Note On) 17491756108004 0x9B 0x41 0x00 (Note On (Off)) 17492010090319 0x9B 0x41 0x7F (Note On) 17492252354114 0x9B 0x41 0x00 (Note On (Off)) 17492505751848 0x9B 0x41 0x7F (Note On) 17492756967283 0x9B 0x41 0x00 (Note On (Off)) 17493008787323 0x9B 0x41 0x7F (Note On) 17493252041818 0x9B 0x41 0x00 (Note On (Off)) 17493506312898 0x9B 0x41 0x7F (Note On) 17493759652043 0x9B 0x41 0x00 (Note On (Off)) 17494001488768 0x9B 0x41 0x7F (Note On) 17494254615933 0x9B 0x41 0x00 (Note On (Off))

Nick

I would suggest disabling the effect loading/saving preference (unless it's something that you want to use). Do you have the MIDI note 65 mapped to anything in MixEmergency? (You can do a text search for this in the file: ~/Movies/MixEmergency/Control Mappings/_AUTOSAVE.xml)

Marv_Incredible

Ok, I'll disable those. As for MIDI note 65, I have no idea. And the only reference to 65 I could find in that document was this: < control channel="0" control="65" invert="false" controlType="Note" interpretation="HoldDecrement" id="FXB1Select">" Is channel="0" theMix Emergency internal? Is FXB1 the left deck FX selector or ssomething?

Nick

I believe that channel 0 is actually MIDI channel 1. FXB1Select is the pop-up button for the right effect (so, it selects which effect is applied).

Marv_Incredible

Well that could explain why it appears to be clashing with teh 68 since thats on channel 1 too. But then, when I changed the channel, the flood still happened so...? I must admit, I've been having a hard time working out M/E's MIDI. So from the MIDI log code (4 posts above), can I assume that where it says 0x9B and 0x41 etc., that the 0 = channel 0? Which, as you point out, is in fact channel 1?

Nick

The 0x9B signifies that a "Note On" message has been sent (0x90), and that the channel is channel 0xB (which is the number 11, but actually MIDI "channel 12", as they count from 0 as "channel 1"). Do you have anything sending MIDI via this channel? Have you tried the MIDI Monitor application? You should be able to monitor the messages and narrow down the source.

Marv_Incredible

"Also ran MIDI Monitor to see if any bleed was being picked up but I got nothing until I actually pressed some controls." I'll try again though. See what I can figure out. This cross-fader unlatching thing is a killer.

Nick

Ah, sorry - I missed that.