I don't do sync to midi notes.... if that's what people are talking about in this thread.
it works a few minutes and goes wild after a while and is not useable for me. Worf's step sequencer reacts like this, and even Creamware's Noah's step sequencer (which can send out midi notes) can be erratic after a while. Or even the stock arpegiator (back in the days, it could crash my scope system under win XP) . All these are perfectly useable , but not for a very long time (as said, after a while, it goes wild), and they must be used "reasonably" (not process a ton of information at the same time).
That's why a device like KrOn (or K16 oir LBH or any of my sequencers) does *not* include CV to *Midi note*. KrOn is full sync and it is precise as hell and can run in sync for hours without re-triggering.
Gating is also very precise (triggering external hardware) but that's because it uses CV (or audio for an MS20 signal follower) , not midi, not software. I've been using it with analog synth and it wortks just as fine as it would with a scope synth. But there is no midi involved
Converting midi Control Changes, After Touch etc into CV/sync signal works very fine too. These are all continuous, slow signals. They are perfectly manageable in scope, and addinga lag time to smooth out the midi CC works quite nicely.
It's just that I don't think that Scope is so great for midi. For example, too many midi Control Change at the same time can cause graphic lags, and can be annoying. Using a few of them is generally ok though. I beleive that's because the conversion has to go to Windows before coming back into scope, just like the graphics. so it is slow and will not be great to work "at compressor's speed and precision". There is a bottleneck. But it is enough for manual control for a few CCs and can be helpful.
I will soon release a mini device for KrOn users, that allows to convert CV/sync to Midi CC , to be sent to your VSTi parameters that can be controlled by midi. It is super fast and it *cannot* go out of sync BUT it can be less precise than sync of course.
Now, you could record KrOn output as audio in a DAW , and use this audio to trigger stuff that can be triggered that way, without the need to go back into scope. Like that, it would be 100% windows/native, and it would be as precise as native stuff allow.
Or you could use it to feed an "audio to Gate" module in Scope, and it would be very precise too (because it is not midi).
There is actually a great device that almost everyone has and that is dedicated to midi notes and can also take care of midi CCs: it is the piano roll of your DAW
Why attenmpting reinventing a wheel that would work less good than what we already all have ?
Sorry for the long blurb and possibility of being off topic, just wanted to make things clear about what i do and don't do.
