PlanetZ forums - scopeusers.com

Is anyone else experiencing stuck MIDI notes on let's say a Minimax especially when using aftertouch?

Thanks,

-Tom

That's funny you're talking about that, cause i got this same strange behavior with samplitude and harmonia cx synth into just one song, and i don't understand why.
But i need to investigate it more...It only happens sometimes, even if i reload samplitude and scope.
I'm not so expert with midi, so i'm still searching from where it could come from.

are you using the midi filter module? It does good for eliminating active sensing among other stuff you may not be using. Use the midi monitor and see what data is being sent thru.

Also, what's your MIDI path going into the synth? Directly in to a Scope hardware MIDI in, or via a DAW (and if so, which DAW)? What's generating the aftertouch data?

I've experienced problems with aftertouch data in the past, as it can generate a huge amount of messages, depending on the hardware involved. MIDI-OX can help diagnose problems, as you'll be able to see whether all appropriate messages are being sent.

Hi,

I am using a Korg M3 going directly into Scope. Haven't used it with a sequencer yet. MIDI monitor shows the clock, note on/off, and aftertouch data only. Could the clock cause problems?

Thanks,

-Tom

It's certainly possible that the combination of MIDI Clock and aftertouch could be flooding the MIDI connection, but you'd need try to do some digging though the signal chain to find out where the weak link is.

I'd also suggest testing with MIDI Clock disabled, to see if you continue to have the same problem with stuck notes.

Also look into the Korg to see if there is a setting to choose whether to use "MIDI Running Status" or not.

It cuts the amount of traffic over the MIDI bus down significantly, especially for repeated messages like aftertouch.

(or in SCOPE, filter out the aftertouch and clock, and look for all note-on/note-off pairs until you get a stuck note. If it is stuck, it should show no corresponding note-off message).

Thanks for the suggestions guys. I will try to reproduce it first. It seemed to happen quite frequently, but not right now. Hmm.

-Tom

Hi again,

I got it to happen again. It's really odd, however. I had 2 proTones running with 16 poly each (not that should matter). I'm using Scope Pro cards BTW. One proTone got the note off message, the other got "stuck". I wasn't even using aftertouch. I'll try turning off the clock.

-Tom

tlaskows wrote:Is anyone else experiencing stuck MIDI notes on let's say a Minimax especially when using aftertouch?

Thanks,

-Tom

I experience stuck MIDI notes using a Edirol PCR300 controller w/ SCOPE 5.1, going directly into XITE-1 MIDI In,- since a long time.
It´s not related to a specific device, it just happens w/ everything sooner or later.
I´m still on Win XP SP3 32Bit, but it might be, it came with some Win XP SP3 (security) update short before support of Win XP ended.
It drives me nuts because I never had it w/ the same gear combo before which was dead on stable.
B.t.w., I don´t use AT from the PCR300 because it´s not working correctly, so I deactivated anyway.

Bud

That's interesting...

I'm on Windows 7 x64 and 2 Power Pulsars.

-Tom

I get it with various synths sometimes (C4T, three o three, etc ...)

I have a midi keyboard going from my luna to the sequencer and from the sequencer to my scope synths ...

I suspect it happens when i mess with the sequencer transport and there is not "note off" msg that is sent (subsequent note on/offs -e.g. Playing the keys, do not solve this and i have to turn the voice count to zero and back up to stop it .... )

I dont use aftertouch and i think most of the non essential midi messages are filtered (i use a midi filter)

I am running winXP ...

Can you send a MIDI Reset command (it's a real time command, and only takes 1 byte to send...0xFF (hex) or binary 11111111.

That is supposed to reset all voices to a power-on state. It also depends if the soft synths support that...but it sounds like it's worth trying, at least until you figure out if there's a root issue here.

Do you have any advice on how to generate that command in scope(pci) and/ or cubase?

I must add that I get stuck MIDI notes without using a sequencer. Going straight into the MIDI in of the Scope PCI.

-Tom

Oh I forgot to update...

I turned off the clock on the M3 and haven't had a single stuck note

But now I have to slave my M3 to Sonar to use the Karma.

-Tom

That's interesting, because MIDI Realtime messages can be sent at any time in the MIDI stream (even within another message, like a note off).

I wonder if SCOPE is sensitive to this type of behavior? (I personally send controller data through my DAW, so have a dedicated MIDI Sequencer device for realtime messages like clock, and separate MIDI Sequencer devices for each controller.)