New Oscilloscope View


(Ledger) #1

Beat matched for the selected track:

renoise oscillosope view.png

Fantastically useful for visual feedback on compression and even just peak volume differences.


New Tool (3.1.1): SamRender v1.4 build 008 (February 2019)
(The Empty Self) #2

that would be nice …that and also …corrent visualization of the Sxx command when you trigger a part of the sample …would be super cool

so you dont have to switch between the 2 tabs to look for the interesting part in long samples


(Ledger) #3

that would be nice …that and also …corrent visualization of the Sxx command when you trigger a part of the sample …would be super cool

so you dont have to switch between the 2 tabs to look for the interesting part in long samples

Just to be clear both outputs would be a rendering of the audio on the track (one before any fx are applied and one at the end of the chain before the master track fx), so it doesn’t make a difference if it is a VST or a sample, it’s just the output you see. So if you have an Sxx command then you would see the audio rendered as it sounds, i.e. from the correct place. I don`t think you could do what you wanted with that, as in sampler-style scanning parts of a sample.

Some examples of oscilloscopes in VST form:

http://bram.smartelectronix.com/plugins.php?id=4

http://www.sugaraudio.com/oscarizor/

https://www.bluecataudio.com/Products/Product_OscilloscopeMulti/

or LFO tool, which I took the screenshots from for the mock-up:

https://www.xferrecords.com/products/lfotool


(Ledger) #4

Just a simple example of when this is useful:

Snare compression, where compressor has let through and exaggerated a transient, which needs clipping:

Add a clipper to solve the problem:


(ffx) #5

Yes that would be great, just like Ledger said!

And for the “old” oscilloscope like mode, a wavelength detector (or is it some interpolation?), so the waveform will stand still in any case. have a look here, isn’t that cool looking and also seems to be much more informative than a simple very zoomed in “wavescroller”:

https://github.com/Zeinok/SidWiz2F/tree/master/SidWiz


(Ledger) #6

Yes more options around this would be good!

I also saw something similar? in a REPRO-1 video being used in the background. Seems to be in Ableton Live but not sure if it`s a native feature or VST:

https://youtu.be/D3q9t1fOcds?t=39

Fl Studio seems to have Wave Candy too:

https://youtu.be/vf0xXW3Z4ho?t=96


(Ledger) #7

Just found from the youtube comments, the one in the REPRO-1 video is BlueCat oscilloscope but there is a freebie 32bit one from rs-met too:

called ‘Signal Analyzer’ (scroll down page)

http://www.rs-met.com/freebies.html


(Garf) #8

That’s a great idea, I would use it all the time


(Ledger) #9

That’s a great idea, I would use it all the time

Gainstaging FTW! :level_slider:


(Raul (ulneiz)) #10

This looks great. I wonder how much this is feasible…

The first oscilloscope must analyze the resulting wave without any effect and in real time. The second oscilloscope should do the same with all kinds of effects. It would be to analyze the wave in the PRE DSP Chain and the wave in the POST DSP Chain.

As it is only a piece of wave to show, it may not require many resources, but supposedly should have a horizontal zoom. To what limits? Because this would be crazy for a whole clue. I suppose I could be limited in time, 5 or 10 seconds. But I suspect that this can have a direct impact on performance.

I do not know to what extent this is feasible. I can not imagine these new oscilloscopes without a new Renoise GUI that is really fluid. Even some specific native effects can shake the fluency of the playback of the sequence.


(Ledger) #11

Yes It’s certainly feasible on modern cpu. If on a machine that struggles then you just wouldn`t enable the view, but I still imagine that you’d need to be maxing out quite heavily for problems to start.

To make the mockup I used LFO-tool VST. Here on a Xeon 1231 (haswell gen i7) It use less than 1% running 2 instances.

If you want to try yourself there is a demo here:
https://xferrecords.com/products/lfo-tool

To enable the scope press the circled button on the left. if you want to increase the readout length (up to 16 bars), use the Rate slider on the bottom-left.

LFO%20tool

edit:
RE: Rendering up to song length, I guess it wouldn`t be too major of a problem as it only needs to access the current audio ‘chunk’ as any other plugin does. The calculation for previous ‘chunks’ is already done and those results are just rendered to screen and not continously calculated. Similar to showing a long wav in a sampler/ DAW timeline.


(Zer0 Fly) #12

Suggesting a new native dsp device. “Analyser Send”…like send, but will send signal to scope or spectrum analyser channels from anywhere inside DSP fx chains.

I already use it in mixer view, having 2 muted dummy send channels which are wired to the spectrum analyser channels, and then send from anywhere to get spectrum analyser goodness going. Would be cool to do the same for oscilloscope, too, also layering 2 channels to compare the waveforms.


(Ledger) #13

Nice idea too!

Just to expand on that, we could do similar without the need for a device, i.e. just having the option for [output 2] to show the selected device in the track:

edit: though if you wanted to compare different channels/tracks, I see that devices would be necessary.

Renoise%20oscillosope%20view%20sel%20dev


(Ledger) #14

Would be a good place to put some peak readouts (changeable/ next to rms aswell). Shown bottom right of each scope:

osc%20view