• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Height of automation lines?

To the OP's point, scaling autonation vertically makes all too much sense and should be there. 👍

Has Henrik [OP] or anyone FR'd this?

No, I haven’t requested it. The thing is, over the past 20 years I’ve suggested a lot of improvements to plugin and DAW developers—many of which ended up being widely adopted. But honestly, the time and effort it takes (for free) is starting to wear me down.

The bigger the company, the more patience it takes—and the harder you have to push to get a request noticed. The gap between the user and the actual developer is often filtered through layers of decision-makers who aren’t necessarily prioritizing quality improvements. More often, they’re focused on short-term revenue goals.

Presonus is a good example. They have a very strong 'firewall' around user requests. And to be fair, I get it. They’re running a support function, managing tickets, and not everyone on that end is as invested as we are. For them, it’s a job with KPIs to hit—not a passion project.

I get more appreciation and enjoyment from working (for free) with smaller developers. Less turnaround time. Product improvements in just days or a few weeks. More recognition.
 
Last edited:
No, I haven’t requested it. The thing is, over the past 20 years I’ve suggested a lot of improvements to plugin and DAW developers—many of which ended up being widely adopted. But honestly, the time and effort it takes (for free) is starting to wear me down.......
I can appreciate everything you mentioned. Same FR experience here. I've even offered to post others FR's and occasionally have. I no longer do that. I hate to say it, but I'm bushed. Even the visability of such FR's are so deep in the minutia, it's no longer a time I'm going to invest in. There are a few good sources here that can grab the baton if they support the need. They'll know what to do.

As for the size of the company, you're also correct. I think in the case of Presonus, its largely the complexity, do's and dont priorities and timing. They mean well, but its been my experience some of the motorsaporandai they won't budge on. In this case, its more of a common UI scaling convention that likely could be implemented. Easy on complexity, and makes sense on application.

I'm glad you posted "Height of automation lines", and I'm all for enhanced scaling. 👍
 
Last edited:
Voted, thank you.
 
Nicely done, added my vote.
I see the the F/R site has had a makeover.
"At PreSonus, we care about the needs of our users. Let us know which features you would like to see us implement next. Your feedback and comments are highly appreciated" !

Left a small post-it note in support.

Best regards
 
  • Like
Reactions: AAV
Voted too - great idea, well described. Thank you Dave
 
I found a somewhat okay solution for when doing:
  • channel fader (volume) automation
A.O.M. has a free plugin called Triple Fader which is suitable for volume automation.

Its faders can be calibrated, meaning you can set a range of dB the fader handles. When set to +- 6 dB, it has the same effect as if you could zoom the automation lane. The adjustments are now visually much larger, and therefore much improved, which is exactly what we discussed in this thread. If you calibrate it to 1 dB, the adjustments are visibly huge.

It has three faders and it loads default with 30 dB, 6 dB and 1 dB faders.

You can recalibrate them at any time.

So, instead of automating the built-in Studio One channel fader, you place Triple Fader last on the channel and use it (or any gain plugin). Incorporating it into a mixing template is of course the way to go.

There is also a bonus by having this secondary layer of automation. The Studio One channel faders are now free of automation and can be freely adjusted.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Back
Top