Questions & Answers

Transform to Rendered Audio issues

0 votes
1,347 views
asked Apr 16 in Studio One 6 by renatosegundo1 (850 points)
edited Apr 16 by renatosegundo1

The automations made on the fader are not maintained when using the "Transform to Rendered Audio" option, making it necessary to add a panorama plugin, for example, for the automation to be rendered. This option also does not render sidechains and, sometimes, settings made in third-party plugins are not maintained when we revert the rendering to the original state with the "Transform to Realtime Audio" option.

I have a very large and CPU-heavy soundtrack mixing project, but I simply don't trust "Transform to Rendered Audio" for fear of losing my plugin settings, automations and many sidechains. Something that is so simple in other DAW's is terrible in Studio One.

In the link, I recorded an example video of how these problems occur.

2 Answers

+1 vote
answered Apr 17 by timothyerk (810 points)
I have had so many issues with transforming audio, including what you mentioned. My other issues include:
1. If you render a mono file/event on a stereo channel that has the Splitter instantiated as a plugin, and you try to transform back to realtime, the result is messed up. It's destructive. This may only be the case when the session has been closed and reopened.
2. When I transform audio that previously used ARA (confirmed with Melodyne, RePitch, and Vocalign), it imparts some digital artifacts in the audio. Bouncing the event also make a digital click at the beginning of the event. The click will move and follow if you adjust the beginning edge of the event. I get the sense this is a CPU based bug since I only started experiencing this after moving to an AMD Ryzen 9 machine.

Studio One 6, in general, has been riddled with so many bugs that I'm ready to go back to Pro Tools. Or just go back to version 5 and never upgrade.
0 votes
answered Apr 20 by pr3lud3productions (310 points)
So instead of using the "transform to realtime audio" have you considered using mixdown "selection" and the disabling the plugins on the other tracks and hiding them in mixer view? it may just be a workflow issue as i do understand the method you are using but with using "mixdown"selection the effects are rendered with the automations just fine. Gregor explains different types of rendering here
...