What is going on with Studio One v7.2.3 - just opened it and ALL settings have been wiped???

[Vocalpoint]

All

Early this morning - I was simply a spectator - chiming in on a few posts where a user was saying his Studio One V7 layout had complete reverted to a default install.

5 mins ago - I am getting the same thing. Just fired up S1 v7.23 to see this:

Which I know is never a good thing. So I did not Accept or Decline - just hit the X in the upper right

Then - I immediately went to the Studio One v7 AppDate folder and saw this:

As barebones as it gets. Everything - gone

Luckily - a backup ran this morning at 8:45am - preserving my last known good v7 state - which is this:

Does anyone have ANY idea just what is going on here? This is Danger with a capitol "D" for anyone who is unprepared.

Might need to contact support as well - as this is a disaster.

VP

 

[lokeyfly]

TY for the heads-up, VP.
I had no issue this morning editing in a few songs. I will back up though, hearing this. What the ____!
You're one that covers all the precautions.

I lIve close to Baton Rouge now, so if you need me to roll some heads, I will.

 

[Vocalpoint]

Yeah - just chatted with a few Presonus/Fender resources on the FB group - apparently - this CAN happen.

Been told that your config can suddenly get "corrupted" (reasons unknown) and this is the default action. Was also told it is NOT a bug.

Not sure how to feel about that explanation - but I am VERY glad I have daily imaging going on.

Was able to restore the directory from last nights backup and all good now.

VP

 

[parityflux]

IMO this should never happen. I write software. This is bullshit.
-j

 

[Vocalpoint]

The language in your post aside - I do agree.

This a major oversight - if the only solution to a "supposed" (unknown/unannounced/unplanned) "corruption" problem is to ice the entire installation - including the ENTIRE set of application files, customizations - basically anything a guy need to run Studio One/SP and present to user with an empty config - is about as ridiculous a solution as I can fathom.

The user gets no chance to do anything - except watch their entire installation directory disappear and have the app starts over as if it has never been run - ever.

This needs an explanation at multiple levels - especially for whoever decided this "recovery" (and I use that term VERY lightly) method has any value in any way.

Would like to get some insight from Arne Kaiser or Lukas or Ari or anyone who is closer to the development bench than we are.

VP

 

[Stuart Welwood]

MO this should never happen.

I'm a retired software engineer, and I agree. Destruction of user data is considered to be one of the biggest no-nos in software development. Inexcusable IMNSHO.

 

[Craig Anderton]

Does anyone know whether this can affect FSP8 as well?

 

[Vocalpoint]

Does anyone know whether this can affect FSP8 as well?

Until someone can explain why I saw i in the first place in S1v7 - I would have to assume it can (and will) occur in SPv8 as well.

VP

 

[parityflux]

Hey,
Apologies for my small outburst. I can do better with prose than that.

I will be taking note and writing some scripts to backup and restore my settings to hedge against any future corruptions. I had done this with S6, but S7 was working so well I didn't bother. I'll do it for both S7 and FSP8. I mentioned the issue to support (inside another ticket) and they asked me to copy my "settings" from FSP8 to S7. I was a little skeptical but gave it a shot since my S7 settings were toast. I used the Win path %USERPROFILE%\AppData\Roaming\Fender\Studio Pro 8 to copy from. It largely worked, with a bit of barking about being unable to use the FSP8 manual and resetting the license again (blank slate like the OP). It was also only effective because the initial FSP8 installation migrated my S7 settings. My devices were there and that's really the biggest relief.
-j