Why have all my user settings been erased, all project VST's been removed and Looks settings lost?
Oh, and I had to re-enter my Serial Key twice beforehand.
All user settings returned to default
-
- KVRAF
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- Topic Starter
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I found this file in the User folder [UserFolderPath.txt]
it contains this:
UserFolderPath=@SystemAppData
What I want to know is how the hell that happened? I know it wasn't me that did it as I never use the system folders and haven't even accessed MuLab's preferences for well over a year!
it contains this:
UserFolderPath=@SystemAppData
What I want to know is how the hell that happened? I know it wasn't me that did it as I never use the system folders and haven't even accessed MuLab's preferences for well over a year!
-
- KVRAF
- Topic Starter
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Deleted the above file and restarted and then asked to enter Serial again, then had to select audio engine after which, MuLab crashed.
-
- KVRAF
- 5381 posts since 25 Jan, 2014 from The End of The World as We Knowit
Covid-19sl23 wrote: Wed Aug 26, 2020 11:57 am Why have all my user settings been erased, all project VST's been removed and Looks settings lost?
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Please see this doc page, especially the section about the user folder.
https://www.mutools.com/info/M8/docs/co ... ences.html
So if you would have moved an existing MuLab folder (containing all your user settings incl vst plugin database etc) to a non-writable folder (which is not recommended, unless you know what you're doing) then the user folder will have switched in the app data system folder. If you then want to continue to use your previous user settings, then have to copy them to the new user folder in the app data folder.
In short: If you want to keep things simple then make sure you install MuLab in a writable folder.
Then the user folder will simply be the MuLab/User/Settings sub-folder.
NB: To find your previous MuLab user folder you could search your system for the file MainSetup.txt
https://www.mutools.com/info/M8/docs/co ... ences.html
So if you would have moved an existing MuLab folder (containing all your user settings incl vst plugin database etc) to a non-writable folder (which is not recommended, unless you know what you're doing) then the user folder will have switched in the app data system folder. If you then want to continue to use your previous user settings, then have to copy them to the new user folder in the app data folder.
In short: If you want to keep things simple then make sure you install MuLab in a writable folder.
Then the user folder will simply be the MuLab/User/Settings sub-folder.
NB: To find your previous MuLab user folder you could search your system for the file MainSetup.txt
-
- KVRAF
- Topic Starter
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Always has been and always will be in a writable folder in the default location, so again it's not possible this was done via user error.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
If you did not change anything and MuLab still is in a writable folder then quit MuLab and simply delete the UserFolderPath.txt file in the default user folder MuLab/User/Settings. Then everything should work as before. Right?
-
- KVRAF
- Topic Starter
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Yes, problem solved without knowing how it happened though?sl23 wrote: Wed Aug 26, 2020 12:05 pm I found this file in the User folder [UserFolderPath.txt]
it contains this:
UserFolderPath=@SystemAppData
What I want to know is how the hell that happened? I know it wasn't me that did it as I never use the system folders and haven't even accessed MuLab's preferences for well over a year!
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Good to know that deleting that UserFolderPath.txt file indeed gets back all your user settings. Knowing that is part of analysing the issue. I will add extra log info for that specific area.
-
- KVRAF
- Topic Starter
- 3157 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- Banned
- 3564 posts since 22 Aug, 2019
Sounds like the problem I have, I also had to reenter the key...
viewtopic.php?f=79&t=550866
Today I tried to export a simple, short clip to audio, Mulab crashed completely, simply disappeared. The audio file on the desktop is completely empty, 0 bytes.
Something is seriously wrong with the latest version of Mulab.
viewtopic.php?f=79&t=550866
Today I tried to export a simple, short clip to audio, Mulab crashed completely, simply disappeared. The audio file on the desktop is completely empty, 0 bytes.
Something is seriously wrong with the latest version of Mulab.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Why not take a copy first? I doubt going backwards is supported, though. (I don't remember if M7->M8 required a full package upgrade along with patch rewrites - I think it did at some point.)
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
No.
No.Can I simply copy the M8 user folder into the M7 folder?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Note that the crash could be in a VST plugin. If any VSTs were used then simply concluding that it is MuLab's fault is a wrong conclusion.e-crooner wrote: Sat Aug 29, 2020 8:00 pm Today I tried to export a simple, short clip to audio, Mulab crashed completely, simply disappeared. The audio file on the desktop is completely empty, 0 bytes. Something is seriously wrong with the latest version of Mulab.
Please send me the detailed crash report thus the tech info that includes exception module and address etc. And try to repeat the problem and then post the precise steps how to repeat it.