Change O-scope default colors?

ben_wizards

I love the integrated Scope. It's about 90% of the reason I decided to start this new project with Bela rather than one of the other dozen or so boards I have sitting in my "someday, I'll do it" pile. It's great to not need extra hardware to get a quick idea of what's going on. It makes Bela a sketchpad for ideas in ways that I haven't seen other platforms do.

That said...I hate the default colors past 0 and 1. 3 + 4 are almost unusably unreadable, especially if I'm up late and I'm using Flux. I've tried changing the colors by typing in different hex values but it doesn't take. Any advice?

Also, as a wish list item, one thing that'd be cool would be if you could add the scope as an in IDE option so I don't have to tab back and forth. It'd obviously be much smaller, but even seeing that there is SOME periodic output is often enough to verify something quick.

Thanks!

LiamDonovan

ben_wizards Great to hear you like the scope. You should be able to change the colours for each channel in the control panel, but it actually looks like that is broken on the current release!

If you update to the scope-dev branch of the repo (instructions here) this is fixed, and there are a number of other improvements too, including better performance, a nicer UI and some extra plotting options.

giuliomoro

Not sure what you mean about typing in hex values.
You can change the colour of a scope trace by opening "controls" and clicking on the color box. If you want to change the defaults , edit on the board: Bela/IDE/public/scope/js/bundle.js, find the line
var colours = ['#ff0000', '#0000ff', '#00ff00', '#ffff00', '#00ffff', '#ff00ff'];
and put there your favourite scope colors. Note this will very likely be overwritten at every board update.

We are not planning to add a scope view in the main IDE window at the moment, but it can easily be achieved using multiple browser windows and your operating system's window manager (recommended), or writing your own <frame> wrapper page (not-recommended).

giuliomoro

For instance create a file ide-scope.html on you computer with this content and open it in your browser.

<frameset cols="100%" rows="70%, 30%">
  <frame src="http://192.168.7.2" >
  <frame src="http://192.168.7.2/scope" >
</frameset>

Note that <frameset> is not supported by HTML 5

ben_wizards

giuliomoro <frameset cols="100%" rows="70%, 30%">
<frame src="http://192.168.7.2" >
<frame src="http://192.168.7.2/scope" >
</frameset>

I didn't event think about that. Perfect, thanks. And about my initial question, LiamDonovan answered it. Adjusting the color isn't working in the branch I'm using.

ben_wizards

@LiamDonovan , I downloaded the latest scope-dev branch. It doesn't have the Neon math library included, so I can't use it on my project, but I wanted to play with it. It's not working. When I first build a demo project I get this warning and then nothing happens in the scope window.

Build finished
In file Scope.cpp: 'yAxis[1u]' may be used uninitialized in this function [-Wmaybe-uninitialized] column: 60, line: 439
In file Scope.cpp: 'yAxis[0u]' may be used uninitialized in this function [-Wmaybe-uninitialized] column: 42, line: 439
Running project...

Also, a weirdness. When I updated to the scope branch, the sinetone_optimized example was still in the demo section-how could that be the case?

LiamDonovan

ben_wizards That's odd, I can't reproduce this.

Did you update via the IDE or with the scripts?

ben_wizards

LiamDonovan The IDE. I was running the latest from the neon-dev branch and updated to the scope branch.

Is there something I can do to troubleshoot this?

LiamDonovan

ben_wizards Yeah, I suspect it's actually a problem with the in-IDE update rather than the scope code. Could you try updating via the scripts? To do this you need to clone the main Bela repo on your host computer (or run git pull if you already have it cloned), run git checkout scope-dev and then run scripts/update_board and say yes to the warnings.

Once that's completed, refresh both the IDE and the scope in your browser and run the 05-communications/scope-slider example. Also check to see if the sinetone_optimized example is still there?

ben_wizards

Ok, yeah. I updated everything. Same problem. I see the new choices, the sliders, the different look, but it just sits with a red "Waiting"

I just looked on the github page and the sinetone_optimized example is there in scope-dev under examples, but there's no support for the new Neon functions added yet to this branch.

LiamDonovan

ben_wizards Ah, are you using Safari?

It looks like the new scope is not working in Safari, try Chrome or Firefox! I'll fix it in Safari...

giuliomoro

It is not there. https://github.com/BelaPlatform/Bela/tree/scope-dev/examples/01-Basics

Can you describe in detail how to reproduce your issue?

The thing about examples not being deleted is known and I am working on it. Fixed now.

ben_wizards

Works great in Chrome. Can't use it with my project though, it's dependent on sinf_neon for to make sine waves.

The new scope looks awesome, love having the color selector instead of the raw hex to pick the color (and love having it work). Linear interpolation makes it pretty. Love the slider option. Can't wait to try it out on my project.

@giuliomoro, I just saw your email. I'll try that out and report back.

ben_wizards

@giuliomoro -works well so far. Thanks! I love the new scope.

ben_wizards

@LiamDonovan, just an update. The FFT of the new scope crashes often in Chrome (OSX) and even when it doesn't, CPU + IDE usage % goes through the roof.

giuliomoro

Oh the crash is annoying. Can you explain how to reproduce that?

ben_wizards

giuliomoro I tried, but I changed some stuff around and can't get it to come back.

I am, on this build, running into an issue where once cpu hits above ~80%, I get really nasty distortion that manifests as like a rolling interference pattern on the scope.

giuliomoro

When Bela's audio thread CPU goes above 75% you are expected to hear crackles in the audio, because the buffers cannot be processed in time, but the "Bela" CPU usage reported is the sum of the audio thread and all auxiliary tasks (including those that service the Scope).

Is this CPU usage you report the "CPU/Bela" usage or the "IDE" ?
What settings are you using on the scope?
A very short holdoff time can easily lead to this sort of behaviour.

A detailed list of the scope parameters (and possible the code you are running), along with the revision you are running would greatly help us to solve your issue.
But I would urge you to update to the latest scope-dev branch, as a few fixes (also pertaining to CPU usage) came through in the last 5 days.