Congrats Cakewalk !
 
I assume a list of bug fixes with CWBRN numbers will be made available later?
 
In future though it would be cool if the bug fixes get listed in full at the same time as the release, and the problem reports forums gets updated accordingly (it would be nice if all posts with CWBRN numbers get marked as fixed, or at least acknowledged as well). This will probably mean QA will need the final build for testing a week earlier than what is probably happening right now.
 
Anyway it's amazing you released the patch on time considering the amount of snow (although VPN's I'm sure helped) and the fact that this is a new process, which I'm sure will improve as time goes on. For the first normal update this is indeed impressive and really does add value to the product.

I noticed that Braintree updated Boost 11 and installed it to program files->cakewalk->vstplugins. I have multiple VST scan paths defined (including the above mentioned path) to cover the various bases (multi vendor) but I try my best to keep all my VSTs in a central location (program files->vstplugins).

Since I had an older version of Boost 11 in this central location, the scan wasn't picking up the updated one until I moved the older one and put it in my "VST No Scan" folder which is not a scan path.

I hope that wasn't too confusing and is useful to someone.

Anderton
No, that's the Acoustic Piezo amp. The ProChannel presets should be visible when you go to load a ProChannel preset...I'll verify when I'm at my music computer.

Yes, click the folder at the top of the PC to see the AC guitar presets

Thanks Steve. FYI although they were designed around specific Gibson guitars (I have access to the world's coolest lending library for guitar players), they work with other acoustic guitars as well. Call up the preset for the type of guitar that's most like yours, or just call them up and see what works.

rcklln
I noticed that Braintree updated Boost 11 and installed it to program files->cakewalk->vstplugins. I have multiple VST scan paths defined (including the above mentioned path) to cover the various bases (multi vendor) but I try my best to keep all my VSTs in a central location (program files->vstplugins).

Since I had an older version of Boost 11 in this central location, the scan wasn't picking up the updated one until I moved the older one and put it in my "VST No Scan" folder which is not a scan path.

I hope that wasn't too confusing and is useful to someone.

I experienced this... Thanks for the tip.
Moving the VST files to my preferred folder, resetting and rescanning my VST's, and seeing if I can change any registry file paths to help for next time.

Actually (see post above) this is a bit of a major PITA.


What is urgently needed in the next update IMHO is at least a report afterwards which displays where stuff has got installed to after each installation (also save it to a log file), then we are in with at least a fighting chance of moving the files to where we want them. Otherwise we are just guessing.

Of course we do need more user definable custom file paths for all the components but a report would be a good start.
 
I'm off to the enhancement forums...
 
Thanks.

Just got done.  First post-update run and I see my control bar customizations are gone.

Very nice update package thanks !

Anderton

Geo524
Fantastic! Thanks for all the awesome stuff Cakewalk.

Keep in mind this is only the maiden voyage...

Awesome Craig. I'm not sure I'll be able to handle the excitement but I'm sure looking forward to trying. 

BobF
Just got done.  First post-update run and I see my control bar customizations are gone.

CWBRN-31610 Performing update of Sonar Platinum content resets control bar customisations