PlanetZ forums - scopeusers.com

No problem, done.
Please see start post, i hope this will clarify some things!

Thank you Roy, very useful

Thanks Roy, way to push the Scope sequencer envelope!

This is great! Just tried it out a little today, sound is awesome, interface is inspiring, DSP load is lower than expected!
For reference, I can load a 1 Voice instance of the full stepsync on a Luna card, or racksynth1 plus clock and sequencers with approx 30% of the resources left.

Thanks again for these great devices

big thanks, fantastic! love it!!
wait for modul to manipulate steps ><; <>; >~> ...

yes, I want that too.
I have the idea of a kind of 'Uber-SeqClk', which could control all the things you mentioned.
Let's see..

fantastic idea, look and work!
outside device-modules for better midi-timing and more separate ctl-allocation because on ch1-16...
> system I/O compatible with bc modular sync/async...pipe and/or convert to midiout for ext?
gizzmo is lost and the real sb404 grandchild comes home,
hoch lebe roy!

Just out of interest.

The sequencer works perfectly on Xite.

What is it you did/do when making these devices so that the sequencers work fine on Xite?

it's not using nifty async dsp modules but primitive sync ones instead.
if that wouldn't work in xite I think you could throw it away

hallo roy,
i love your SeqDevices, REALLY!
what you think about "CTLR to Midi" converter?
see brainstorm pic
... and pleace add too
> "Rack/SyncStep Synth" with second Hp-filter, serial (ctrl-Param. identical to Lp)
> hardware connection
>> all SeqDevices with MIDI Ctrl Assignment >> hardware controller
>>> "visuals Clk on" with MIDI Ctrl Assignment (0/127) >> hardware (Buttons) Lightline
that would be really cool!!
lg
ron

+1

** Visualizer - ghost button on the right cheek opens PresetList!?!
*
** add polymode for successful chord editing, define the voiceboards which should be editable, or link them to the destination
*

Spielraum wrote: Sat Dec 07, 2019 2:18 am Visualizer - ghost button on the right cheek opens PresetList!?!

Ah, you've noticed! Please forgive me.

Spielraum wrote: Sun Feb 18, 2018 2:12 am what you think about "CTLR to Midi" converter

I don't have Mehdi's devices...
...but I'm sure you cannot convert Sync signals to Async signals without being totally out of sync. (long live Sync )

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.

spacef wrote: Thu Dec 12, 2019 12:04 am ...
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.

roy thinnes wrote: Wed Dec 11, 2019 6:06 am ...
...but I'm sure you cannot convert Sync signals to Async signals without being totally out of sync. (long live Sync )

ich Jäger und Sammler, du Jane!
I have copied the current very interesting data into my block
http://forums.scopeusers.com/viewtopic.php?f=36&t=36169#p342421

that should help with constant searching and not finding