Solved Pipeline Prevents Automation from Working When Rendering Master File in Real-time

[dlsmusic]

I've been trying to troubleshoot an issue with a guitar track that uses TwoNotes Genome. I have some parameter automation on the track as well as an instance of Pipeline to use an external hardware effect. The automation works as expected when playing back the track however, the automation stops working when updating the mastering file. It does the same if I try to transform to audio.

I've read some issues regarding Pipeline in the past. Has anyone had this type of issue?

 

[ianaeillo]

Is it just that particular plugin or others? Is pipeline before or after the plugin? What parameters were you trying to automate? Stereo or mono pipeline? I’ve never had an automation issue with pipeline but do have a spot of free time today and can see if I can replicate it over here!

 

[dlsmusic]

Is it just that particular plugin or others? Is pipeline before or after the plugin? What parameters were you trying to automate? Stereo or mono pipeline? I’ve never had an automation issue with pipeline but do have a spot of free time today and can see if I can replicate it over here!

Hi! Thanks for your reply! I'm using TwoNotes Genome and Pipeline mono. I had a delay bypass automation as well as a TwinTracker bypass automation. Pipeline is before the plugin. If I bypass Pipeline, it accelerates the rendering of the master file as expected. However, if I have Pipeline engaged, the automation works in playback, but not during real-time rendering. I also tried Transform to Audio and it does the same thing.

PreSonus has been helpful and did get back to me and said that Pipeline will be using a lower latency setup so when this is activated it will disable some plugins to keep the CPU consumption down, so this will bypass plugins in your song file. I asked for clarification since I didn't understand the statement.

 

[ianaeillo]

Hmmm i don’t understand that explanation either. Automation works after pipeline mono over here. Let me download a trial of genome and see if I can reproduce. I’m finishing up work for the day but will get to it shortly!

 

[dlsmusic]

Thanks so much for looking into this! I heard back from TwoNotes and they told me they were able to reproduce the issue on their end. Automation works with Pipeline during playback but does not work when rendering the master file in real-time (which is what you must do if you have Pipeline on any track). Still waiting to hear back from PreSonus with an explanation of what they were saying.

 

[Craig Anderton]

I think what PreSonus might be saying is to make sure low latency mode isn't active. Try turning it off (Options/Preferences > Audio Setup > Processing) to see if that solves the problem.

 

[SwitchBack]

How much time does it take to update the mastering file? Songs using pipeline must/will use real time processing where maybe updating the mastering file ignores that. If so then the pipeline plugin (and the outboard processing) won't work.

 

[dlsmusic]

I think what PreSonus might be saying is to make sure low latency mode isn't active. Try turning it off (Options/Preferences > Audio Setup > Processing) to see if that solves the problem.

Thanks for chiming in Craig! I never use the low latency setting, so I don't think that's the issue. TwoNotes has confirmed the issue on their end so perhaps it's a compatibility issue with Genome and Studio One. I'm still waiting to hear back from them regarding a possible fix

 

[dlsmusic]

How much time does it take to update the mastering file? Songs using pipeline must/will use real time processing where maybe updating the mastering file ignores that. If so then the pipeline plugin (and the outboard processing) won't work.

Thanks for your reply. Yes, since I'm using outboard gear via Pipeline, the master file update is happening in real time. Studio One automatically forces that selection. You don't have any other option which is good
I tried getting around the issue by Bouncing the track as well as Transform to Audio but both options result in the same issue whereas the automation isn't working.

 

[dlsmusic]

Been working with the PreSonus helpdesk on this issue but so far, haven't been able to solve the problem.

 

[lokeyfly]

How much time does it take to update the mastering file? Songs using pipeline must/will use real time processing where maybe updating the mastering file ignores that. If so then the pipeline plugin (and the outboard processing) won't work.

Yeah, that's my take as well. Workflow depending, I would print (render) the pipeline track with automation to simply work as intended, timing wise. Don't want to make that permanent? Then copy complete the track, so the OP has the automation if further editing is needed.

Updating the mastering file in my mind requires solidifying the tracks first, but I could be missing the intent here. I think "updating the mastering file" could use a little further detail. JMO, thx.

Do you mean when updating, by exporting a new mixdown? Exporting to a project?
For both, you should be stamping first. Not for automation. That will export timing wise, just fine. For Pipeline, no. That's not something I'd expect. Perhaps it's possible by some low latency setting. I just wouldn't expect that to happen for best case timing.

 

[dlsmusic]

Yeah, that's my take as well. Workflow depending, I would print (render) the pipeline track with automation to simply work as intended, timing wise. Don't want to make that permanent? Then copy complete the track, so the OP has the automation if further editing is needed.

Thanks for chiming in lokeyfly. Rendering the Pipeline track has the same issue; the Genome automation doesn't work

Updating the mastering file in my mind requires solidifying the tracks first, but I could be missing the intent here. I think "updating the mastering file" could use a little further detail. JMO, thx. Do you mean when updating, by exporting a new mixdown? Exporting to a project?

I'm using the term "Updating the mastering file" because that's what the command is in the Song page: Song>Update Mastering File which - as you point out - is the file used in the Project page.

After communicating with the Genome plugin vendor, Twonotes, they've concluded that the issue is with the Genome plugin itself. They've confirmed the issue. Automation works fine when using Pipeline along with native or other third-party plugins, just not with Genome.

I've updated the thread to SOLVED

 

[lokeyfly]

Awesome, dismusic that it's solved. Ok, update as per the Song page. That was one of the possible choices, only I was looking at it from the song page.

Hey, good deal. I just saw "solved", and was going to delete my question.
I'm glad it's sorted for you.