Source
r/StudioOne•
SycopationIsNormal

Track Transform

I use the "transform to rendered audio" option (https://www.pro-tools-expert.com/studio-one//transform-to-rendered-audio-track-freeze-in-presonus-studio-one) in S1 quite a bit because I use a lot of instruments (softsynths, particularly u-he synths, and some Kontakt libraries) that really eat up my processing power. I’m still on S1 v2 and the behavior of using this option kind of annoys me. I want to make sure that I’M not doing something wrong here.

​

So if I only transform once, everything is cool, works just fine (and I never render the inserts). It’s when I have to undo it to change something (tweak an instrument parameter, move MIDI around etc) that I have problems. I often find that any automation I’ve written on the track gets erased. The track also gets moved in the console. It will usually end up getting shifted all the way to the right. And the color that I gave it originally will be gone (turns to white). The lst two things are minor annoyances but the automation thing is extremely annoyng as I tend to mix and add effects as I compose.

​

Is there anything I can do differently to help solve or at least mitigate these issues? Has anyone else had the same experience? And were these issues fixed in later versions?

​

Thanks.

Posted Feb 8, 2019, 4:45 PM UTC

210
m0nk_3y_gw•

I don't have personal experience with it -- I would report it to Presonus as a bug and start doing a full track duplicate before rendering to audio (i.e. keep the original instrument track as a disabled track, so it is easy to re-render it and then drag it over the track that has the additional automation work on it.

2
SycopationIsNormalOP•

keep the original instrument track as a disabled track

But does this disable the instrument and therefore give me the CPU advantage that I'm seeking by doing the transform in the first place?

I'm not quite sure what you're saying. So I bounce the track to audio, then track transform the original track (that contains the VSTi) and then do my automation on the audio track?

"I would report it to Presonus as a bug" - Do they actually fix prior versions? The main reason I'm still on v2 (aside from the expense) is that I just don't want to deal with the work / hassle of installing it, learning it etc. I probably will eventually, I just have no desire at this point (I'd rather just focus on making music). I'm just curious if it's been fixed in later versions as it might finally help motivate me to upgrade to the latest version.

1
IIIllII11lIIl11IIIl•

Don't be surprised that a major feature of the DAW is ostensibly not QA tested whatsoever. I've had the program crash when doing any kind of quantization on audio - just had to export and do it in LPX, which makes me want to die (fuck LPX).

Welcome to S1

:)

1
SycopationIsNormalOP•

LOL well hopefully the issue got / gets addressed in later versions. I'm still stuck on v2 because I'm lazy.

And it's not usually an issue. I usually try to strategically transform those tracks that 1) have a high CPU hit and 2) I am unlikely to want to change later.

That way I can usually avoid transforming things like a lead synth that I know I'll want to do a lot of fine tweaking to with automation later in the composition process. So it's usually not a huge issue. But it is occasionally annoying.

2
amadeusex72•

I actually tried to freeze multiple audio tracks on a medium sized project (80 tracks) and everything went smoothly on S1 v4.1.3.

It might be time to dive into the update fellow stranger :)

1
SycopationIsNormalOP•

OMG 80 tracks is a MEDIUM project?

If I only freeze once, everything is cool. It's undoing it that is the problem.

I'll probably upgrade eventually. Just waiting for the right time.

1
amadeusex72•

Yeah I get that - I meant to say that unfreezing worked just fine.

80 tracks isn't really that much. The fun begins with 150 upwards. :)

1