Plugin directory structure question

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I don't understand what is the purpose of the Diva folder:

...\U-he\Diva.data\Presets\Diva\BS Deep Space Diva.h2p --> Diva browser > Local > BS Deep Space Diva
...\U-he\Diva.data\UserPresets\Diva\My Preset 01.h2p --> Diva browser > User > My Preset 01" folder in Diva's browser

The Diva folder doesn't show up in Diva's preset browser at all, besides, it adds unnecessary complexity to the directory structure, here's an extreme case just to illustrate my point:

...\U-he\Diva.data\Presets\Diva\Definitely Diva\Oh yes this is Diva\BS Deep Space Diva.h2p

I was expecting this to look like this (basically skip the Diva folder altogether):

...\U-he\Diva.data\Presets\BS Deep Space Diva.h2p --> Diva browser > Local > BS Deep Space Diva
...\U-he\Diva.data\UserPresets\My Preset 01.h2p --> Diva browser > User > My Preset 01

Another problem is that it is not very clear where users are supposed to put third-party presets. On one hand, there is a "THIRD PARTY" folder in Diva browser > Local > THIRD PARTY, but on the Diva browser > Local is supposed to be just the stock presets, not presets added later after installation. I'm curious how U-he intends this to be used.

Cheers

Post

Let's look at it in a more generic perspective:

...\U-he\Product-Name.data\Presets\Plug-In-Name\some preset.h2p

And a bit more specific where Product and Plug-In have different names:

...\U-he\Zebra2.data\Presets\Zebralette\some zebralette preset.h2p

While Diva is a "lonely" plug-in, many of our offerings come in bundles: Filterscape, Repro, Uhbik, Zebra2. Hence, in some parts of the folder hierarchy there is an "extra level" to account for that, while other parts (e.g. UI resources, license files etc.) are shared. It surely seems redundant in Diva, but then Repro-1 and Zebra2 both started out as single plug-ins which became bundles. There are requests for FX versions of synths, so I'd never rule out that more products become bundles.

#-------

We see "Local" as "part of the installation" and "User Presets" as data you add. We however leave it up to users. If you wish to add soundsets there, you can. If you wish to only put your own creations in User, you can. If you wish to ignore User, you can. Historically "User" only existed on Mac due to the given file structure. We only recently added it to Windows to make this more consistent across platforms.

(Our upcoming soundset installation tool - see Hive 2.1 beta, Bazille - installs soundsets into the User area)

#-------

"THIRD PARTY" is a faux pas naming convention in this context. These were presets contributed by external sound designers to be included with Diva, but which were not part of our own effort to create a factory library. In Hive we called it "Treasure Trove", which is less misleading. We recently moved to make these collections optional downloads since tagging and macro controller assignments put an extra burden on our content managers. We also introduced the bank name feature to distinguish between versions of the factory library and non-factory content.

Post

Urs wrote: Fri Feb 12, 2021 6:23 am Let's look at it in a more generic perspective
Thanks Urs, that makes sense now :tu:

Post

Urs wrote: Fri Feb 12, 2021 6:23 am Let's look at it in a more generic perspective
Thanks Urs, that makes sense now :tu: BTW the bank name feature is that just Zebra 2?

Post

Bank name comes to all plug-ins which have the tagging browser... slowly to all of them...

Post Reply

Return to “u-he”