tlw
You'll need to install Sonar and all plugins under Win 10 as well as 7 if you want it to be usable under both in a dual-boot setup. I doubt there's any reason why a project saved in Win10 won't open fine if opened in Win 7 or vice-versa, but the Sonar recent files dialogue will differ depending on which Windows installation you're in at the time. Things like vst presets will probably be using different folders as well, so won't be accessible from both installations unless you sort out the paths, which may involve some fiddling with Windows junction points....
I'm still on Win8.1, partly because Windows versions seem to need to get to SP1 stage to be really solid and partly because the PC has been behaving a bit oddly for the last few weeks with intermittent freezes and I need to get to the bottom of that, but I've run dual-boot setups in the past and the above has always been my experience.
hmm... something I hadn't considered (and thus the thread) and raises some interesting points/problems.
I mostly use default paths for everything (at least for Cake stuff). I mostly only use Cake stuff but some third party tools.
I know that's not your point (actual user presets... not the VSTs themselves) but this seems very important. All the VSTs (and pretty much everything... which I'm drawing a blank on) would need to be using the same paths or at least somewhere the projects can find them on the different partitions.
All of a sudden the importance of there being a general VST folder that seems to get used by all programs (like other DAWs and the VSTs themselves) is becoming clearer. Interesting.
As far as presets... yeah, I guess if a user preset is saved in one partition it won't be there in another. I gotta wonder how that affects projects though. Like once a preset is loaded into a project should the project file then have all the data it needs to load the preset (because it is already in the track and the settings set to the preset values) even though the actual preset isn't available outside the project?
So I would not be able to call up a preset from scratch (on the new partition) but if it already exists in the project the project will load it's settings anyway (and I could even then save it as preset and thus have it on the new partition).
As far as preset migration... I know some plugs make this easy (like the preset export options on things like GR5 and TH2) but a lot of the Sonar stuff... yeah, not sure where that all lives or if there is a saveable/moveable folder (doubt it).
Kind of having a hard time envisioning how to set up those folder "link" setups (I'm assuming you are referring to the mklink command) to access them since the presets would be on the other partition and not accessible.
Unless the Windows partitions can talk to each other and the first partition (where the presets reside) can act as a slave/storage that files can be accessed from (while ignoring the OS installation).
I know Linux setups can sneak into Windows partitions to yank files (but not vice versa) but now I'm wondering if Windows to Windows parts can behave in this manner.
Ooof... okay, I guess I just sent myself into a brain bender (and am mostly "talking" out loud) but that's definitely some stuff to think on.
Thanks, dude. This is why I like chatting with you.
Cheers.