Can someone explain?

Discussion about: tracktion.com
RELATED
PRODUCTS

Post

Why this?

This is my vst folder
22062015_184855.jpg
This is how it appears in T6

My (E)ffects and (B)ass folders don't show up but VB1, Muon Tau and CM303 are both in the (B)ass folder on my drive yet for whatever reason get lumped in the list.
The Kjaerhus Audio Classic Series are in the (E)xtras folder but show up as their own folder in T6
Sonar plugs which are all in a Sonar folder get the same treatment.

It's just not logical and more than a bit frustrating.


22062015_185059.jpg
You do not have the required permissions to view the files attached to this post.

Post

I have experienced this issue as well as another pertaining to the display of VST plugins (see my thread here: http://www.kvraudio.com/forum/viewtopic ... 2&t=440544). Like you, I have some higher level directories that are ignored while one of their subfolders is included elsewhere. Hopefully the Tracktion folk will get around to investigating when they have time.

Post

Glad we are both reading from the same page.

Post

Taking a stab in the dark here: is it possible that the folders only appear if they contain a plugin .dll file directly within themselves, rather than in a subfolder? My guess is that your E and B folders only contain subfolders.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

jabe wrote:Taking a stab in the dark here: is it possible that the folders only appear if they contain a plugin .dll file directly within themselves, rather than in a subfolder? My guess is that your E and B folders only contain subfolders.
A quick test in the 6.2 beta here would suggest that can indeed cause it.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

It's been that way since v4

Post

Jabe.
Indeed you are right.
As long as there is one vst plugin in the folder it groups them correctly.
My (E)ffects folder did indeed contain all subfolders so I put a limiter vst in and everything appears as it should.

Thought there may have been something in the manual. Oh wait! We don't get a manual!
You do not have the required permissions to view the files attached to this post.

Post

Does this mean if I put a dummy VST in all of my intermediate subdirectories, the nested menus will behave as they did in Tracktion 3?

Post

Maybe or maybe not. I created a text file in a folder, saved it with some text in it, then renamed it to something-or-other.dll. When I did a plug-in search, it said it couldn't load the VST and then didn't show the folder on the list. So perhaps it needs to be a real plug-in. But perhaps my attempt at a fake wasn't good. Or perhaps there were other things I could have tried.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

It has to be a real VST. But you can use a duplicate of another VST. As I said, I noted the bug in V4, Jules didn't consider it a bug.

Post

metamorphosis wrote:It has to be a real VST. But you can use a duplicate of another VST.
which is just going to f**k up plugin menus for all our other applications.
As I said, I noted the bug in V4, Jules didn't consider it a bug.
Well its an undesirable implementation then.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

Hi guys, I've looked into this a bit and as metamorphosis says this is by design.
The plugin paths get condensed to avoid displaying folders that don't contain any plugins (some plugins have settings folders etc. that shouldn't appear in the list).

I'm going to have a look at if we can improve this logic a bit though to give the desired behaviour.

Post

dRowAudio wrote:I'm going to have a look at if we can improve this logic a bit though to give the desired behaviour.
Failing that, can we just have a way of (pre-)populating the custom menu based on one of the available directory structures (eg directory, manufacturer, category).

And better still, extend that with load-/save- to/from files for the custom menu, with a Macro action for loading a specific menu file.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

I've looked into this in more detail and it's not quite as simple as it seems. If we create a new sub-menu for every folder you end up with lots of single item folders e.g. "Users" -> "Dave" -> "Library" -> "Audio" -> "Plugins" -> "VST". This is clearly what the existing concatenation was intended to remove. There's no way to tell how the plugins were originally scanned (they might have been dragged individually onto the window) so we can't remove these root paths.

We might be able to extend the custom menu in the future but don't have any immediate plans to do so. You can easily create a custom menu with a couple of sub menus containing the same plugins if you like to see them organised differently for different occasions.

Post

Not sure if I've got the wrong end of the stick... If I select a folder to search in (eg VSTPlugins), I'd only need to see the subfolders of folder VSTPlugins that themselves have a plug-in at any lower level. If a subfolder contains only one plugin, I'd want to see either the folder containing the plug-in or the plug-in itself. I don't need to see anything at a higher level than VSTPlugins.

Or something!
Last edited by jabe on Thu Jul 02, 2015 3:37 pm, edited 1 time in total.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post Reply

Return to “Tracktion”