Diva's Scope

[JustusHall]

It's unbelievable to me that a daw like cubase 7 has the same oscilloscope that came with Cubase sx3, released in 2005 I can't seem to work with that thing, i want u-he's

Curious - Bram's s(M)exoscope runs in Cubase 6 32bit and 64bit too.

That is indeed curious. It just doesn't show up Did it multiple times, rescanned all plugins but no go....

Try the alternatives from these sites:
http://jaggedplanet.com/VST/jscope.html - very good features
http://www.progressaudio.co.uk/Products.html - simple
Both are running in Cubase 6 Artist 32 / 64 bit.

Manandmusic thanks for the share, but i think these are windows only.
i have a mac but thanks again

[Nig]

We were discussing that last week. We have a suite of analysers, but they're not in proper shape.

I'll see what's possible once Satin is released!

A suite of analysers would be sweet

[mabian]

We were discussing that last week. We have a suite of analysers, but they're not in proper shape.

I'll see what's possible once Satin is released!

A suite of analysers would be sweet

A suite of analysers would be suite

- Mario

[xh3rv]

Do any scopes out there have internal buffers that can hold recorded input? Like a gate-triggered few seconds of audio kept static for comparisons etc. Really like the multi-instance Voxengo stuff, this would be another way to approach that ... I kinda did this with a horrible max patch, it seemed like it'd be nice if it were actually well done

[Ch00rD]

+1 for u-he analyser plug-ins.

Do any scopes out there have internal buffers that can hold recorded input? Like a gate-triggered few seconds of audio kept static for comparisons etc. Really like the multi-instance Voxengo stuff, this would be another way to approach that ... I kinda did this with a horrible max patch, it seemed like it'd be nice if it were actually well done

Perhaps try schwa's schOPE.

[Ameyah Audio]

I'll see what's possible once Satin is released!

[xh3rv]

Perhaps try schwa's schOPE.

Interesting. I haven't looked at schOPE in a long time ... it does buffer the last 1000ms of input, which can be 'frozen' for closer inspection (panned, zoomed, etc.) or with a different type of scope (waterfall spectrograph missing though?). This seems pretty useful to me, much better than just freezing what gets drawn onscreen.

It's not quite what I was trying to suggest, though - let me explain a bit more specifically. (This might make sense or not, but definitely will be boring and too long.)

I think when graphically superimposing two audio signals in the same scope, there's usually some exotic routing. By this I mean anything other than the standard stereo input pair 1/2 that most hosts will just automatically plug the signal chain into when a plug-in is instantiated. So, 'exotic' might be a side-chain or the stereo pair 3/4.

There's more than one way to handle exotic routing. Plugs like schOPE expose additional exotic inputs alongside standard input to the DAW. The DAW has to be configured to send channels to these inputs. Voxengo SPAN's method is an interesting alternative. Here, multiple instances of the plug are dropped at the right points in the signal chain, and they share data directly between each other. The exotic routing is handled inside SPAN. I prefer the latter quite a bit ... perhaps it's DAW-related, routing tracks exotically in Live can be tangled and clunky.

However - I also think there's a way to do some interesting things with no exotic routing. It does require freezing, though, so I'll gloss over that here ...

With a no-frills, generic scope, standard input writes to a drawing buffer. This buffer can be frozen in something like s(M)exoscope; input no longer writes to it. 'Freezing' essentially just stops input writing to the buffer.

Code: Select all

(standard) Input 1/2 -> Buffer -> draw
FROZEN:
Buffer -> draw

With schOPE, input writes to buffers, and buffers are drawn. The buffers are a bit independent of what's onscreen, though - sort of equivalent to having the last 1000ms in a sample, and various scopes can draw all or part of that sample. When 'freeze' is activated, all buffers freeze.

Code: Select all

(standard) Input 1/2 -> Buffer A,
(exotic) Input 3/4 -> Buffer B,
...
(exotic) Input ( n )/( n+1 ) -> Buffer N -> draw
FROZEN:
Buffer A,
Buffer B,
...
Buffer N -> draw

I would suggest that we can freeze buffers one at a time, and also switch where standard input goes.

Code: Select all

(standard) Input 1/2 -> Buffer A -> draw
FROZEN:
Buffer A -> draw,
(standard) Input 1/2 -> Buffer B -> draw

With this method we might avoid exotic routing by first buffering and sampling or freezing an 'A' signal, and then drawing that alongside the actively monitored standard input writing to 'B'. At this point we could turn on some effects and compare A/B. Or if the scope were on a buss, we could solo something into 'A' and then compare with a 'B' that's another solo'd track, or some sub-mix, etc. ([e] Also, not freezing but just ceasing to write to a buffer on a duration of silence IMHO makes sense here, too - gate-triggered recording)

I don't know how 'exotic' routing works in many hosts, but I do know it's a PITA in Live, and not well-defined across plug-in standards. Avoiding it might nice when possible ... I guess these different styles could probably co-exist a bit too, just configured for the context.