basic midi troubles

Kullervo · Post by **Kullervo** » Mon Jan 22, 2007 5:29 pm

Hello,

I bought a Scope Home 4.0 recently on ebay, and installed it Yesterday.
The installation was trouble free (sadly, there aren't any synth with 4.0 though

); all things audio: mixer, effects and XTC are working flawlessly, but the midi interface seems to be unusable.

Whether internally in Scope, or in my sequencer, the midi IN is completely erratic, note off messages seem not be sent, note value (height) isn't always correct, ...
(my main controller is a technics digital piano, no problem with it when it is plugged in my old terratec card or in the midi in of my usb remote25)

Is there anything obvious I ignore or might have overlooked ?

Thanks for your help!

astroman · Post by **astroman** » Mon Jan 22, 2007 5:50 pm

yes, turn off 'active sensing' on your controller/keyboard - most likely it's transmitting this (unfortunately) by default.
If that's not possible insert a 'midi filter' after the 'midi source' in SFP and route only the filtered midi data - but the best way is to switch it off right at the controller, as the ('Active Sensing') message tends to overflow the midi buffers.

cheers, Tom

Kullervo · Post by **Kullervo** » Tue Jan 23, 2007 3:27 am

Thanks for your answer, Tom. I tried the midi filter option, but unfortunately, that's not it

..weird...
It's good that I still have the remote25 to use as a midi interface.
With 3 dsp's, I wasn't planning on using any scope synth anyway, but it's annoying nonetheless.

Plato · Post by **Plato** » Sun Jan 28, 2007 9:16 am

Sadly I think some gear just doesn't sit well with Scope - I had the exact same problem with a Roland XP-80 - no matter what I did it'd never work with the Scope midi ins - I always had to use an alternative midi input......just one of Scope's idiosyncracies I suppose.
Other gear I've got seems to work flawlessly with it btw