What are your top Studio One feature and improvement requests? [Now with poll]

I've added a poll of the combined and updated list of feature requests. You can vote up to 15 different options. (I made a mistake on the poll question and put 5. Have asked mods to edit it)

<EDIT> I misread the request. Apparently the poll is new? (I thought it had been here for months and was just being modified.) In that case, I edited the title to say 15.

"Apply Track Names to Instruments" already works with this script:
Shared Add Ons
"Track Presets to store Drum maps" works since Version 6.2

"Apply Track Names to Instruments" is also included in the latest version 1.5 of Navigation Essentials.

This command also takes into account instruments that are assigned to several tracks and then informs about this instead of renaming the instruments incorrectly.

That's so cool, I need to remember to check your script versions @Lukas I wasn't aware you kept updating Navigation Essentials too. Now it shows on the Find Command, which is the best shortcut ever. Thanks a bunch.

Aren't the poll's percentages all over the place? They definitely do not add up to 100.

EanS said:

That's so cool, I need to remember to check your script versions @Lukas I wasn't aware you kept updating Navigation Essentials too.

Click to expand...

I try, as far as my time permits.

EanS said:

Now it shows on the Find Command, which is the best shortcut ever. Thanks a bunch.

Click to expand...

That's good to hear. I created the concept for it back then.

Lukas said:

I try, as far as my time permits.


That's great to hear. I created the concept for it back then.

Click to expand...

So thanks again, because if it's not in the Macros, it's in G1 (Corsair KB has 6 Elgato Keys) so it's organized like this



Then on mouse with 6 Buttons

Mid click = , (go to song start)
One side button to FF
One side Button to RW
One side button to scroll the mouse tools
And two side buttons for these macros.



Pair with F1-F12 keys and numeric KB for Markers and voila, it's almost all there, the rest goes with a Faderport and/or Midi Controller's Transport Controls.

Now I need talent, which hope it comes with next update.

Olympum said:

Aren't the poll's percentages all over the place? They definitely do not add up to 100.

Click to expand...

They're not supposed to add up. Everyone can choose as many as 15 features from the list. If, for example, everyone chooses exactly three, the percentages would add up to 300%. But different folks check different numbers of boxes.

Pretty comprehensive list - well done. I see a bunch listed that I have suggested over the years (and I'm not the only vote for them! Who would've thought.).

as much as I appreciate Lukas products I am not happy to see many "good ideas" not as a "standard" feature in "S1Pro" ...
(they should hire Lukas permantely and go forward with ideas ...)

Probably unsurprising the top three request areas so far seem to be:

CPU/large track count performance

CC automation lane improvements

Sound variation improvements

Although the first of those is probably two issues in one. CPU and large track count performance aren't necessarily the same thing.

Studio One's poor large track count performance, with painfully slow track visibility, is quite frustrating.
Cubase is still king here. Perhaps Presonus could (also / finally) use graphic processing power to speed things up?

customizing clicks for meters of 5 and 7. DP did this over 10 years ago. Logic and Cubase also do it now. It’s crucial that when subdividing beat emphasis on this time signatures.

Missing from poll: MIDI 2.0
(separate but related to MPE, I suppose)

vitocorleone123 said:

Missing from poll: MIDI 2.0

Click to expand...

Which exact MIDI 2.0 feature(s) do you miss?

Lukas said:

Which exact MIDI 2.0 feature(s) do you miss?

Click to expand...

I don’t have MIDI 2.0 yet but will get a controller within a few months. It’s more that I’d like my DAW of choice to be fully compatible ahead of me using it. Maybe it already is and they just need to check that box, so to speak.

So you don't have a specific need for MIDI 2.0 and don't know if MIDI 2.0 would bring you any advantages? You just want the DAW to be able to do it in case you ever need it?

I'm just trying to understand the specific user story behind the feature request. At the moment, I don't see it yet.

Lukas said:

So you don't have a specific need for MIDI 2.0 and don't know if MIDI 2.0 would bring you any advantages? You just want the DAW to be able to do it in case you ever need it?

I'm just trying to understand the specific user story behind the feature request. At the moment, I don't see it yet.

Click to expand...

Is that what I said or are you just being obtuse?

This isn’t hard to understand. I’m getting a MIDI 2.0 controller and want to take advantage of what it offers on as many things that support it, which requires a DAW that supports it. Why would I want to wait if I don’t have to?

One main benefit of MIDI 2.0 is the higher resolution of parameter values. Studio One was designed from the ground up to work with a resolution much higher than 128 MIDI steps. So there is only a small functional gap (if any) to fill. Of course, this is just one aspect of MIDI 2.0.

The word is thrown around a lot, but when you ask people what they expect and need from MIDI 2.0, you usually don't get an answer. When someone does ask for it, I wonder what the exact need or application is. So I ask.