Fender Studio 8 - Crash

[Cyrus]

Hi everyone , I have some problems with my DAW Fender Studio 8 latest version [roaming crash ]. I wrote to the support team and they told me:

If it happens a lot, you can try a settings refresh to see if things settle down.

Instructions:
Go to menu Help > Open Settings Folder
Close Studio Pro.
Cut all the contents of the settings folder and paste it to a new folder on the desktop, leaving the settings folder empty.
Restart Studio Pro and it will create new settings files.
Ignore any missing things like recent files list, etc.
Test for the error, etc..

After the settings reset and re-launch:
The Recent Files lists will be empty, that's normal.
Plug-ins from custom paths will not have scanned in.
Manually open a song and check to see if the reported issue is resolved
If it is resolved, restore any custom plug-in paths in .
Restoring some settings: (if the reset resolves the issue):
If you've created custom plugin folders in the browser and want to restore those, close Studio Pro and copy the file PluginPresentation.settings from the desktop settings folder to the application settings folder before launching Studio One again.

If you want to restore your Recent Files menu listings and Recent Files Start Page listings, close Studio Pro and copy the file RecentDocuments.settings from the desktop settings folder to the application settings folder before launching Studio Pro again.

Others: user.colorscheme.settings user.keyscheme.settings

Once everything is settled, you can delete the desktop settings folder.
To undo / revert (if the reset doesn't resolve the issue):
Go to menu Help > Open Settings Folder
Close Studio Pro.
Copy all the contents of the desktop settings folder and paste it to the application settings folder.

This sugestion dosent work.

I dont know how to fix the problem. I dont remember this king of crash on version 6 or 7.

Any sugestion ?

 

[Vocalpoint]

Interesting "fix" - but for some of us - it takes weeks/months to get our Studio Pro Settings exactly the way we want them - deleting the entire settings folder - for me anyway - is not a solution.

While crashes are extremely rare here (just 4 since 2011) - this one of yours - will most certainly be 99% due to a plugin. And if you are lucky - on Windows - the cause of the mayhem might be listed in Event Viewer.

As to the "why" that things appear to be more "touchy" in v8 VS prior operation in v6 and v7 - v8 is much less "forgiving" of bad plugin code - and unfortunately in some cases - this can lead to a crash. You would help you troubleshooting here - to list your plugins so we can see what you using.

Finally - you claim the error is occuring in V8 of Studio Pro - yet your screencap is for Studio One?

Which version are we actually talking about here?

VP

 

[Navar]

Interesting "fix" - but for some of us - it takes weeks/months to get our Studio Pro Settings exactly the way we want them - deleting the entire settings folder - for me anyway - is not a solution.

Sometimes it's a bit of the standard lucky shot tryout fix from the support.

I have definitly crashes in every version of Studio One/Pro and most of the time it was a plug-in. But sometimes not the ones you might think of. As an example, Ara, as nice at seems is sometimes a pain, Vocalign crashes a lot for me and I never use it in a serious project and only work with additional editing projects, export the edits and re-import them into my main project. And the last Vocalign update is ages ago and no one knows what might have changed in the time between.
I used the Splice Bridge Plugin direct from Splice (not the internal one), turns out after texting with the Fender support, it caused a lot of trouble and I had it in my standard song template. Never thought of this area because this thing only transfer some stupid data from A to B.
And also the internal Fender add-ons like retro mix legends and the splice integration need to be checked from time to time if there is an update available. There is no auto reminder for this and they can get outdated too and crash. I had this with the retro mix legends. I don't get it, why those things don't auto update with a new Studio Pro version but I've started to check them from time to time.

What I do if I have a crash dump is, that I send it to the support team and ask them if they can take a look into it to check if they can see any problems with a plugin. And chances are high that they find something. (On windows I always create a fresh system info file cause they will ask for it anyway).

 

[Cyrus]

Finally - you claim the error is occuring in V8 of Studio Pro - yet your screencap is for Studio One?

Which version are we actually talking about here?

VP

this is a random screenshot from Internet , but it looks like mine in Fender Studio Pro 8

 

[Vocalpoint]

Sometimes it's a bit of the standard lucky shot tryout fix from the support.

I have definitly crashes in every version of Studio One/Pro and most of the time it was a plug-in. But sometimes not the ones you might think of.

Have seen a whole raft of plugins that folks "think" should be solid - suddenly not be. Studio Pro consistently updates their VST SDK - release after release - tightening the screws on all plugin vendors and will expose the ones that do not follow the spec.

Unfortunately - sometimes - the only way that "exposure" is shown to us - is via a crash.

I use exactly 146 plugins - from VERY established vendors and have used these for years now and have never had an issue. The only one currently - that is really frosting my corn - is Scaler 3.

The latest releases in the v3.3 cycle (even the one just release today v3.3.1) will consistently crash the Studio Pro Plugin scanner - which is a first as far as I know.

Oddly - this process still "allows" Scaler 3 to pass - the plugin scanner does not blacklist Scaler 3 (which it should do) it simply registers a crash in Event Viewer and then seems to carry on without any other negative aspect.

Not exactly sure what this means - but I might do a post on it.

VP

 

[Cyrus]

Sometimes it's a bit of the standard lucky shot tryout fix from the support.

I have definitly crashes in every version of Studio One/Pro and most of the time it was a plug-in. But sometimes not the ones you might think of. As an example, Ara, as nice at seems is sometimes a pain, Vocalign crashes a lot for me and I never use it in a serious project and only work with additional editing projects, export the edits and re-import them into my main project. And the last Vocalign update is ages ago and no one knows what might have changed in the time between.
I used the Splice Bridge Plugin direct from Splice (not the internal one), turns out after texting with the Fender support, it caused a lot of trouble and I had it in my standard song template. Never thought of this area because this thing only transfer some stupid data from A to B.
And also the internal Fender add-ons like retro mix legends and the splice integration need to be checked from time to time if there is an update available. There is no auto reminder for this and they can get outdated too and crash. I had this with the retro mix legends. I don't get it, why those things don't auto update with a new Studio Pro version but I've started to check them from time to time.

What I do if I have a crash dump is, that I send it to the support team and ask them if they can take a look into it to check if they can see any problems with a plugin. And chances are high that they find something. (On windows I always create a fresh system info file cause they will ask for it anyway).

Yes i send them a Diagnostic Report , today they asked me for another NFO file so they can take a deeper look at my system.

My typical setup spire, arturia analog lab, arturia acid v , Airwave by Adam Szabo, Serum, Access Virus - Aura Plugin all stuff is legal, UAD - 1176, La2a and studio one stuff reverb, delays, compressors.

I tested my older version of Studio One 7 today, and there were no crashes. I opened several projects, and everything worked flawlessly.

 

[Vocalpoint]

My typical setup spire, arturia analog lab, arturia acid v , Airwave by Adam Szabo, Serum, Access Virus - Aura Plugin all stuff is legal

Well - it's not really about "legal" it's more about how much development clout is behind each plugin.

I use a raft of Arturia, Spectrasonics, Toontrack, UAD here etc - ALL the big names - and none of them ever exhibit any issues.

I would be looking at tiny players like Airwave etc. Again - nothing against Adam Szabo - but just because Airwave seem to work in v7 - does not necessarily mean anything if Fender DEV has considerably tightened the VST SDK spec within SP v8.1.2.

If Adam's work is not up to the exact VST spec that v8.1.2 expects to see - oddball stuff can happen.

VP

 

[Navar]

Btw. there are tools like the KVR Studio Manager, which is free and able to scan the plugin library and to show outdated versions. It does not have an update function integrated but you can check from time to time and do an update orgy. And it works for Win&Mac.