Neole


My point is, Cubase or Nuendo or Protools won't give me 'boing' and an error message that I must organise my plugins everytime I open a project in front of my clients.

SonarX1 does this everytime because I have more plugins than it is comfortable with.

I just want the error message to stop, and also the slow scrolling through a long list of plugins can be handled better with some kind of page up page down buttons.

Ive never organised my plugins, nor my wardrobe neither, so I dont care that cubase doesnt allow it. Im only requesting features that *I* find lacking.

then the only way to get it implemented as a feature is to submit a feature request.  if cake feels it's worthy then it will be implemented. 
 
http://www.cakewalk.com/Support/FeatureRequest.asp
 

Sorry for not coming back to my thread a bit earlier I've been away on my holidays.

Thanks for the feedback, but I can see a few of you are not getting a complete picture of problem.

I totally appreciate that you can create an organised custom list on plugins, I have one. But that's not what's happening here. Your all talking about the plugin limit on the menu. There exists a seperate plugin limitation bug.

Once cakewalk actually scans over a certain number of plugins within your VSTPlugins folder, it doesn't matter HOW you arrange your plugin list or how few or many you place in you custom list.

Plugins will simply FAIL to appear in the plugin list. You'll put them in, save the custom list, start a project, load your custom plugins list and they'll simply fail to appear where you placed them. It's even random as to which ones will be missing from the list. But they'll always be the same ones missing.

The only solution, like I said previously, is to physically remove plugins from your vstplugins folder.

To me, that goes way beyond organising your plugin list more effectively. It's (another) physical limitation. I'm just saying that for the amount of work involved and the number of complaints cakewalk have received about this issue in the past and also considering that Sonar X1 producer is Cakewalks premiere product... for such a limitation to even exist in this software looks very bad indeed (to me at least).

Sonar has a lot of good features. A lot of time and effort has obviously gone into making this software over the years. But times have changed. Maybe this issue needs to be addressed once and for all.

PS.

All my plugins are perfectly well laid out in my vstplugins folder, such as, so besides the limitation, I also wish there was an option which would just display my plugins folder layout as it is within the actual plugins folder itslef - this is a bare directory list of my VSTPlugins folder:

_Cycling '74 Commercial
_Delays and Modulation
_DirectX (Converted)
_Distortion
_DJ Tools
_Drums
_Drums Replacement
_Dynamics
_EQ
_Filters
_Guitar AmpSims and Tuners
_Listening Speaker Emulation
_Metering
_MIDI
_Misc
_Modular Chainer
_Native
_Panning
_Pitch Tempo Vocal and Harmony
_Restoration
_Reverbs
_Sampler
_Sampler (GM)
_Sampler (Sliced)
_Sampler (Sound Font)
_Sequenced and Multi Effect
_Stereo and Phase
_Surround
_Synths
_Synths (Physically Modelled)
_Synths (VA)
_Vocoders
_Waves

Thanks TheSteven. I'm going to leave this thread here as it is. Once again, we are talking cross purposes. But I think it was important to bring this problem up (again). This is 64 bit software. It shouldn't have this limitation / bug.

The official "windows component doesn't support it" is what it is. But I don't agree with it. Unless the software REALLY requires backward compatability to Windows 95 SDK components. Even in that case, it would be a simple modification to use a different component which does support large lists (listbox or tree).

But again, this isn't what I'm asking for (although it would be nice)...

All I'm asking for is that the number of plugins supported be extended (in other words NOT simply to disappear when the number grows too large).

You are talking about the Windows SDK component. I am talking about not being able to create a viable custom list, because once the number of plugins SCANNED by the scanner has reached a certain number, some plugins are not shown in the custom list (even if you create a custom list with 1 single plugin - if it's a plugin that Sonar refuses to display because the maximum number has been reached - that custom list with that single plugin WILL appear to be empty).

Essentially:

Don't mind making a custom list. No problem. I'll make and use custom lists all day happily.

But

I do mind plugins just vanishing from my custom list, just because there are too many in the VSTPlugins folder. That DOES NOT require any modification to any windows components. It just requires that cakewalk / sonar actually registers them correctly into it's lists and then make them actually SHOW UP in my custom list.

That is simply a software bug. A variable limitation in the program. Some multiple of 256 bytes no doubt that freaks out when randomly when exceeded. Not a limitation imposed by any windows compoenents.

I'll end the thread there. Not much more to be said on the subject. Thanks for listening.

PS. I put in a feature request (again). After all that I'll probably be told its a windows sdk component problem (again) lol. It isn't... *sighs heavily*

To the Poster:

I couldn't agree with the poster more....According to the error message I get, I have over 735 vst's.  X1, when you start it, and it runs the VST scan, it gives an error message stating that you are over the limit.  It is kinda embarassing when you show it to clients.....I also wish that Cakewalk would offer some kind of reserve tank so that I can assign them properly.  I get tired of seeing the same error message every time I start Sonar...

I find it highly amusing that people come on these threads with their wealth (mostly lack) of knowledge and tell you how you should use a forum......What ever happened to "you do you, and I'll do me"?.....Just saying....There are enough judges in the court system....let them stay there.

+1

FastBikerBoy

I get tired of seeing the same error message every time I start Sonar...

Er...... may I suggest switching the scan at startup off then.....

That does not correct this error message from popping up on startup....

Hmm.

I think they should fix this. It's just this "in front of paying clients" stuff that I find silly.