Quote:
I hope the new GUI enables users to do everything the processor can do. As I mentioned on the other topic, please consider having several levels of adjustment visibility. Those who have pro version should be able access all adjustments. One person's unnecessary feature may be the reason another person purchased the software.
Anyone should be able to access all adjustments. And they should always be findable. That's why we're getting rid of the adjustment modes: you wouldn't believe how many people couldn't find a setting because it was only visible in the next mode tier up.
Quote:
The comment about the need for adjustable low pass filtering frequency on FM processing mode made me smile, because no doubt people have used an FM processor on AM to see how the pre-emphasis limiting sounded on AM. The problem was the need to apply 10 kHz filtering afterward to meet the USA FCC mask. Indeed, the adjustable low pass filter may be needed by someone, even in FM mode.
If someone needs functionality that isn't present anymore, they can tell us in this thread. But before we start adding sliders and knobs (or start programming new features), we would like to know why it would be necessary and/or of use to anyone.
Quote:
Additionally, I have not found anything in Stereo Tool documentation indicating where in the processing chain AM or FM pre-emphasis is introduced, and if it is introduced in multiple stages. Big difference between pre-emphasis before final HF clipper, or pre-emphasis before a multiband stage that precedes the HF clipper. Or if pre-emphasis is introduced on a side chain with a parallel processor.
I'll forward this to Hans.
Quote:
Does version 10 have adjustable maximum gain reduction meter scale on the compressors?
It does not.
Quote:
So far, I get the impression much of the ongoing work on Stereo Tool is changing the GUI and digital housekeeping. Any thoughts about the audio processing itself?
I'd suggest creating another topic for that. You could also ask Hans directly, he's usually more than happy to spar about new ideas with knowledgable people.
Quote:
Please find a way to make the GUI usable for all users, basic to full-tweaker. Don't take out any adjustments.
That is indeed what we're trying to achieve.
Quote:
I think one issue with the GUI may be the obtuse descriptions of control function.
We would absolutely love to have a list of suggestions for better naming and explanations! If you're the kind of user that has experience with the functionality that ST offers but that is named differently in the (un)official jargon or in other applications, please let us know so we can improve.
Quote:
When testing, it seems like compression ratios are pretty mushy. [...]
Another example- in the wideband [...]
Please create new topics for these problems. We need to know about it, but this is a thread about the new GUI only.
Quote:
You don't need to dumb down the GUI. You just need more specific descriptions of the actual processing function parameter on the GUI controls or pop-up descriptions.
We're not trying to dumb it down. Not at all. We're just trying to make it less crowded and overwhelming. It's still every bit as versatile and adjustable if one is as willing to dive into it as they were when they first started using it.
Quote:
Sadly it's still completely unusable in OBS after closing and reopening the GUI. It's still scaled up waaay too large on the second opening of the GUI, and it recursively gets larger every time.
Fixed that. I didn't properly account for DPI.
Quote:
I'm using the web interface with a screen reader, and since preset selection is broken in that case, I figured I would go with the version that works for me.
We've put an external team on that, will let you know as soon as they've figured out what's going wrong.