PlanetZ forums - scopeusers.com

I thought I saw something in regards to this here a while back but maybe I was dreaming.

No problem with a Kurzweil keyboard but my Triton Pro seems to suffer from stuck MIDI notes with Pulsar synths. Anyone know how to cure that problem?

With the Roland A33 controller the problem is that it sends a midi clock by default which must be switched off. Maybe your keyboard is also send extraneous commands... Can you monitor the stream from the keyboard ?

Thanks Spirit. I am sorry to report that I am nothing more than an amoeba in the evolutionary scale of MIDI instrumentation and understanding. So I don't have a clue how to monitor MIDI streams. But I will look into the MIDI clocking thing. I will reluctantly have to actually look at the dead sea scrolls which are my Triton User Manuals and attempt to find the section concerning MIDI clocking If anyone else knows a thing or two about this, please feel free to chime in!

Sorry if this sounded more complex than it really is ! Just drop the "midi monitor" device into your project and give it a feed from the midi source module. Then double-click to see what incoming midi you have.

If you are not playing anything it should just say "active sensing". Anthing else - especially "timing clock" indicates your keyboard is sending extra commands. It should then be pretty straiht-forward to consult the scrolls and see how to switch it off.

This of course assumes that the problem is your keyboard, but then the monitor should tell you....

And actually Active Sensing can throw off many devices as well - it locks up my AMT8 when connected via USB, for example - and most/many MIDI keyboards do not send active sensing. Of course it is easy to filter active sensing inside a Logic environment, and also where I happen to monitor all my incoming midi streams...