Studio Pro 8 Mixdown and Automation issue

[Midiboy]

I meant to say "Mixing down" not mastering. So that was my bad. However, if I freeze the track, my automation worked. So ... that's weird. A lot of inconsistencies here. Definitely some opportunities for Fender to fix some stuff.

 

[Lukas]

FYI: Fender is already working on a fix, which we are currently testing. It will be included in the next maintenance update.

 

[Midiboy]

I knew they would. Something you all need to remember...it is the SAME team working on this that was working on S1 before. I have complete confidence in them.

 

[khilts]

I've been using PS1/FSP for a handful of years, and also have confidence that bugs will be smooshed (technical term) to an acceptable level for most of us. It's just unfortunate that something as basic as automation popped up with a new major version number and rebranding.

 

[Midiboy]

The weird thing about is that I have another track that I just did and automation works fine on it and mixed just perfectly.

 

[Lukas]

The weird thing about is that I have another track that I just did and automation works fine on it and mixed just perfectly.

It might only happen when there's a certain (large?) number of automation points.

 

[Midiboy]

It might only happen when there's a certain (large?) number of automation points.

That is a good point. The track that worked had 11 tracks with one automation. The track that failed has 57 tracks with several automation events.

 

[@soundworks]

Hi everyone. I’m new to this form as well and unfortunately, I’ve encountered the same problem with an electric guitar bus that I added volume automation to. In this case, I can’t render the bus to audio like I could a track. It’s particularly frustrating because I’ll post a file for band members to listen to that was based on their feedback and the mix down doesn’t reflect the changes they suggested—not great for my credibility.

This is a pretty serious problem. I hope fender gets on it quickly.

 

[John Vere]

seemed to me, that it could be related to some external runtime libs and stuff like that

Are you aware that a bunch of us found out that the installer for Studio 8 asked to install a bogus C++ file and that all of us had Vegas crashing. The solution was to install the proper new runtime file. Look for the thread I started About Pro Studio 8 killed Vegas

 

[Timo]

I'm jumping in here.

Today I loaded a project created with Studio One Pro 7.2 into Studio Pro 8 to continue working on it. Everything, including automation (insert FX with stock and third-party plugins, volume, pan, send levels, stock and third-party instruments, etc.), exports correctly from S1 Pro 7.2.

Automation and sustain pedal information are not being included in the export for many tracks. Freezing only partially solved the problem. Furthermore, there are extreme pops and clicks as soon as CTC-1 is inserted as a mix FX in the master. The only solution is a steep volume automation curve in the track's mix channel to trick the engine into thinking there's a fade-in.

My current workaround is to finish projects created with 7.2 using that version.

Another workaround that helped with exporting was setting the dropout protection to maximum before exporting. That was never necessary with S1 Pro 7.2.

I'm going to create a new project in FSP8 with every conceivable automation scenario and see if this also happens with new projects that aren't carrying any "legacy" from previous versions.

 

[Sam Nadai]

The new upgrade seems to have fixed it.

 

[khilts]

Unfortunately I still have an automation-related issue after the update to 8.0.1.
On an instrument track (Presence) with ProEQ as the only plugin, I have a single dynamic EQ band at 2kHZ with the non-dynamic gain for that band automated. It's full of crackles if the automation lane is enabled and in read mode. If I disable the automation lane -or- change the mode from Read to Off, the crackles go away. If rendered to audio, the crackles are also present.