KVR Audio

MickGael · Post by **MickGael** » Thu Sep 28, 2006 3:43 pm

Reports are starting to filter in from early users of Cubase 4, and I found this post:

Selection menus in Cubase 4 are structured separately for VST2 and VST3 plug-ins. VST2 plug-ins are sorted into a sub menu named "Earlier VST Plug-ins", from there on the list is generated in relation to folders on the hard disk, where the plug-in files are installed into, just like it is known from previous Cubase versions. VST3 plug-ins are always displayed on top level of the menu. The classification in categories is no longer folder-based but determined by the plug-in itself. The category is effectively stored inside the plug-in. http://forum.cubase.net/phpbb2/viewtopi ... 508#444508

It was confirmed by the moderators.

WTF? This is STUPID - talk about killing usability. I have quite a few plugins, and I rely on the ability to order them as I need to avoid "spagetti" and the imposition of what someone else things is the best workflow.

Major buzz kill for me...

mn · Post by mn » Thu Sep 28, 2006 3:50 pm

I guess it's nice that you can have some metadata in the dll itself now so it can "self-identify". But that's still no reason to disallow user grouping, just use the built in data for the "default" view.

Kind of ironic since Sonar 6 FINALLY allows you to organize them yourself now, into as many different views as you want, while still always reverting to the default if you want.

Dandruff · Post by **Dandruff** » Thu Sep 28, 2006 3:53 pm

mn wrote:I guess it's nice that you can have some metadata in the dll itself now so it can "self-identify". But that's still no reason to disallow user grouping, just use the built in data for the "default" view.

exactly.

Dominus · Post by **Dominus** » Thu Sep 28, 2006 4:06 pm

Nice, and you'll get vendors that just put "Effect" or "Instrument" into the .dll file.

Or, they'll just put their company name in that field.

My copy of Sonar 6 arrives today.

topaz · Post by **topaz** » Thu Sep 28, 2006 4:21 pm

dont worry,

i'm sure it will be fixed in a future update.

Dominus · Post by **Dominus** » Thu Sep 28, 2006 4:23 pm

Doubt it. Steinberg knows better than the users what they want.

If anyone questions it, they'll just delete the posts off of Cubase.net.

zeoy · Post by **zeoy** » Thu Sep 28, 2006 4:28 pm

simple: open the dll in a hex editor and ... nevermind

bduffy · Post by **bduffy** » Thu Sep 28, 2006 4:32 pm

Yuck! I'm sure they'll change that!

zeoy wrote:simple: open the dll in a hex editor and ... nevermind

Please, share! I'm going to need to know how to do that, it would seem...

stag · Post by **stag** » Thu Sep 28, 2006 4:36 pm

Dominus wrote:Doubt it. Steinberg knows better than the users what they want.

If anyone questions it, they'll just delete the posts off of Cubase.net.

You are not telling the truth.
Perhaps the plugs are not organized in folders but allowed some other kind of organization.
Speculation is a lot of fun but i don't see the point here.
You seem not to be a member of Cubase.net, neither a cubase user.

zeoy · Post by **zeoy** » Thu Sep 28, 2006 4:36 pm

bduffy wrote:Yuck! I'm sure they'll change that!

zeoy wrote:simple: open the dll in a hex editor and ... nevermind
Please, share! I'm going to need to know how to do that, it would seem...

I've no idea! I just thought that the meta data could be readable in a good editor. So you could edit them to taste. Or something like that. I thought it would be cumbersome that's why the "nevermind" but if you're desparate you could try

shamann · Post by **shamann** » Thu Sep 28, 2006 4:38 pm

I just hope that the VST3 spec doesn't force other hosts to follow suit. What a massive pain in the ass that would be. I do a lot of plugin testing and generally like to keep alpha/betas filed in a different manner than the rest of my plugins, so not having folder-based sorting would cause me all sorts of needless plugin hunting.

bduffy · Post by **bduffy** » Thu Sep 28, 2006 4:41 pm

zeoy wrote:
bduffy wrote:Yuck! I'm sure they'll change that!

zeoy wrote:simple: open the dll in a hex editor and ... nevermind
Please, share! I'm going to need to know how to do that, it would seem...
I've no idea! I just thought that the meta data could be readable in a good editor. So you could edit them to taste. Or something like that. I thought it would be cumbersome that's why the "nevermind" but if you're desparate you could try

Ah! I thought you meant "never mind", like it's so obvious that anyone could do it. I might have to try that when it comes out. I mean, this will not do; I need control over my plug-in categorization. Man, Steinberg is a weird company sometimes. And I'm a fan!

monsterbeetle · Post by **monsterbeetle** » Thu Sep 28, 2006 4:59 pm

I think this is actually kind of cool, relational structures have all sorts of advantages over hierarchical structures for sorting and querying stuff.

Big question is wheter this system will be relational :
if a plug-in in can happens to fall in more than one category, like being a delay and a distortion and a flanger and a compressor at the same time, will it appear in each of this categories, or will a new category delay_distortion_flanger_compressor be created specially for this plug?

bduffy · Post by **bduffy** » Thu Sep 28, 2006 5:05 pm

Yeah, well take something like CLAS: does it go in "Dynamics" or "EQ"?

whyterabbyt · Post by **whyterabbyt** » Thu Sep 28, 2006 5:13 pm

shamann wrote:I just hope that the VST3 spec doesn't force other hosts to follow suit.

I cant see how. Just because there might be metadata there, there's no conceivable reason to enforce its use inside a host...

Re: Cubase 4: You Have Got to Be Kidding Me!