I'm with Tom!

OT  ,but :
The reason people say the vinyl sounds better is because the music was better.
 
You are hitting it.

I love it for my Console 1, my favorite UAD plugs and my Arturia stuff.  They get used very frequently.

Seems to be some naysayers regarding this new "recent plugins used" feature addition . . . isn't Cakewalk just trying to save us some time, fishing through the drop down menus of our vast collections of plugins . . . come on, don't you find yourself using your same five amazing plugins over and over again ?
 
 . . . or, are we just mad that there's no "off" switch in the preferences for this new thing ?
 
I actually like it a lot.

Whether it's useful or not is up to the individual. My custom menu is already set up in a more logically organized way than a 'last used'.
It could be a useful feature for many but not for me.  In my case an option to turn it on or off would be as useful as the feature itself.

M@
I'm going to bump this too as i too prefer lean menu's and can do without the list.

However as it's a feature that's going to stay i'd want to re-suggest what I suggested in a different thread before this feature got inplemented:

** the list should contain most FREQUENTLY used fx **

That way as your habits change and your arsenal of available plugins grows you will have an automatically updated list of those plugins that are most likely your favorite and most needed. (No need for an additional "favorites" folder)

Just because i add the adaptive limiter to my master bus doesn't mean i want it to be top of the list in my add fx menu?!

Besides; for some peoples workflow the most frequently used might also be the most recently used :)

As so often: ideally the user would be able to configure his preference.

Add me to this list. Otherwise, yeah, I'd like to disable it. It's no help to me, especially when it lists the same plug-in twice. (I don't know why it does that, and I don't really care to find out. I'd rather just turn it off entirely, if Cakewalk will give us the option.)
 
Steve

I don't recall Cakewalk consulting their users on a lot of these new features they're introducing, they seem to go ahead and just do them based on internal development meetings . . . with no "opt out" possibility, whether you like the new feature or not ? Perhaps keeping up with the monthly update quota. This last monthly update was kind of lacklustered, summer break, who knows ? Still, I'm always amazed by what comes next.

planetearth

Add me to this list. Otherwise, yeah, I'd like to disable it. It's no help to me, especially when it lists the same plug-in twice. (I don't know why it does that, and I don't really care to find out. I'd rather just turn it off entirely, if Cakewalk will give us the option.)
 
Steve

I hadn't checked out SONAR's implementation as yet, but when I read the above (in bold), I thought to myself that sounds pretty stupid. So I updated to the latest version to see, I couldn't get it to display the same plug twice, I tried but it just didn't happen. What I saw was similar behavior to how Studio One and REAPER do it, if you add a plugin that is already in the recent plug list it isn't duplicated but promoted to the top of the list, which would be the sensible thing to do, as apposed to duplicating.

Matron Landslide

planetearth

Add me to this list. Otherwise, yeah, I'd like to disable it. It's no help to me, especially when it lists the same plug-in twice. (I don't know why it does that, and I don't really care to find out. I'd rather just turn it off entirely, if Cakewalk will give us the option.)
 
Steve

I hadn't checked out SONAR's implementation as yet, but when I read the above (in bold), I thought to myself that sounds pretty stupid. So I updated to the latest version to see, I couldn't get it to display the same plug twice, I tried but it just didn't happen. What I saw was similar behavior to how Studio One and REAPER do it, if you add a plugin that is already in the recent plug list it isn't duplicated but promoted to the top of the list, which would be the sensible thing to do, as apposed to duplicating.

I haven't seen this either. The only way I can imagine this happening is if someone were to open two different versions of the same plugin. (Vst2 vs vst3, DXI vs VSTi, 32 bit vs 64 bit, etc)
I like the feature myself. Very handy.

Well done, just tried that, and it does indeed happen if you add the vst2version and vst3 version of same plug.