PlanetZ forums - scopeusers.com

I've been struggling with my Luna card's inability to properly handle midi signals. I know I'm throwing a lot of information at it, but the inability to cope with real playing of almost any vst instrument has finally gotten me to the point of enough.

Sadly, 'cause I really like the rest of the card features.

So, to give it one last attempt of redemtion I ask this:

Does version 5 or 5.1 of scope solve the issue of the card choking on midi messages?

I'm not going to spend the money for an upgrade, if I'm not certain. Especially since I could use a portable interface, and this would be a good time to invest.

What are you sending to it? I send several ch of midi including poly at and cc messages and not had one prob.If you send active sensing you need to stop that.Everything else shouldnt be a problem...at all.And you need to filter active sensing before it reaches the card.More info is needed here.

It's connected to a Roland A90, and yes that throws active sensing at the card. However, I don't think I can turn that off on the keyboard

soje wrote:It's connected to a Roland A90, and yes that throws active sensing at the card. However, I don't think I can turn that off on the keyboard

You are using that as masterkeyboard i guess.You can try to filter it out directly after the midi in with the midi filter.Apart from that ....its getting a new masterkeyboard.
Or you use another midi interface like the ploytech midi-usb which is very good and route that to scope.
Those are the options.

use a midi filter in Scope after the Luna midi source and filter active sensing. that should fix the problem. basically, Fluxpod gave good info.

It might depend on the system. My JD800 & JV1000 both send active sensing and some systems seem to not mind at all (an LGA775 Core2 system I had for a bit) and others will outright crash even with the Scope-based filtering (P4 era machines w/ HT). Most older synths with Active Sensing don't let you disable it unfortunately. You can certainly try the filtering that Flux recommends with little time lost though...and find out.

I've got the same problem with korg triton extrem as controller . the scope midi filter don't help at all .
this the only keyboard i've got which shows this problem . so I don't use it as controller.
hope this help .

All the little boxes here filter out Active Sensing before it hits your port.

http://www.midisolutions.com/products.htm

From thier FAQ page :
=============================
Q. Do any of the MIDI Solutions products filter active sensing messages?

A: We have found that the problems introduced by active sensing outweigh its benefits, therefore all MIDI Solutions products (except Thru boxes and the Power Adapter) filter active sensing messages.

=============================

The THRU is the cheapest at $49US.

But maybe you could first test it with another keyboard that doesnt have Active Sensing.

one thing I want to add ,in my case it happen only with scope synth ( minimax , b2003 for example ) and not with cubase vsti .....
when I use the korg triton extreme as controller very often some note get stuck .it happen in scope instrument but not in VSTI . The scope midi filter don't solve the problem .

I had the problem, too. Pulsar I, Win XP , Scope software 4 and mostly a Yamaha CS1x.
My solution was to use an USB midi interface, like Fluxpod already mentioned.
The old green box, midiman - midisport 2x2 did the job.

Now I am on scope 5.1 and I discovered no midi problems and can use the Pulsar midi ports again.
My tip, upgrade and when the problem resists, get an additional usb midi interface but don't throw away your Lunas.

I filter mine out on either my MOTU MicroExpress or TimePieceAV.