Ah, ok, makes sense. I noticed that the update had made the plugin layout revert to default rather than my custom layout. With the custom layout re-selected, the behaviour is the same as previously.

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...

jbraner

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...

http://forum.cakewalk.com/FindPost/3639259


All the best.

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

Just updated and two issues so far...
 
1) How can I turn off the "recently used plug-ins" addition to the insert synth/fx menu. It's just more clutter in the menu IMO.
 
2) Inserting TH3 into fx bin now crashes Sonar every time without fail. WTF? Just me?
 
 
 
 

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 haven't tried this so it may do bad things, but try setting permissions on that registry key so that users (ie. Especially the user you're running SONAR as) doesn't have write permissions. I've used this elsewhere with SONAR to block some history or other and it worked fine.

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.
 
 

KPerry
1 - I haven't tried this so it may do bad things, but try setting permissions on that registry key so that users (ie. Especially the user you're running SONAR as) doesn't have write permissions. I've used this elsewhere with SONAR to block some history or other and it worked fine.

Thanks for trying to help, but I don't really want to go down that route as I'd be out of my depth tbh. I was hoping that somewhere there would be a simple yes/no option to have this extra part of the menu displayed. 

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.