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

vitocorleone123 said:

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

Click to expand...

Uh... wow. Maybe you really are Vito Corleone.

Lukas is not just some chump, he's the most helpful person on this forum with regard to Studio One, and he has connections with the SO team.

He's just trying to elicit information because he wants to keep his finger on the pulse of the Studio One user base.

Again, I'm sure you weren't aware of this when you made your rude comment. Lukas was not being rude and obtuse, and I've never seen him be anything but gracious to forum users.

vitocorleone123 said:

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?

Click to expand...

You don't know who Lucas is, I bet

Lukas said:

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. 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

Click to expand...

DaddyO said:

Uh... wow. May you really are Vito Corleone.

Lukas is not just some chump, he's the most helpful person on this forum with regard to Studio One, and he has connections with the SO team.

He's just trying to elicit information because he wants to keep his finger on the pulse of the Studio One user base.

Again, I'm sure you weren't aware of this when you made your rude comment. Lukas was not being rude and obtuse, and I've never seen him be anything but gracious to forum users.

Click to expand...

This is the second time he’s come across as a touch rude to me in this thread, and yes I know who he is. I’m chalking up at least part of it perhaps as a language issue (I’m pretending English is not his first language), which is why I dropped it and gave his follow up reply a thumbs up as “good enough”.

This isn’t the friendliest thread on the board if you’re requesting things that aren’t popular/mainstream.

My wishlist goes like this:

1. Only load plug-ins needed for project playback

2. Better CPU/large track counts performance

Saving/auto-save is like being pulled through the entire London sewer system, when you have a 100+ kontakt instances in your project...

RenePedersen said:

My wishlist goes like this:

1. Only load plug-ins needed for project playback

2. Better CPU/large track counts performance

Saving/auto-save is like being pulled through the entire London sewer system, when you have a 100+ kontakt instances in your project...

Click to expand...

These are probably my top two features. I have not managed to get track presets really work efficiently past 150 tracks in the project, which is not unusual in an orchestral cue. When you drop a track preset it take foreveeeeer, hence why support for projects with large track count is important for me.

I also love Logic’s AU XPC for switching off the audio engine automatically when not in play mode or live.

And I would add a third one, related to this topic of large projects & RAM/CPU: transform to audio (render/bounce/freeze …) should have an option to render to audio the dry signal without baking in the effects. Right now all the effects are baked in when we transform to audio track.

RenePedersen said:

My wishlist goes like this:

1. Only load plug-ins needed for project playback

2. Better CPU/large track counts performance

Saving/auto-save is like being pulled through the entire London sewer system, when you have a 100+ kontakt instances in your project...

Click to expand...

I don’t understand #1. Doesn’t it do this already?

madfloyd said:

I don’t understand #1. Doesn’t it do this already?

Click to expand...

Technically yes, but it only does it for plugins, I think what was meant with this was "instruments" and not plugins. So if you have a template of 100 instances of Kontakt, and you only use 30 of them with MIDI data on them, it will unload the rest of the 70, so they do not need to be processed on every project save - And therefore minimise load times and increase performance for gigantic templates.

Am I the only one who doesn't like the fixed cc lanes of piano roll (aftertouch, pitch wheels, music symbols, etc.) that can't be hidden?

I would like to be able to hide unused lanes because they push my other lanes to the right and some of them are not easily selectable.

Edu said:

Am I the only one who doesn't like the fixed cc lanes of piano roll (aftertouch, pitch wheels, music symbols, etc.) that can't be hidden?

I would like to be able to hide unused lanes because they push my other lanes to the right and some of them are not easily selectable.

Click to expand...

By NO MEANS are you the only one. It makes zero sense to me to force users to see CC lanes that are irrelevant for their use. In orchestral work, CC lane screen real estate is at a premium.

Also, we need for custom CC-lane presets.

VSL can often employ an extensive set of CC controllers that vary by library.

DaddyO said:

By NO MEANS are you the only one. It makes zero sense to me to force users to see CC lanes that are irrelevant for their use. In orchestral work, CC lane screen real estate is at a premium.

Also, we need for custom CC-lane presets.

VSL can often employ an extensive set of CC controllers that vary by library.

Click to expand...

Totally agree, this is one of the things that drove me to give Cubase a try...

Another request that's on the Presonus boards and no one at Presonus notices: easy MIDI NRPN handling.

I can't find a way to resize this column:



I'd love to make it wider so I can always see the instrument names in their totality. It would help when selecting/deselecting tracks while in the MIDI editor.

I've resorted to giving them short names, but that isn't ideal for me because I often sacrifice information I'd like to keep (like what library they are, articulation, etc.). And even then stuff can get cut off.

If there's a way to do this already, I'd love to know how.

annexation said:

If there's a way to do this already, I'd love to know how.

Click to expand...

It's not yet possible.

annexation said:

I'd love to make it wider so I can always see the instrument names in their totality. It would help when selecting/deselecting tracks while in the MIDI editor.

Click to expand...

I fully agree.

MIDI routing is also too rudimentary.

Someone with multiple MIDI outs out to be able to send any note anywhere. Or, say, set C4 to go out MIDI2 Channel 4 and D4 to go to MIDI3 Channel 12, etc. Or even just C4 is MIDI2 Channel 4 and D4 is MIDI2 Channel 5.

Even a less expensive DAW like Tracktion Waveform comes with DAW utility plugins to route MIDI. As far as I can tell, you have to create a separate Track for each MIDI channel in S1.