Stereo Tool

I already knew I introduced a regression when I pushed the changed that caused this... Should've asked Hans to hold off. My bad.

I've been trying to consolidate the code behind scaling for single meters, double meters and actual scale numbers.
The goal is to make their start, end and steps easier to implement and clearer in code.

However, I didn't realise the scope of how much (seemingly unrelated) stuff was inferred from these values. Like coloring, inversion, etc.

Will try to fix it before the next beta.

If by "FM bar" you mean the meter for the output (that we call FM Output), then it shouldn't be darkened/disabled when you're still using it. Regardless of the state of the transmitter.

An output is an output. If you're using it, the gui should tell you about how its doing.

Could you DM me a screengrab to show me exactly what's happening?

Have thought about moving back, honestly. Not the worse place in the country. California's prices are sky high for example.

992-BETA002 posted. Meters should be ok again, FM stuff in the meter bar is hidden if FM isn't enabled.

Feedback wanted: For meters with a small range, we have now added scale values for every 3 dB instead of every 6 dB. I'm not sure if this is clearer (it does make the direction of the scale clearer, at least) or not (because you might have less visual cues that the range is smaller).

Edit: BETA002 had an issue with meters showing a percentage, BETA003 is ok again.

This last beta033 still make window smaller and smaller every time it's minimized and restored.
Still zoom is not remembered after old GUI.
beta003 also disables Reset, load, and Save in Old GUI, i can't fix this now! Skin background is PINK in old GUI after New GUI. AGC is green instead Yellow.. other colors are odd too.
Old GUI 9,91, when you click "Full screen" twice, it does not bring back previous window size.

Edit: Somehow reset, load, save works now in old gui, but still bugged skin(s). It was all fine until i started New GUI. I done factory reset still bugged..
Now i deleted ini and skin still bugged. And yesterday 9.91 worked just fine..wth !? I'm confused.

Edit2: somehow i fixed it. I'm not touching new gui for some time.

_________________
control point
control point2

Can we get the 10s integration as a part of the ITU meter, or an option to select between the long-term integration and the 10s integration for display?

There's no way to bypass the processing while using the WEB GUI remotely. If a primary button is out of the picture, perhaps placing a bypass on the Processing Overview popup would be sufficient?

Add /st after the port number and press the bypass button on the old web GUI.

Yeah, I don't (usually) work during the weekend and didn't have time this friday.
Working on it right now, should be fixed in the new beta.
As I explained, the issue lied in the old gui removing the setting. If you're not on the newest beta of the old gui, the version you're using will keep removing it.
We didn't touch any of that code. There's no presets with pink backgrounds, so I have no clue what's going on.
Window state tracking in the old gui is a mess, that's one of the reasons why we're building a new one.
Well that's too bad, you do kinda bring in all the good bugs

It looks like this has always been broken. I went back all the way to version 9.50 and it does the same thing. I think there's a bug in the DPI size handling, anyway, it's the old GUI so we're not going to fix it anymore.
Loading and saving tries to load and save things based on where you are in the GUI. The location in the GUI is of course different in the old and the new GUI. Because of that, you're coming in on an invalid (empty) page, which is something that we never took into account (and have never before encountered). I can actually still load and save in this situation, but it's untested and kinda undefined behavior. If you encounter this, please go to a valid page first, my expectation is that that will fix it.

The ITU header has two meters.
The first one has the 'entire program' (long-term) variant.
The second meter is a double one: the slow moving part is the 3-second measurement, the fast moving meter is the 400ms measurement.
We'll look at that, we'll probably place the button in the navigation bar before the next beta.