• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Studio Pro 8 Mixdown and Automation issue

Midiboy

Midiboy

Active member
I ran into my first issue with Studio Pro 8 today. Panning Automation is not coming through when mastering. It DOES work when freezing the track. Also had a track where the sustain pedal didn't work in master, but only on ONE track where all the others worked. I had to freeze that track too.

Any thoughts?
 
There have been multiple reports of automation on MIDI tracks not reading when transferring unrendered tracks direct to the Project page. Most Rendered automation seems OK. After the dust settles, this may get resolved.
And you may get more interaction if you move this to the V8 discussion thread.
 
To add to the point @OutrageProductions made, it seems the song (session?) needs time to load up all cached audio (automation renders...), but that time isn't granted when pulling a new master from the project page. Is the issue also present when sending a master from a session to a project?
 
To clarify, I didn't master it to the Project Page. I just ran a Mixdown with Mastering presets in the Master channel. However, this same thing happens whether or not I have the mastering FX on or off.
 
Wait....what?
 
I mean you might be the victim of a mythical bug that popped up around SO3 point something, which excludes some automation moves from the mixdown. This was never solved. I think I actually saw a recent post about this in the forum.
Does your export dialog box "freeze" at any moment during the process?
Also If you export in real time, and the automation does get printed, pretty sure it's this bug.

There is even a script file that some user gave me years ago: you execute it through Autohotkey and, when you start exporting, it shakes the dialog box with the cursor every few seconds.
 
Last edited:
You. Have. Got. To. Be. Kidding? That's....hilarious that that is an actual known workaround. How on EARTH did anyone figure this one out? And more so, how on Earth has it not been fixed yet if this has been going on since V3? I've been using S1 since V3 and have never had this happen to me until now. There has to be some weird thing that is tripping it up...if it was more random, you'd think I would have encountered it. I use automation is every song and have released at least 12 full albums since v3.
 
IIRC (and I could be wrong) but this only occurred on a miniscule subset of Mac (?) installs, and was not completely confirmed as reproducible by the experts. The script was built by a user as a work-around. Something to do with GPU interaction.
But... Cunningham's Law may be at work here.
 
Ah. That makes more sense. I'm a PC guy. But maybe the issue decided to pop up and say "Hello" for PC on this new release.
 
Midiboy said:
Ah. That makes more sense. I'm a PC guy. But maybe the issue decided to pop up and say "Hello" for PC on this new release.
Click to expand...
Just guessing, but you may want to check that your DotNet and MS Visual C++ redistributables are up to date. [Create a Restore Point first].
 
I just updated my VC++ last night to fix the Vegas issue that version 8 created. My .Net is always pretty much up to date as I stay on top of that as I do side work for a major FX company that needs us to stay on top of that stuff to test their product. But, that is GREAT advice for all! I'll have to check the mix down now that I did update VC though!
 
Midiboy said:
I just updated my VC++ last night to fix the Vegas issue that version 8 created. My .Net is always pretty much up to date as I stay on top of that as I do side work for a major FX company that needs us to stay on top of that stuff to test their product. But, that is GREAT advice for all! I'll have to check the mix down now that I did update VC though!
Click to expand...
In that case, I'd send a support request in with a system dump. And be patient cuz I'll bet their inbox has been inundated.
 
Another thought, and forgive me if redundant, but have you toggled the automation track on Master to/from <Read>?
 
OutrageProductions said:
IIRC (and I could be wrong) but this only occurred on a miniscule subset of Mac (?) installs, and was not completely confirmed as reproducible by the experts. The script was built by a user as a work-around. Something to do with GPU interaction.
But... Cunningham's Law may be at work here.
Click to expand...
Definitely wrong on the Mac part. This gremlin has been chasing me through 3 or 4 different setups (different interfaces, PCs, OS versions) in the last ten years. All of them Windows.
Several years ago, a guy took matters in is own hands and spent weeks trying to reproduce it, finally succeeded and the bug was logged in.
At this point, whoever needs to know about it, knows about it. The subject rises on the forums from time to time.
It is my guess that this bug happens waaaaay more than people realize, it just goes unnoticed because sometimes it affects really subtle volume automations and things like that.
This (and just a couple minor things) is why I don't use SO for any professional work in spite of it being my favorite DAW by far.
Sorry for the negativity, this matter is kind of triggering for me. :LOL:
When you get to this point, I don't think the "burden of proof" should be on the user anymore.
 
