Stereo Tool

I give my opinion, Stereo Tool in 4K resolution! what's the point?

Having text and buttons bigger than a milimeter on a 4k screen.

Well, it never happened before beta 42 when the default 4k window size was fixed and the line spacing was changed. The odd thing for me is that it seems to happen randomly. I currently experiment with negative (-1) or small (0.0001) positions to see if it makes a difference.

Ok this is in one of my latest changes. Does it happen immediately after starting and have you ever had NAN issues before? The code looks fine, the only thing that I think could have triggered this is a NAN error. I can easily put in protection against that - but if it's not that I might be hiding some other problem and cause bad behavior.

The address looks like it's NOT a NAN error though..... I'll investigate more, must be overlooking something....

Till now, all systems go... modern skin... nice thou...

Thank you Hans...

same problem here windows 10 64 bit beta 046

Hans,
It happens immediately after starting. I haven't tested a Beta in a while so have not experienced any errors before.

C.

Btw with the new skin the white median line/dots for MB are almost invisible on the powder blue (or whatever you call that color) level bars.

Hi,

just a tip: since there are a lot functions to show in gui of ST (and still growing), is it possible in the near future to re-arrange or shrink the position of oscilloscope? I just don't see a reason that
oscilloscope needs to fill almost entire lower part of the screen?

BR.

FYI: I received a preset from someone which causes the crash that several people have reported within seconds on my system. Unfortunately only in release mode (and only in 64 bit mode). I've been trying to fix it today, but it's not easy - the code looks fine, and adding logging makes it not crash... I am getting closer though, I've added one line of code that makes it not crash, next step is to find out what exactly in that line is causing it not to crash.


Edit: Very odd. It starts to appear like

1 + maximum(something, -0.99999)

can be smaller than 0. But only in 64 bit mode, and only in a release build.

maximum(0, 1 + maximum(something, -0.99999))

works fine.

I'm starting to suspect yet another compiler bug.......