Slower Largescope

[Wassaka]

Hi, I am trying to do a largescope (display) for my compressor. I made it, but is too fast... Any idea how to slow it down? Thanks!
Here is the largescope with compressor.

[nix]

You need to take a longer window time somehow mate

[Wassaka]

You need to take a longer window time somehow mate

Yeah, but I have no idea how to do that

[BobF]

Hello Wassaka ,

How does this work for you? You can choose a value that works for you.

compressor_largescopeBobed.fsm

(736.44 KiB) Downloaded 1058 times

Cheers, BobF

[Wassaka]

@BobF
Thanks you for the reply, but I'm looking for a way that slows down in speed, not in FPS.

- I made a version that works just as I want it, but unfortunately it is modifying the SAMPLERATE, and that destroys the sound... Is there a way to do the same but without modifing the SR?
Here is the file (dowsn't work on FLSTUDIO Flowstone, [only in .exe] )

[tulamide]

That tells you resolution is key.

Reducing the samplerate means you reduce the amount of data per second. So instead of reducing the sample rate, reduce the amount of data per second for the scope only. Less data means less change, less change means slower movement impression.

[adamszabo]

He is using the mono to graph primitive, and the "INS" input (number of samples to take) has an upper limit, so he cant increase the size.

[Spogg]

I do know this isn't what you want exactly but it does allow you to examine the waveform using the run/hold button...

Cheers

Spogg

[Wassaka]

He is using the mono to graph primitive, and the "INS" input (number of samples to take) has an upper limit, so he cant increase the size.

Exactly, the limit of samples per second is 44100. If you choose a smaller value of samples to this the graph, it will go even faster.

[tulamide]

He is using the mono to graph primitive, and the "INS" input (number of samples to take) has an upper limit, so he cant increase the size.

Exactly, the limit of samples per second is 44100. If you choose a smaller value of samples to this the graph, it will go even faster.

I'm not sure if the limit is 44100, or the samplerate of the project (which makes more sense).
If you use a smaller value, you don't have less data per second, since it still runs at samplerate. You could either buffer data to get away from samplerate and lower the amount of data per second, or leave out data while maintaining the samplerate speed.


view displays x amount of data
stream provides y amount of data

if y < x wait until y = x -> results in slower movement
if y >= x just take a portion of y, y/z, wait until y/z = x -> results in slower movement