bailatosco said:
Definitely wrong on the Mac part. This gremlin has been chasing me through 3 or 4 different setups (different interfaces, PCs, OS versions) in the last ten years. All of them Windows.
Several years ago, a guy took matters in is own hands and spent weeks trying to reproduce it, finally succeeded and the bug was logged in.
At this point, whoever needs to know about it, knows about it. The subject rises on the forums from time to time.
It is my guess that this bug happens waaaaay more than people realize, it just goes unnoticed because sometimes it affects really subtle volume automations and things like that.
This (and just a couple minor things) is why I don't use SO for any professional work in spite of it being my favorite DAW by far.
Sorry for the negativity, this matter is kind of triggering for me. :LOL:
When you get to this point, I don't think the "burden of proof" should be on the user anymore.
Click to expand...
Thanks for the clarification on the platform affected.
I had just read about the issue in passing, and since (at least on V7.x.x; haven't actually done the V8 upgrade yet) I have NEVER experienced any failure in Automation being passed through to the Export. And I have always done some bizarre and/or subtle automation moves in both plugs and Vol/Pan/Bypass/Mute/MIDI without ANY issues.
The indication that this is popping up for a subset of users (again) in this new version supports the concept that it may be extremely difficult to replicate by the coders.
I would really recommend forcing a System Dump file and send it, along with an offending project file, as a support request. The more submissions they get that point in this direction should increase their scrutiny and solution.
 
OutrageProductions said:
Another thought, and forgive me if redundant, but have you toggled the automation track on Master to/from <Read>?
Click to expand...
Thanks for the suggestion, but I do not automate the master track ever. Only busses and tracks themselves. However, yes, I always make sure they are set to READ, and plus, it works in playback no problem. ONLY during mixdown does the issue happen.

I find it interesting that moving the Mixdown progress window seems to help. That actually blows me mind on why that would fix it. I'll have to try that....but that still seems...really odd. Plus, this is the first time this has ever happened to me.

I did workaround it by freezing the tracks though. Which isn't the BEST option, but it's a workaround none-the-less.
 
Midiboy said:
I find it interesting that moving the Mixdown progress window seems to help. That actually blows me mind on why that would fix it. I'll have to try that....but that still seems...really odd. Plus, this is the first time this has ever happened to me.
Click to expand...
I've been through this thing also and sadly I can't give you any solution. On my side, this occured between V3-V5 and went away between V5-today. But I had the exact same behaviour, needed to move the frozen export window to get the automation.
I had very, very long conversations with the support about that. The typical starting suggestion was to remove every plugin and try to reproduce the problem with a single automation. Which (of course) wasn't the problem because it only occured during complex projects which didn't render with 50x speed in 10 seconds.
I've also stopped the time when the export window started to freeze (somewhere around 1 minute of rendereing time) and this was the exact moment after which the automation didn't work. So it seemed to me like some timeout issue, maybe multithreaded, don't know how the rendering is distributed during offline renderings. But the problem was, the support refused to test it with one of my songs, because my projects used 3rd party plugins and they wanted a project with presonus only plugins where this happens. After a while and a lot of mails and a lot more people reporting this problem, they've confirmed that there is a problem and that they work on it. Long story short, it was gone at some point.
In my very personal opinion and without any confirmation about that, I think this was not a "oh, there is the line in the code" problem, it seemed to me, that it could be related to some external runtime libs and stuff like that which is quite complex to hunt down. And this could also be introduced by an outdated plugin, maybe some kind of driver issue or what so ever.
 
I just checked this again. I added a bypass automation to LFO tool for one track in a specific section of my song and it didn't export that in the stems. How do we use this in a professional scenario then. Luckily i used a project file which got shelved so i won't lose any work. i'm using this DAW on an apple M4 Pro chip running OS 15.7.3
 
Initial post in this thread mentioned the issue occurring "when mastering" but I can confirm that rendering an instrument track ('freezing' to audio) ignores automation. In addition, trying to revert a rendered track that had been saved in 7.2 can result in some of the automation lanes being removed entirely.
Moral of the story: Try FSP8 only on backup copies.
 
You must log in or register to reply here.
Back
Top