Komplete Kontrol and Windows Problem with categories

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

Post

I got a preset from make and hives category shows as Hive where category for a preset saved on windows shows Hive(x64) . THe same goes for all plugins as i also own bazille and Ace. Same Problem.

Post

Daniel09 wrote:I got a preset from make and hives category shows as Hive where category for a preset saved on windows shows Hive(x64) . THe same goes for all plugins as i also own bazille and Ace. Same Problem.
A preset from the MAC? Apple?

Post

Yes a preset from Mac. get Categorized as Hive. While presets i make get categorized as Hive (x64).

Post

I guess that is because the plugin name from Hive is different between Windows and OSX.
You can try renaming the .dll on Windows but if that works it will give problems with presets created for Hive on Windows.
Doubt if that will even work since NI uses the internal plugin names afaik.

On a whole different note, the ()'s in the plugin name also prevents using images/logo's inside Kontrol/Maschine.
If u-He decides to use the same name for Windows and OSX then using one without the ()'s would be a better choice.

Guess u-He isn't the only one using different names for plugins. NI could consider an extra option in the plugin manager: alias.

Post

Mace404 wrote: Guess u-He isn't the only one using different names for plugins. NI could consider an extra option in the plugin manager: alias.
Yes it's annoying e.g. Oddity 2 on Mac is 'Oddity2_VST2MachO' - I don't know if that causes compatibility issues between Mac and PC versions (it certinaly does when it's the VST ID that is changed, which has also happened) but in any case it would be better if devs stuck to the same names on both platforms, please.

Post

Daniel09 wrote:Yes a preset from Mac. get Categorized as Hive. While presets i make get categorized as Hive (x64).
If you save a preset in the Mac version and put it in the Hive (x64) user folder on Win, does it still load correctly?

Post

Yes loads But with Hive as category. Anything i save Is Hive(x64). Im hoping u-he is gonna take care of this problem. THey are supposed to be on board with making nks updates for there vsts. Ive emailed xfer records and NI gonna have to email Madrona Labs.

I'll share what i find out.

amused ps by the way im wurlt01 that emailed you.

Post

Hi, I had a similar issue in Maschine with ACE. The 64 bit version on Windows is ACE(x64).dll and the () does prevent the images from working. The 64 bit version should really just be ACE.dll like the 32 bit Windows version. I renamed the plugin to ACE.dll and it works fine.

Presets saved in Maschine under the (x64) plugin name will still load so I think it is safe. But they will not be under the same browser entry in Maschine or share images. Also you have to rename the .dll after every update.

Speaking of, really need an easier way to get these presets in the browser of Maschine. I know Diva is coming but was hoping Bazille and ACE would too. Saving one by one and typing in the name is a drag.

Post

Also note that if you rename the 64 bit Windows .dll that you can load the previous presets made and resave them. This will place the preset under the new product/plugin name in the NI browser.

Post

Why are people trying to rename dlls, can't you just rename the user folders between systems, the preset files still load?

Post

It's not a matter of it loading. It loads fine either way. The issue is how it appears in the NI browsers for Komplete Kontrol and Maschine. NI uses the name of the plugin dll to derive the product name that shows in the browser. Further, if you want to create custom images for plugins they will not work with certain special characters like ().

So if you have presets saved with the 64 bit Maschine and others with 32 bit or MAC, you will have two separate products appearing in the browser instead of just one. Some presets under one while the rest under the other. One without any browser images. Renaming the .dll cures this issue.

Post

I think these issues will be resolved once we've finished NKS integration. Without going into any detail, I'm fairly sure that krossplatform support will be komplete.

Nevertheless, we'll send NI a report for this as I think that plug-ins should be identified by Vendor and Plug-In name rather than the file name of the binary.

Post Reply

Return to “u-he”