Some questions about migrating from CbBL>Sonar

[Gary Shore]

Getting ready to install/migrate over to Sonar so I'm posting this thread proactively to get some clarification about a few focus aspects of the overall process I haven't been able to find satisfactory info about after going through many of the threads over here as well as in the FB groups...

Much thx to everyone who's taken the time to contribute to the extensive ongoing online discussion about everything involved;like others who found out about the upcoming 8/1 cutoff date in the context of a period of regular CbBL usage(working on multiple current projects daily for many hours),being able to take full advantage of all the info that's been made available has been indispensable/invaluable(as well as reassuring) and I'm hoping this current thread will serve the same purpose for those who might also be wondering about this stuff....

My main focus is getting a clear sense of exactly what's involved in terms of the migration process with the Cakewalk Projects folder...in other words,when I check the "transfer all my CbBL settings over to the new Sonar" option during the Cakewalk Product Center installation process,will the existing projects that are currently in the CWP folder now also be in the new Sonar Projects folder that it's going to set up?Will this new Sonar Projects folder basically be a duplicate copy of my CWP folder?

Asking about this because my concern here is overall SSD storage space on my hard drive;I already have a solid projects backup system in place so wouldn't need a duplicate copy of my CWP folder alongside the new Sonar one(if this is in fact the case post-installation) ....... 

However I'm also looking at exactly what's necessary for everything to migrate over/continue to work seamlessly....seen a lot of conflicting/confusing  info in different threads about the whole subject of deleting CbBL from your C drive i.e.people describing various problems they've had w/their new Sonar installation if they uninstall CbBL/warning everyone to make sure not to delete the wrong CbBL folders from your system/various things people have experienced leading to them having to re-install it etcetc... 

In light of the above then,I'm wondering if keeping both the original Cakewalk Projects Folder along w/the new(duplicate of this ??)Sonar Projects Folder installed (at least temporarily) is a good idea/possibly necessary re-everything involved in setting up as smooth a transition as possible?

Directly related to this is my second area of focus-making sure that all the "add-ons"/plugins in my currently installed/most-recent- update version of CbBL will successfully migrate and,given the above description of my "24-7 in-the-DAW" routine,I'll be able to continue working on things in Sonar w/"everything intact" (as so many of the threads suggest will be the case)....since  these current/existing projects make integral use of much of the great "legacy" CbBL stuff like the Sonitus suite(getting some great results w/the Sonitus Wah),SI Suite(just started working with SI Strings),Drum Replacer,etc 

My thinking here based on the info I've seen is-since a given VSTi/plugin has already been "recognized" re-VST scan/works correctly in the most recent CbBL update version I'm currently using,when I select the option that allows for all my current settings to migrate over during the new Sonar setup,this should also "seamlessly transition" along w/ everything else.... 

So as far as the CPC installation itself and the option to install both the SI Suite/Drum Replacer as "add-ons",I'm thinking I should leave both unchecked-but would appreciate any about this...

Also,in line w/what I went into above re-the CWP folder,with my C drive "Cakewalk Content" folder containing Drum Replacer (as well as other locations like the AppData/Roaming folder etc w/related DR folders)or the Cakewalk Project Files folder w/the SI Suite etc(see attached screenshot showing all the folders for SI Suite),will these all become redundant/unnecessary duplicates upon the Sonar installation that can safely be deleted or should they be left untouched for Sonar to be able to access as part of the whole "Cakewalk tree" I've been seeing referred to?

Realize this has become a fairly lengthy thread and so will end it w/the final thing I'd like to better understand-

Been reading about the new Track Manager module available in Premium and am wondering if the current Track View "Tracks" menu dropdown Track Manager Dialog  I use regularly in CbBL is also available in the  Free Tier as well?

Appreciate everyone who's taken the time to read this;any info/feedback/finding out how people suggest handling the situations I'm asking about would be great,

Also would be grateful if,as @Jonathan Sasor did a week or so back on a related thread,any other actual CbBL staff people who've been providing the kind of factual info over here all of us still familiarizing ourselves w/everything involved in this migration>Sonar have come to  rely on/who've helped me figure stuff out in the past like @msmcleod or Noel etc might have a chance to post as their time permits .......

Thanks in advance for any/all replies.......


  








 

Edited Monday at 11:10 PM by Gary Shore

[Jonathan Sasor]

Sonar will migrate your actual settings on first launch. You may want to copy some project/track templates from their respective places in Cakewalk Content, but Sonar should have no issues loading those.

As for the add-ons, it's the same versions of Studio Instruments that have installed previously, but they have new installers that Product Center reads to see if they're installed or not. Not required to download if you don't want, but it won't change anything functionally if you do. 

 

[Gary Shore]

29 minutes ago, Jonathan Sasor said:

Sonar will migrate your actual settings on first launch.

@Jonathan Sasor Jonathan really appreciate you taking the time to continue helping me figure things out here...

Although yours is the first reply I've gotten over here,posted this same thread in a few of the FB groups and have been getting a lot of replies from people suggesting that instead of how I've been thinking about things re-above,I should just be looking at the whole CbBL>Sonar migration as a form of the usual periodic updates,that Sonar actually makes use of the existing CWP folder as well as all the other currently-in-place folders/paths....so everything I was asking about yesterday re-duplicates etcetc was actually based on misunderstanding what will be taking place and things can remain exactly as they are...

Would you agree?Am I missing anything here?

Thx in advance for continuing this discussion as your time permits...

[Bristol_Jonesey]

1 hour ago, Gary Shore said:

so everything I was asking about yesterday re-duplicates etcetc was actually based on misunderstanding what will be taking place and things can remain exactly as they are...

Would you agree?Am I missing anything here?

You're not missing anything.

Sadly, Facebook & other social media sites are full of misunderstandings, half truths and generally BAD advice.

It's all mixed in with the GOOD advice so trying to unravel it can be a total minefield

For the proper answers, always come here

[John Vere]

1 hour ago, Bristol_Jonesey said:

For the proper answers, always come here

This! I cringe when I visit the Facebook pages. They will even recommend asio4all!

[Gary Shore]

@John Vere

Hey John!!Been checking out everything you've been posting about the move>Sonar,much appreciated as always man...

Anyways since you're now part of the thread,it'd mean a lot to me to be able to find out your take on the actual specific stuff I'm asking about above re-existing CbBL installation in context of new Sonar installation/CWP folder etc...since I've already learned so much about how to have an empowered workflow in the DAW from studying all your older videos/stuff you've posted on various threads over here I've found,getting the benefit of your wisdom for this current situation would be a real gamechanger if/when you get a chance to continue posting....