Studio One 5 Available Now (5.3 Out June 29th, 2021)

[apoclypse]

oops. Double post.

[zakkk]

Im really happy with the new changes. - coming from protools to S1 is a big change, but I for one will never go back!.

[Funkybot's Evil Twin]

Just edit the Plugins-(language i.e. en).setting file and the changed names get stored there forever if you like...

If that works that's a brilliant workaround. Thanks for the tip. Will check it out. No reason they couldn't add a "right-click plugin in manager and select 'Rename' or 'Create Alias' from a dropdown" to do this on the front-end in a user friendly way though.

EDIT: This doesn't work. Manual changes to the plugin name in the plugins-en.settings file are immediately overwritten as soon as you load the plugin.

All I want is the ability to:

1. Create an alias for a plugin
2. Have that alias appear in the plugin browser and inserts slots
3. Have that alias remain

...no solution or workaround seems to do that.

[Funkybot's Evil Twin]

11. Plugin renaming!!! FFS let us create aliases for plugins in the "Plugin Manager"

Rename the plugin instance in Mixer and save it as default preset - DONE

That one gets halfway there but still doesn't do anything about how it appears in the browser. Still, better than nothing.

[Funkybot's Evil Twin]

7. Dim Solo

?

It's solo that doesn't mute the other tracks but just makes them quieter (usually like -12db). Just convenient for focusing on one track but still hearing the context of the broader mix.

https://blog.presonus.com/index.php/202 ... -dim-solo/

Thanks. This is a [very awkward and clumsy] workaround that won't work with in all setups. It's funny that Presonus acknowledge [through Craig's blog post] that it's a desirable feature and explain exactly why. Hopefully that means a proper native solution can be implemented and is proverbially "on the list."

It's not a deal-breaker by any means, I don't think any one item on my list was meant to be that, but it's just a bunch of little things that Presonus could do to improve the core-DAW functionality of Studio One.

[5Lives]

Do you have trouble reading? I explained my position. I have been doing this for a very long time. You definitely hear about things that everyone is using. I've not so much as seen it in a feature list for any DAW I have looked at. And you want to suggest it's not niche? Spare me days!

You seem to have trouble with the definition of niche. Maybe you’ve spent your 40 years working in a shed. Who knows. Clearly you’re not very clued in on what professional rooms are using. EUCON is supported by Pro Tools, Cubase, DP, and Logic (among others - pretty niche DAWs right?). There’s a EUCON device in the majority of mix / composing / writing rooms in LA. Spare us your ignorance.

[THE INTRANCER]

Since we're offtopic anyway, can you guys please upvote my FR even if it doesn't concern you?

https://answers.presonus.com/69526/let- ... ow-buttons

I know how to do that...What screen resolution are you using ?

[Funkybot's Evil Twin]

EUCON is supported by Pro Tools, Cubase, DP, and Logic (among others - pretty niche DAWs right?). There’s a EUCON device in the majority of mix / composing / writing rooms in LA. Spare us your ignorance.

Eucon makes a lot of sense if Presonus really wants to capture the Pro Tools crowd in particular. That and dual pans!

But I suspect the fact that they're trying to push their own FaderPort series of Control Surfaces means they have little to no interest in supporting Eucon. They're trying to sell their own hardware. But it's a little short-sighted IMO.

[pinki]

8. Selected events and non-selected events need better visual distinctions

What? Selections are bright white, everything else is a muted colour. It literally couldn't be any more obvious.

How is this obvious?
Screen Shot 2021-07-01 at 09.23.44.png

While I do agree that maybe things could be a bit more obvious here. In practice I've never had an issue distinguishing selected vs unselected Event clips in S1.

For example it's a bit more clear what selected or not if you have the track headers be the color of the track. So it will make that whole the event is in the same color as well.

You posted the worst case scenario where S1 didn't give users the tools to mitigate the situation. However that is not the case. This is what you are more likely to see in a session



or this:



I'm not saying S1 couldn't make things a bit clearer but it's not as bad as you are trying to portray it imo.

Actually I agree with ozinga here- it is bad, really bad. The one aspect of S1 that is poor for me is the GUI generally (messy quickly) and selection (vague) in particular.

[apoclypse]

8. Selected events and non-selected events need better visual distinctions

What? Selections are bright white, everything else is a muted colour. It literally couldn't be any more obvious.

How is this obvious?
Screen Shot 2021-07-01 at 09.23.44.png

While I do agree that maybe things could be a bit more obvious here. In practice I've never had an issue distinguishing selected vs unselected Event clips in S1.

For example it's a bit more clear what selected or not if you have the track headers be the color of the track. So it will make that whole the event is in the same color as well.

You posted the worst case scenario where S1 didn't give users the tools to mitigate the situation. However that is not the case. This is what you are more likely to see in a session



or this:



I'm not saying S1 couldn't make things a bit clearer but it's not as bad as you are trying to portray it imo.

Actually I agree with ozinga here- it is bad, really bad. The one aspect of S1 that is poor for me is the GUI generally (messy quickly) and selection (vague) in particular.

Being a longtime S1 users I guess it no longer registers as an issue for me. Maybe if I were a new user coming with fresh new eyes it would be more annoying. That's not to say that Presonus shouldn't address the issue. I was just pointing out that the issue isn't as bad as his original screenshot made it out to be. It's not great, it has some issues, but in practice it's not unusable.

[5Lives]

EUCON is supported by Pro Tools, Cubase, DP, and Logic (among others - pretty niche DAWs right?). There’s a EUCON device in the majority of mix / composing / writing rooms in LA. Spare us your ignorance.

Eucon makes a lot of sense if Presonus really wants to capture the Pro Tools crowd in particular. That and dual pans!

But I suspect the fact that they're trying to push their own FaderPort series of Control Surfaces means they have little to no interest in supporting Eucon. They're trying to sell their own hardware. But it's a little short-sighted IMO.

You may be right - though they have added support for both Console 1 and Komplete Kontrol. EUCON seems like a strange one to leave out, especially since they have been going for that Pro Tools crowd and want to be seen as an alternative there. Not to mention, if they are trying to convert professional users from Cubase and Logic, which do support EUCON.

[BONES]

The highlighted coloured tracks and mixer channels are not cleared (I mean when they are in whole colours) but I find it clear when using part colours (just the right part of the the tracks and the lowest part of the mixer channels).

So what you're saying is that people with poor eyesight, or maybe it's to do with partial colour-blindness, should choose colours that work for them? Seems like common sense to me, not something that needs changing.

If you look closely;
From thew left row Events 4 9 13 15 and from the Right row 6 13 17 19 were only selected. the rest are not selected.

We can't look closely, it's a tiny, little picture on our screens, probably around one-eighth of the size it is full-screen. But what version are you using? When I select a clip, the outline of it changes from a thin dark grey to a bolder white and I can't see that happening on your screenshot. It really couldn't be more obvious on v5.2 or 5.3.

This is what I would call obvious

I call that hideous. It also shows you nothing else, apart from the fact its selected. So are you suggesting you'd rather know what's selected than anything else about the contents of a clip? Seems a bit OTT to me.

Clearly you’re not very clued in on what professional rooms are using.

I think in 2021 that "professional rooms" is definitely a niche in comparison to the number of us who work in home studios. Probably more niche even than people producing on iPads.

The one aspect of S1 that is poor for me is the GUI generally (messy quickly) and selection (vague) in particular.

Compared to what? The thing I like most about Studio One is that it never gets messy, it's really easy to keep it all slick, clean and focused on what I am doing. In Cubase I am forever opening an closing panels and windows and there are vast swathes of the interface I never use. OTOH, in S1 I see only what I need and everything on the UI is something I need/use. Yes, there is still a bit of unnecessary duplication here and there but it's a helluva lot better than Cubase or Bitwig.

Being a longtime S1 users I guess it no longer registers as an issue for me. Maybe if I were a new user coming with fresh new eyes it would be more annoying.

No. I've only been using it this year and it has never been on my radar. It doesn't seem any worse than Cubase or Orion or Bitwig to me.

[ozinga]

Actually I agree with ozinga here- it is bad, really bad. The one aspect of S1 that is poor for me is the GUI generally (messy quickly) and selection (vague) in particular.

Being a longtime S1 users I guess it no longer registers as an issue for me. Maybe if I were a new user coming with fresh new eyes it would be more annoying. That's not to say that Presonus shouldn't address the issue. I was just pointing out that the issue isn't as bad as his original screenshot made it out to be. It's not great, it has some issues, but in practice it's not unusable.

Yes, you are right. I used an extreme example because I wouldn't call Studio One's way is obvious. I can't say it is unusable at all either. As you said it needs some refinement. I use several DAWs and Studio One is the hardest in this respect. On a busy session with lots of small regions it becomes hard to distinguish. Especially when zoomed out and shift selecting regions and trying to make sure something is selected. It is just that Studio One is default to this blue and its shades when tracks are created which are the worst for showing the difference. I get by using Lawrence's Color Tool and trying to use colors that are easier for me than Studio One default set.

[ozinga]

We can't look closely, it's a tiny, little picture on our screens, probably around one-eighth of the size it is full-screen. But what version are you using? When I select a clip, the outline of it changes from a thin dark grey to a bolder white and I can't see that happening on your screenshot. It really couldn't be more obvious on v5.2 or 5.3.

5.3 on Mac but it is like this as far as I remember.
Tiny tiny light blue border and a vague color change.

This is what I would call obvious

[/quote] It also shows you nothing else, apart from the fact its selected. So are you suggesting you'd rather know what's selected than anything else about the contents of a clip? [/quote]

What do you mean? Both S1 and Cubase show nothing on regions at this size and shows more or less the same things when tracks are larger (Waveform, notes overview, fade points, clip gain etc)

[antic604]

Since we're offtopic anyway, can you guys please upvote my FR even if it doesn't concern you?

https://answers.presonus.com/69526/let- ... ow-buttons

I know how to do that...What screen resolution are you using ?

I just want to hide those buttons. What does screen resolution has to do with this? I know I can change resolution and/or scaling and S1 will then display the full toolbar. The point is, if it decides to prioritise what's visible at lower resolution / higher scaling, then it should hide those useless buttons rather than tools one uses all the time.