Fender Studio Pro 8.2 - Discussion Thread

[Vocalpoint]

Has anyone had any issues with Universal Audio plugins? When I drag one from one channel to another, it loses all its settings. No other third-party plugins seem to be doing this. Just Universal Audio since I switched from 8.1 to 8.2.

What specific UAD plugins did you experience this with?

VP

 

[mattyharris]

1176 blue stripe, distressor, I tried a few more. Seemed to be a UAD thing.

 

[Vocalpoint]

1176 blue stripe, distressor, I tried a few more. Seemed to be a UAD thing.

And you are simply dragging an existing instance (with I assume some specific settings) - with no modifier keys like ALT etc?

Just tested the Blue Stripe and three others - cannot replicate.

All mine copy their unique settings from source to destination in a standard "drag" scenario.

My specs below...

VP

 

[tremo]

I can confirm that UADx native plugins lose settings when dragged (copied) from one channel to another. But UAD DSP plugins (I'm using a Quad TB Satellite) keep settings when copied.

 

[Vocalpoint]

I can confirm that UADx native plugins lose settings when dragged (copied) from one channel to another. But UAD DSP plugins (I'm using a Quad TB Satellite) keep settings when copied.

Was just going to add this in. All my tests were using DSPs. Will try a Native now...

And...confirmed.

Not only does it not retain the settings - the "dragged" plugin reverts BUT keeps the preset name of the source.

I added Ampex ATR to a track - then switched the preset to "Classic 250 Warm Master". The controls switched to the settings for that specific preset. Then I dragged it to another track - the preset name stayed locked in - but the controls rolled back to the "Default" preset settings.

That is really messed up.

VP

 

[mattyharris]

Just heard back from Fender:

Thank you for contacting Fender Digital Audio Support. Sorry to hear about the recent issues you have been experiencing.

I do apologize for this issue. It is a known issue and logged with the Studio One developers. Unfortunately, I am unable to provide a time frame for when this will be resolved. Please keep an eye out for bug fixes in Studio Pro update release notes.


So looks like it's a known issue. I'll stick with 8.1 till they push a fix.

 

[tremo]

Not only does it not retain the settings - the "dragged" plugin reverts BUT keeps the preset name of the source.

At least the preset name on the copied plugin changes to italic, indicating changed settings, but yeah -- it's really messed up.

 

[Ken Morgan]

Ive started getting crashes on 8.2 that I can’t track down, but they seem to happen when I try to move/relocate a buss in the seperated mixer screen while in playback mode.

Also had at least 1 instance of a crash while mixing AU and VST plugins on a buss (but no issues while mixing them on a track)

2018 Mac Mini Intel, Sequoia 15.7…32G…external SSD audio drive…

 

[Lukas]

Also had at least 1 instance of a crash while mixing AU and VST plugins on a buss (but no issues while mixing them on a track)

Don't use AU plug-ins in Studio Pro unless you have a good reason to do so.

Not saying this is the cause of the crash, but since I see so many reports of AU plug-ins being unstable (and apparently not tested at all) in FSP, it might be at least one thing to consider.

 

[Vocalpoint]

Don't use AU plug-ins in Studio Pro unless you have a good reason to do so.

This. If you really crave instability - by all means - use AU.

VP

 

[Gary Shepherd]

I don't have any UA plugins but all my Waves, Bogren, Line 6, and Toontrack seem to work fine on 8.2. It is not vastly different to 8.1 so whether UA need to update, or you need to refresh them, it's hard to say.

Out of interest, I am still on Sequoia - how is Tahoe working with Studio Pro?

Maybe UA are not yet updated for Tahoe?

I have held off with Tahoe - just wondered if there is anything to worry about that update (in particular or in general)?

 

[Vocalpoint]

Maybe UA are not yet updated for Tahoe?

I have held off with Tahoe - just wondered if there is anything to worry about that update (in particular or in general)?

Tahoe has been good to go for a long while now...but it's up to your hardware and specific situation if it's worth it for you.

VP

 

[Ken Morgan]

Don't use AU plug-ins in Studio Pro unless you have a good reason to do so.

Not saying this is the cause of the crash, but since I see so many reports of AU plug-ins being unstable (and apparently not tested at all) in FSP, it might be at least one thing to consider.

Still seeing crashes...with NO audio plugins, no instruments, nothing. Just moving a track in the mixer from one place to another, playback stopped.

Like others, sometimes, not always, not even most of the time, when trying to add an instrument (usually Superior Drummer 3 VST) results in a crash...I've learned the hard way to back up after every significant move and/or recorded track.

Sure hope these matters get resolved quickly

 

[Vocalpoint]

Still seeing crashes...with NO audio plugins, no instruments, nothing. Just moving a track in the mixer from one place to another, playback stopped.

That sounds like it's time for time into Fender support.

VP

 

[Lukas]

Like others, sometimes, not always, not even most of the time, when trying to add an instrument (usually Superior Drummer 3 VST) results in a crash...I've learned the hard way to back up after every significant move and/or recorded track.

Could it be more obvious? An instrument plug-in crashes when loading? Then it's (usually) not a Fender Studio Pro problem and you have to reach out the the plug-in company.

 

[Ken Morgan]

Could it be more obvious? An instrument plug-in crashes when loading? Then it's (usually) not a Fender Studio Pro problem and you have to reach out the the plug-in company.

Uh…no. The instrument in question worked perfectly in SP8, 8.1…ithere was never a problem in the Studio One/Studio Pro environment until 8.2 works perfectly in ProTools, Logic, and Reaper.

Obvious, yes. It’s obvious it’s not the plug-in.

 

[Lukas]

Uh…no. The instrument in question worked perfectly in SP8, 8.1…ithere was never a problem in the Studio One/Studio Pro environment until 8.2 works perfectly in ProTools, Logic, and Reaper.

This is a common misconception that keeps coming up in forums.

Just because a plug-in works in one version but crashes in another version doesn't automatically mean the DAW is at fault. A newer DAW version might use an updated VST SDK or start using API features that weren't used before, exposing bugs in the plug-in that previously went unnoticed.

The fact that a plug-in worked in an older version, or still works in other DAWs, doesn't prove it was implemented correctly.

...Logic...

Logic doesn't even support VST.

 

[Vocalpoint]

Just because a plug-in works in one version but crashes in another version doesn't automatically mean the DAW is at fault. A newer DAW version might use an updated VST SDK or start using API features that weren't used before, exposing bugs in the plug-in that previously went unnoticed.

This.

VP

 

[Ken Morgan]

So…every other instrument reporting problems is also wrong?

Gotcha

Added: it would seem to this non-computer literate user that the key to making any software successful is to make it compatible with the majority of already established supporting apps, not re-write things to cutting edge standards and expect the rest of the world to catch up.

Not a good look, but thats just an opinion, but I’ll say this: if the latest version of StudioPro doesn’t work with what I already own, I’m not going to use it. Not my job to tell Toontrack or anyone else to upgrade their products - thats between Fender and Toontrack

 

[Vocalpoint]

So…every other instrument reporting problems is also wrong?

You would be surprised. Updates to the internal SDK do not play favorites OR single out just one plugin to be upset about.

Added: it would seem to this non-computer literate user that the key to making any software successful is to make it compatible with the majority of already established supporting apps, not re-write things to cutting edge standards and expect the rest of the world to catch up.

It is up to Fender to decide what is right (or wrong) for their app.

They also cannot control bad/sketch coding - even from the biggest plugin vendors - OR test every plugin in the known world

And they won't be testing on your 2018 Mac mini either. There are limitless reasons for software failure in the big world.

If the latest version of Studio Pro doesn’t work with what I already own, I’m not going to use it.

Or why not simply rollback to v8.1.2 and stay there if you are convinced v8.2.0 is a mess?

Not my job to tell Toontrack or anyone else to upgrade their products - thats between Fender and Toontrack

It is clear from other reporting in here that v8.20 does in fact have some rough edges but until an v8.2.1 appears - not much else anyone can do.

VP