Traditional Oscilloscope

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

Curious if there's currently a way to get a "traditional" left-to-right oscilloscope in Wren? I see that there's an XY oscilloscope, which is handy for stereo images, but I'd like to have a way to view waveforms in a more traditional manner to see what is happening to the sound over time.

Is there currently a way to do this? If not, I think I'd make that a feature request Smile

Thanks!

Blue Hell · Posted: Sat Apr 10, 2021 1:16 pm Post subject:

The thing sucks a bit .. but what you can try is to connect a saw wave to the X in and the signal to the Y in ... then maybe reset the saw when the signal is near some value ...

Another way is is to use the graphs thing ... F5 to go to the debug screen, make sure that debug settings "Use graphs" is on, then F4 to go to the graphs screen ..then stop audio if it was running (F9) and hit "debug run" in the graphs screen .. but that really is just for debugging things as it is amazingly slow wh lots of points get accumulated ... anyways, that is what I use for debugging signals.

Edit: the graphs are made from the sum of all output modules in the patch .. so .. could send some debug signals to say output 3 .. 8 .. and then use that on just one output module.

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

Just an update confirming that this works for now as a way to use the XY oscilloscope as a more traditional one - you'll have to tweak the history amount depending on your input though, and you'll still get weird black lines connecting different parts of the waveform, but it'll do in a pinch.

Untitled.png

Description:

Filesize:

16.24 KB

Viewed:

254 Time(s)

This image has been reduced to fit the page. Click on it to enlarge.

Blue Hell · Posted: Sat Apr 10, 2021 6:37 pm Post subject:

Yeah it is pretty messy, but indeed can see some things with abit of fiddling.

Blue Hell · Posted: Sat Apr 10, 2021 7:21 pm Post subject:

Your request for a a real(-ish) o-scope has been noted.

I'll have to think a bit of what it would actually have to do. A 'real scope' can be pretty complex, but I do not think such complexity would add much, a more or less still wave image would be enough I guess .. so 'real-ish', without too many controls, maybe just a level control.

edit: and probably some time base control too.

Blue Hell · Posted: Sun Apr 11, 2021 6:23 pm Post subject:

I've made something a bit more traditional in a pre-release version.

https://bluehell.nl/wren/#changes for info
https://bluehell.nl/wiekietje/pmwiki.php/Wren/PreRelease for the info about what to do with a pre-release and a downlaod link.

Posted Image, might have been reduced in size. Click Image to view fullscreen.

Posted Image, might have been reduced in size. Click Image to view fullscreen.

It's not perfect (the update rate is quite low), but at least a bit .. more traditional .. or real-ish :)

Edit: Just made it update four times as fast, but that is not in a pre-release yet .. next time :)

Edit: .. o .. wait .. it actually is in .. heh.

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

Blue Hell · Posted: Sat Apr 24, 2021 12:07 pm Post subject:

Strange ... this is what I get (for example)

Edit: what is your 'lights rate'? (on the settings screen (F3), near the top left). I have it set to 24.40Hz here.

Posted Image, might have been reduced in size. Click Image to view fullscreen.

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

Grumble · Posted: Sat Apr 24, 2021 2:19 pm Post subject:

Maybe it’s a video card issue?

Blue Hell · Posted: Sat Apr 24, 2021 2:30 pm Post subject:

I forgot to set a pen color for trace painting ... and the trace will now show in the border color ... could you set that color to some other value? (to see if you get something displayed then).

It is the Viewer border color under colors in the settings screen (F3).

As to why the module would eat a lot of CPU ... I have no idea yet ... it uses about 1% or so here, and there is nothing in it that would be CPU heavy.

For the next pre-release that color issue will be fixed, and it will be the Viewer line color then

Blue Hell · Posted: Sat Apr 24, 2021 3:02 pm Post subject:

Ok, I've made a new pre-release for the color issue, and also added a debug display to the scope module that will show the internal state of the module.

State can be any of (Collecting, Displaying, PreSyncing, Syncing) (with an msts prefix).

What state does it show to you? (I would expect it to be mostly mstsDisplaying) - in the patch sketched above.

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA

Blue Hell · Posted: Sat Apr 24, 2021 4:54 pm Post subject:

Ok .. still weird .. in that simple patch I used I see no noticible difference in CPU usage (the % as reported by Wren itself) with or without the scope module being present.

Ah, but the windows CPU usage does go up a bit on it it seems, yup, quite a bit .. must be the screen painting then I guess ... hmm

Anyway - is that what you meant?

Edit: sped up the drawing quite a bit too, windows CPU display is more reasonable now. Publised a fresh pre-release for that. Also decided on keeping the state display.

stelpa · Joined: Apr 09, 2021 Posts: 21 Location: USA