Of course UAC settings and general permissions can also impact folders being allowed to be moved to other locations.
If this is not the case for you then there is likely some aspect of your installation that is corrupt. Once you redirect the folders close SONAR down and the registry details for the folder locations shoudl be updated when SONAR next opens. I have always had these files in other locations and never had a problem. The Cakewalk Content folder is an arbitrary location set by Cakewalk to ensure that after instalation all the content files are in a locatiion that is not effected by UAC as its outside of the Program files folder trees.Īs for any folders within the Cakewalk Content folder these can all be redirected through Preferences should you want them somewhere else. You are making much more work out of this than necessary. And this is what the OP was inquiring about.
So., the editable content you see when displaying the "Preferences / Folder Location" dialog box is to be found in the registry at the path I specified in my post #7. except the top one (Project Files), hence the need to manually edit the registry. I looked at the Cakewalk Content folder and I see that some of the contents location and path can be changed in the Preferences Menu. If for reason x, this was not the case, I simply specify my preferred default folder locations again.
Change default file location sonar x1 update#
At worst, an update or quickfix could reset these values to the original default location (as proposed by Sonar), but usually and understandably, user preferences are not overwritten when dealing with these (updates/quickfixes). It was meant to be changed as this allows users greater flexibility in organizing/managing their audio related filing system. It's a user preference, a feature the "bakers" coded in enabling users to specify the default folder location for different types of Sonar files (eg. That's not going to happen and here's why. The concern I was addressing, is, if this value is changed it can cause a failure in some future update or quickfix. An overeaction in this case even though I understand your concern. I agree using the word 'hack' is subjective and is left up to interpretation.
0 kommentar(er)
