For examples of how ripple editing affects MIDI notes with Ripple All selected, view this month's Tech+Music publication!

Is there an easy way to download this?
There used to be...

Aah! Thanks Zargg - I didn't maximise it, so I didn't see the arrow.

1. I don't know, but you can clear entries from the registry, as described in the eZine. Maybe there's some way to delete those keys...but at least live with the feature for a couple weeks before deciding you don't need it. I find it saves me time.
2. Did you update the Boutique FX Suite containing TH3, as instructed in a recent update (don't recall which one offhand)?

Anderton
1. I don't know, but you can clear entries from the registry, as described in the eZine. Maybe there's some way to delete those keys...but at least live with the feature for a couple weeks before deciding you don't need it. I find it saves me time.
2. Did you update the Boutique FX Suite containing TH3, as instructed in a recent update (don't recall which one offhand)?

1.  I use custom templates, so all my "go to" fx and such are already in place when I start a project. If for some reason I want to add another instance of the "go to" ones,  I just drag it across from an existing fx bin, so yes, to me, it's just clutter that I don't really need to look at every time I open the menu. Sorry and all that, but I would prefer that CW "improved" things like the fact that inspector doesn't shrink back properly when expanded using the clip tab, or fix the irritating "undo" glitch where it doesn't display the correct undo item rather than fix things that didn't really need fixing IMO.
 
2. Yes. CCC shows green light for boutique fx suite and says it is latest version (2017.05). However, what I have since discovered is that CCC only updates the 64 bit plug-ins and not their 32 bit counterparts where they exist, so I have just re-installed the update manually to include 32 bit versions and it works now. Now that I know this, I will revert to doing the updates manually as I had been doing until recently seeing as it now seems that in leaving it to CCC I will still end up having to that anyway.
 
 

paulo

Anderton
1. I don't know, but you can clear entries from the registry, as described in the eZine. Maybe there's some way to delete those keys...but at least live with the feature for a couple weeks before deciding you don't need it. I find it saves me time.
2. Did you update the Boutique FX Suite containing TH3, as instructed in a recent update (don't recall which one offhand)?

1.  I use custom templates, so all my "go to" fx and such are already in place when I start a project. If for some reason I want to add another instance of the "go to" ones,  I just drag it across from an existing fx bin, so yes, to me, it's just clutter that I don't really need to look at every time I open the menu. Sorry and all that, but I would prefer that CW "improved" things like the fact that inspector doesn't shrink back properly when expanded using the clip tab, or fix the irritating "undo" glitch where it doesn't display the correct undo item rather than fix things that didn't really need fixing IMO.
 
2. Yes. CCC shows green light for boutique fx suite and says it is latest version (2017.05). However, what I have since discovered is that CCC only updates the 64 bit plug-ins and not their 32 bit counterparts where they exist, so I have just re-installed the update manually to include 32 bit versions and it works now. Now that I know this, I will revert to doing the updates manually as I had been doing until recently seeing as it now seems that in leaving it to CCC I will still end up having to that anyway.
 
 

If you set CCC to use Verbose Install the installations will start automatically as usual but will stop for user input as various options come up eg to use 32 and/or 64 bit.
If you don't do that then CCC assumes by default that as you're on a 64 bit OS you're going to install 64bit plugins etc.
the other way is to go to the Cakewalk Command Centre downloads folder and double click on the installer file. It will run giving you options as I've outlined above and you know yourself from installing them manually.
Hope that helps.

Just installed the 2017.07 documentation. Windows 7 shows the user guide date was modified today but the reference manual remains at a last modified date of 12/14/16.
 
Could someone please confirm that the updated user guide version should be 21.00.00 and the reference guide version should be at 22.12.00? If so, I'm not sure why Windows did not update the modified date for the ref guide...
 
Kind regards,
Rick

scook
That is correct. The reference guide is not updated with every release. It appears to be on an annual update cycle. The User Guide has no regular update cycle. The local chm help file is updated with every release, just like the web-based help.

scook,
Thank You again for your Help and the information.
 
regards,
Rick

As always, no problems here. At least for me and my 3 machines,  never had any issues with CC or an update.
 
There was one post regarding TH3 and a crash. I had the same, but since I always install both VST2 and VST3, there has been a workaround using one over the other.
 
The grid in the track pane now corresponds with the snap settings. Wonderful! THX Bakers, I love you.
 
If after two years you will also fix the broken transient detection I will marry one of you haha xD.

And I'm assuming this is not the case so this is more of a request/suggestion...
 
It would be awesome if the new "Recently Used Plugins" thing allowed for an option to load not just recently used plugins but also an option to load specific plugin states between tracks/projects.
 
Like how Ctrl Dragging a plugin to another track loads that plugin with the same settings... except it can be done via menus (and across projects). That would be brilliant because as we all know many plugins have their own weird user preset functions (some better/easier than others). Being able to bypass that plug to plug silliness would be a massive time/brain saver.
 
Cheers.
 

I just wanted to say that I've been seeing far less crashes since this update, and things seem a little speedier. Also I find the new 'recently used plugins' feature really useful. I do have my own layout going on for plugins, but it's still nice to be able to snap back to the last few I used so instantly. Great work!

The title to the thread in which you've posted tells it all. See the first post then open CCC and download and install the new update.
In any case CCC will tell you if an update is available. Any item with an update turns yellow with details about the update being available in the right hand screen.

recently used plugins - a super idea!!  Way to go Cakewalk!!!
 

RobertLogan
I just wanted to say that I've been seeing far less crashes since this update, and things seem a little speedier. Also I find the new 'recently used plugins' feature really useful. I do have my own layout going on for plugins, but it's still nice to be able to snap back to the last few I used so instantly. Great work!

Once this topic was not answered, I leave here the suggestion for improvement in future versions of Sonar.