Transition from Logic to Studio one

[Remixreprogramme]

Any tips or ideas that might help the transition from Logic to studio one ?

[apoclypse]

Focus on the workflow. One of the things that took me by surprise when moving to S1 coming from Logic was that S1 felt like ti was missing so much compared to Logic (admittedly this was going all the way back to v2). But if you focus on the workflow vs what Logic does that S1 doesn't it's an amazing application.

Have a suite of plugins. If you use Logic's built-in plugins well S1 doesn't have the range or the same quality as Logic. That can be a deal breaker for some. Personally I have my 3rd party plugins so no big deal.

Get acquainted with Macros. They are super useful in S1.

[jonljacobi]

Nothing startlingly different.

[Ploki]

i demoed it last time, some things are worse, some are better.
i still feel more at home in logic. what is prompting you to switch?

[pdxindy]

i demoed it last time, some things are worse, some are better.
i still feel more at home in logic. what is prompting you to switch?

Year after year of significant Logic updates with no update cost is a compelling feature.

Especially with Logic 10.5, it feels like the Logic Dev team is really on it. The new Drum Designer and Sampler are excellent and fresh. There's still some old outdated stuff in Logic, but if 10.5 is any indication, the Dev team gonna address that stuff. And pretty fast too. A couple more updates like 10.5 and it would be hard to switch away.

If Studio One adds Bitwig style MPE editing, that would be a temptation. As is, Studio One is not quite there for me. Also, the various reports of Studio One bugginess on the Mac is a red flag.

[Ploki]

Year after year of significant Logic updates with no update cost is a compelling feature.

Especially with Logic 10.5, it feels like the Logic Dev team is really on it. The new Drum Designer and Sampler are excellent and fresh. There's still some old outdated stuff in Logic, but if 10.5 is any indication, the Dev team gonna address that stuff. And pretty fast too. A couple more updates like 10.5 and it would be hard to switch away.

If Studio One adds Bitwig style MPE editing, that would be a temptation. As is, Studio One is not quite there for me. Also, the various reports of Studio One bugginess on the Mac is a red flag.

Well I agree, but I thought OP is trying to switch to Studio One not from it.

There are some wonderful functions in Studio One - the single one that made me consider it was FX Chains. I'd kill for something like that in Logic (or Waves StudioRack that hosts AUs would be fine too).

But then I demoed it, and logic just seems faster for vast majority of operations, the new step editor for me is really really great.
Somehow, dev team manages to keep all the functionality at hand, but when you open it everything is clean and just makes sense. Nothing is missing, but nothing is in the way.
On the other hand, delay compensation for sidechain and automation delay compensation just makes me angry - i don't know how good Studio One is on this front.

[andypryce]

On the other hand, delay compensation for sidechain and automation delay compensation just makes me angry - i don't know how good Studio One is on this front.

It was OK until 5.1 but currently it is like Logic on buses but will be fixed with the next maintenance update.

[chk071]

Any tips or ideas that might help the transition from Logic to studio one ?

RTFM.

[Ploki]

It was OK until 5.1 but currently it is like Logic on buses but will be fixed with the next maintenance update.

jesus really?

[andypryce]

I guess PDC is the biggest curse of DAW makers

[pdxindy]

On the other hand, delay compensation for sidechain and automation delay compensation just makes me angry - i don't know how good Studio One is on this front.

Yup... that is one of Logics flaws... another is not being able to choose individual controllers per track.

[Etienne1973]

another is not being able to choose individual controllers per track.

What do you mean exactly?

[pdxindy]

another is not being able to choose individual controllers per track.

What do you mean exactly?

Say you want to record midi to two tracks at the same time, one played by one midi keyboard and another played by a second midi keyboard. You cannot select a specific controller per track. All controllers are active on each record enabled track. So both tracks will record the midi from both controllers.

Actually, there is a way to do it using Logics Environment, but that is arcane and clumsy. In Bitwig (and other DAWs) you can simply select a specific controller on track input. I would like Logic to add that function.

[Ploki]

Actually, there is a way to do it using Logics Environment, but that is arcane and clumsy. In Bitwig (and other DAWs) you can simply select a specific controller on track input. I would like Logic to add that function.

kinda but not really really, logic's sequencer only has a single input port, so you can't bypass that even through environment. you could assign a separate channel but that means no MPE controllers.

its whack really

[pdxindy]

Actually, there is a way to do it using Logics Environment, but that is arcane and clumsy. In Bitwig (and other DAWs) you can simply select a specific controller on track input. I would like Logic to add that function.

kinda but not really really, logic's sequencer only has a single input port, so you can't bypass that even through environment. you could assign a separate channel but that means no MPE controllers.

its whack really

Ahhh... didn't know. Someone said you could do it in the environment. I've never touched it.