VST don't show up in the plugin browser
Hi
I have a problem with loading VST pluins since I changed my computer...
I now run a PC with Win8 and Usine 1.1.008m
When I put a new VST in my VST folder, rescan all : Usine scans it, it does appear in the scanning window, but it doesn't show up in the plugin browser (I only see the VST loaded before, when I had my old PC and Usine 1.1.006a).
I can load them in other VST hosts like Reaper, so I'm sure they're here and work.
I can load them on my old PC with Usine 1.1.006a so I'm sure they can work with Usine.
I hope I'm clear... Anyone can help ?
I have a problem with loading VST pluins since I changed my computer...
I now run a PC with Win8 and Usine 1.1.008m
When I put a new VST in my VST folder, rescan all : Usine scans it, it does appear in the scanning window, but it doesn't show up in the plugin browser (I only see the VST loaded before, when I had my old PC and Usine 1.1.006a).
I can load them in other VST hosts like Reaper, so I'm sure they're here and work.
I can load them on my old PC with Usine 1.1.006a so I'm sure they can work with Usine.
I hope I'm clear... Anyone can help ?
So I now run my old Usine version 1.1.006a (32bits) on my new laptop Win8 64 bits, and the new plug in do show up...
What's the bug ?
What's the bug ?
-
woodslanding
- Member
- Posts: 1327
- Contact:
you can't run 32 bit plug-ins in 64 bit version of HH. Could that be the problem?
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
OK thanks Woodslanding, it's exactly the point... I didn't know the plugins were bits sensitive.............................
Is there a way to know if a VST is 32 or 64 bits when you have a .dll (I don't see anything in the properties) ?
Thanks.
Is there a way to know if a VST is 32 or 64 bits when you have a .dll (I don't see anything in the properties) ?
Thanks.
If you guys look for some mda vst 64bits : http://sourceforge.net/projects/mda-vst ... p_redirect
-
woodslanding
- Member
- Posts: 1327
- Contact:
Ha, ha, wouldn't that be convenient then???XpiR wrote:OK thanks Woodslanding, it's exactly the point... I didn't know the plugins were bits sensitive.............................
Is there a way to know if a VST is 32 or 64 bits when you have a .dll (I don't see anything in the properties) ?
Thanks.
I guess the best way to tell is whether HH recognizes it or not!
Actually it is a rare 64 bit host that doesn't support 32bit vsts natively, so it's not a problem most folks have. I hope we will see this in a HH upgrade sometime soon. For now, I'm only using 64bit vsts.
There is jBridge, but it seems klunky. You can look into that, it might work for you.
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
@ Magickz : Just their name ! But I was looking for white/pink noise generator, and I found one in this free VST family
thanks, Xpir.
I also think that JBridge is clunky, but some people experience it as a reliable solution. So, I guess the results depend on the environment where it is installed.
I think it is tricky to deal with 32 and 64 bit plugins.
I have commercial plugins that are not available in 64 bit, and others that are not available for 32 bit - I want to use them all together. To get a better overview first I tried to sort them into two separate directory structures, "...32bit", "...64bit". But then I realized that not all installers allow the user to install the plugins into two different directories. Other plugins might stop working if you move them manually into another directory. Now it is a little bit messy on my harddisk 
Sometimes they have some hint like "64bit" in their filename. Sometimes you find it in the documentation or readme file. But not always. You mention you have Reaper. There you can create an empty track, insert an FX or instrument. In the "add fx" dialogue window you can see the information "(x86)"; that indicates the 32 bit plugins. All others are 64 bit.
Btw.: I have no idea about your requirements. Would the "JS" noise generators in Reaper work for you? Then they could also work for you in Usine, no matter if you decide for 32 or 64 bit. http://www.cockos.com/reaper/reaplugs/
I also think that JBridge is clunky, but some people experience it as a reliable solution. So, I guess the results depend on the environment where it is installed.
I think it is tricky to deal with 32 and 64 bit plugins.
Sometimes they have some hint like "64bit" in their filename. Sometimes you find it in the documentation or readme file. But not always. You mention you have Reaper. There you can create an empty track, insert an FX or instrument. In the "add fx" dialogue window you can see the information "(x86)"; that indicates the 32 bit plugins. All others are 64 bit.
Btw.: I have no idea about your requirements. Would the "JS" noise generators in Reaper work for you? Then they could also work for you in Usine, no matter if you decide for 32 or 64 bit. http://www.cockos.com/reaper/reaplugs/
Thanks for the tip, so I'll take a look at the reaplugs, I didn't notice their were some noise generators among them... (and I'm not a super fan of reaplugs........).
In Reaper you add an FX, and find it in the JS category. In Usine you load the ReaJS plugin and find pink and white noise there...
Oh, and I just discovered the "oscillator" module in the Usine patching system. It can also produce some noise.
maybe that's even easier for you... and more elegant than using a plugin.
http://www.sensomusic.com/wiki2/doku.ph ... llatorbase
Oh, and I just discovered the "oscillator" module in the Usine patching system. It can also produce some noise.
http://www.sensomusic.com/wiki2/doku.ph ... llatorbase
I can't believe that Usine doesn't run 32 bit plugins. That's a real shame. This seems like a big oversight. I gave jBridge a try to get DtBlkFx to load, but still no joy. DtBlkFx is of my favorite VSTs. I can't use a large chunk of my plugins. Please fix this.
-
secretkillerofnames
- Member
- Posts: 97
- Contact:
There is a 32 bit version of HH you can download and use. Won't that help?symplx wrote:I can't believe that Usine doesn't run 32 bit plugins.
I have an interesting issue re: VSTs on the Windows machine.
I am putting all my 64bit plugins into C:VSTPLUGINS.
Some of them (like Melda and Soundtoys) create their own subdirectories.
These plugins weren't showing up until I included the subdirectories in the plugins folder setting. Is it not possible to have HH scan subdirs?
I could use the 32 bit version but then the 64 bit VSTs won't work. I just removed JBridge. It was causing too many problems, breaking my patches. Guess I'll use the 32 bit version for this plugin. It's not ideal but will have to do for now. Why is this a problem? Is it that difficult to have both usable in one program?
Secretkillerofnames, you're right, that seems to be the best way for now. Most of my VSTs are 32 bit, or have 32 bit versions. I had a 'no audio' error in the 32 bit version. Fixed it with this driver: http://www.asio4all.com/
Plugins are the main point of instability in any DAW/host. So trying to support 32-bit and 64-bit at the same time makes a complex situation even more complex.symplx wrote:I could use the 32 bit version but then the 64 bit VSTs won't work. I just removed JBridge. It was causing too many problems, breaking my patches. Guess I'll use the 32 bit version for this plugin. It's not ideal but will have to do for now. Why is this a problem? Is it that difficult to have both usable in one program?
In my experience, there are not very many DAWs which support both. I can only think of Bitwig and Reaper, at the moment.
If Usine could have a similar sandbox as Bitwig, it would be awesome. But really I would prefer the devs spend their time on other parts of the software than spending time making the 32-bit / 64-bit bridge.
It seems to me that the normal choice, and usually the only one, is to run a 32-bit host for a 32-bit plugin. A creative constraint. Or you can think of it the other way, and only 64-bit plugins. Another creative constraint.
Who is online
Users browsing this forum: Google [Bot] and 94 guests
