Stereo Tool

If the multiband (individual band) hold control is to be removed, please reconsider. I use this control because I don't want to change gain unless it is necessary or desirable. I purchased Stereo Tool precisely because I want a large number of user adjustments and maximum flexibility to implement processing structures. If the product is simplified I will not be particularly motivated to purchase more licenses.

Please leave every control in the product and consider adding more. You can simplify it by having layers of access in the GUI just as the Orban and Telos Alliance products do.

As you suggested I will eventually suggest control descriptions from my point of view.

btw- could you please clarify the location of Bandpass section in the signal flow. Presumably low-pass filtering for the AM and FM outputs is in the output section. Therefore, Bandpass would probably be after the Repair section, but before the Auto-EQ section. Is the low-pass of Bandpass actually adjustable? You can appreciate that some users might want to remove frequencies that will not be transmitted before Auto-EQ or Multibands can act on them.

Also, this a really big ask but for users with multichannel sound cards, could you consider a comprehensive monitor section?

When a processor is on the air, it helpful to have a monitoring output that can be easily switched between input, output and a bridging tap of every significant point in the processing path. That way the user can hear what (for example) what the output of a mid-band in the compressor sounds like, or exactly where some pumping or objectional artifact is coming from. Most of the time these things are noticed on-air, and if the user is physically next to the PC, they could easily zero in on why a particular song is not working with the processor, by comparing input, output and bridge-tapping sections.

Thank you !

By "Hold", do you mean Release hold? That's under Release. Just click on the open ">" symbol next to the word Release and it will appear.

We are not removing any settings. Well, we removed 8, which were really useless.

btw- I like the sophistication and user adjustability of the bass clipper in the Advanced Clipping section. But to me many of the control descriptions are cryptic. I don't want to "reduce bass when mids and highs are present" since that implies a frequency response change. But I do want bass clipping threshold to move between two user adjusable points dynamically.

Like probably hundreds of other users, I would like for my bass clipping threshold to dynamically rise to a higher level when only bass is present in the audio. That is, a user might want to clip bass at - 3 dB when mid and high frequencies are present, but clip bass at - 1 dB when only bass is present. Or the bass clipping threshold could remain fixed at user adjustable point and the aforementioned dynamic action could produce make-up gain. That is a subtle difference, and a user might want that choice.

Ideally there would be a "cross-coupling" style matrix to determine how higher bands are summed to produce the control voltage.

The time domain-based bass clipping controls are fantastic. Please leave them in. Actually, all Stereo Tool time-based tweaks are great. It's a wonderful palette for creating sound.

A thought for the AM version- Unless it is integrated into your clipper in a proprietary way, make the "NRSC style pre-emphasis" a PEQ style user GUI. That way the curve could be tweaked. Also, the AM low pass filter might also have a "FCC mask compliant" setting, or other slopes. Here's why- If the user has already cut off above 10 kHz on the input side bandpass, how much low pass do you need on the back end? Maybe I am asking a personal question about your clipper, but can you blame me for wondering?

On the back end 0.25 db and 0.5 dB changes are significant. Any fixed curve or uncertainty is not helpful. You've got an advanced limiter/clipper and then a final limiter/clipper providing an absolute peak ceiling. The difference between the thresholds of those two appears to be adjustable, but it is evidently described as headroom. Would you consider describing as "absolute peak ceiling clip threshold" and "advanced peak clipper threshold" both referenced to digital full scale at the output bit depth? Then users can set their margin accordingly.

All that about bass clipper in "clipper" is possible and it's right there. Question is do you really want it like that. It's there to minimize distortion/imd caused by bass. You need atleast 3dB dynamicaly to go down and sometimes even more depend on how loud is general output and how much you want to trade distortion for loudness. Also you don't want it at 100%, even if only bass is present, since it can interfere with pilot and RDS, so you maximum want it at around 85%. But sure you can really set it however you want.

_________________
control point
control point2

Those clip threshold dB values I mentioned were for example. I know about the pilot and composite signal stuff and the distinction between a processor for audio such as mastering, mono AM, streaming, HD Radio, and a processor for analog FM stereo. Considering the different customer applications and subjective expectation, it is challenging to make a processor that makes everyone happy.

Thank you for developing Stereo Tool.

Yep, that is what i mean. And thanks for pointing me out. I knew there is "something":)

Here's a handy tweak that AFAIK isn't documented outside of this forum. You can expand all cells and fill out the page with settings sorta similar to old UI by pressing CTRL-SHIFT-+
In other words, it's CONTROL+SHIFT+PLUS, and it's best in common with a low scale factor and compactness if you want to fit as much on screen as possible.

I use this when I know there's a setting but I can't quite find it. I still think a search would be amazing, but it's important to focus on one thing at a time.

Wich proves that newGUI is not ready, that people can't find where is what.. meaning OldGUI should be still alive.

_________________
control point
control point2

Do you mean it won't be ready until a search is implemented? Cause guess what, all new things take time to learn. It's been available for months, and that's on you for not learning it or contributing to it and helping turn it into something you'd use. They gave us plenty of time before they had to force their hand.

Things take time to learn, i agree. But trust me, every time i open newGUI i see something new wich is not how it should be. I forced myself to make it to look and function 'OK' to me, but it's not at all.
And i already said what i had to say. So it's not true i did not 'contribute'! I can't say more since this new gui is wrong in CORE, it's in state where you cannot fix one thing and suddenly everything will be fine.

_________________
control point
control point2