Redirecting saved VST's to new VST path
Redirecting saved VST's to new VST path
Hello! I've got a bit of a problem.
I've reorganized my VST folder so that everything is nice and tidy and in a completely different folder scheme. Instead of all .dll files being in the root VST folder, all VST's are put in separate folders named after the developers. For instance: "VST/de la Mancha/subatomic.dll" vs. "VST/subatomic.dll".
Now, the problem with this is that starting up Buzz and loading an old song file prompts an error message stating "Sorry, plugin is missing... <file path> '<VST name>'".
The obvious solution would be to right click on all offending machines and reload them with the proper VST, however all parameters are lost and this method is incredibly slow. Is there any other way to fix this?
I've reorganized my VST folder so that everything is nice and tidy and in a completely different folder scheme. Instead of all .dll files being in the root VST folder, all VST's are put in separate folders named after the developers. For instance: "VST/de la Mancha/subatomic.dll" vs. "VST/subatomic.dll".
Now, the problem with this is that starting up Buzz and loading an old song file prompts an error message stating "Sorry, plugin is missing... <file path> '<VST name>'".
The obvious solution would be to right click on all offending machines and reload them with the proper VST, however all parameters are lost and this method is incredibly slow. Is there any other way to fix this?
Re: Redirecting saved VST's to new VST path
Odd, it should find the plugins after your reorganizing, tested here and it works. Did you add the new vst folder in the loader preferences?
Re: Redirecting saved VST's to new VST path
Yes sir!
It seems like it loads a lot of plugins fine, but not those. I'm on Windows 10 btw.
EDIT: Figured it out. It's a discrepancy between x64 and x32. If a song is saved with x32 VST plugins, even if the x32 VST plugin doesn't exist, it won't fall-back to loading the x64 plugin.
It seems like it loads a lot of plugins fine, but not those. I'm on Windows 10 btw.
EDIT: Figured it out. It's a discrepancy between x64 and x32. If a song is saved with x32 VST plugins, even if the x32 VST plugin doesn't exist, it won't fall-back to loading the x64 plugin.
Re: Redirecting saved VST's to new VST path
I could open an open dialog where you can select the missing plugin by hand.
Re: Redirecting saved VST's to new VST path
Yes that doesn't work yet, but I have it implemented now. It will work if the plugins share both the same unique identifier. Also the open dialog stuff for selecting by hand is implemented now.EDIT: Figured it out. It's a discrepancy between x64 and x32. If a song is saved with x32 VST plugins, even if the x32 VST plugin doesn't exist, it won't fall-back to loading the x64 plugin.
Re: Redirecting saved VST's to new VST path
Sorry for necro posting but am I correct in saying PVST should load the x64 version of a missing x32 VST automatically if the plugin ID is the same, and if not it should prompt you to locate the dll?polac wrote:Yes that doesn't work yet, but I have it implemented now. It will work if the plugins share both the same unique identifier. Also the open dialog stuff for selecting by hand is implemented now.EDIT: Figured it out. It's a discrepancy between x64 and x32. If a song is saved with x32 VST plugins, even if the x32 VST plugin doesn't exist, it won't fall-back to loading the x64 plugin.
Loading a song saved with x32 VSTs, none of them load automatically (but that may just be the ID thing) so I locate the x64 version in the dialog that pops up. After the song has finished loading however, double-clicking the VST machines just displays the open dialog and if I then select the x64 version again it loads the plugin but with the default settings.
Setting up a new system should be a happy time but oh boy it sucks!
edit: Should say that this is in 32bit Buzz. 64bit Buzz loads the VSTs fine but then there are compatibility problems with all the native Buzz machines.
Re: Redirecting saved VST's to new VST path
Checking the code, there might be still a bug, I'll try to fix it.
Re: Redirecting saved VST's to new VST path
I think I found the bug. However no warranty that the fxb/fxp data is compatible on load. The same uniqueid is no warranty. Will update the loader package the next days after some testing.
Re: Redirecting saved VST's to new VST path
Thanks polac! Good point about data compatibility. Will it crash Buzz if the data is different or would the loader catch it and just crash that machine?polac wrote:I think I found the bug. However no warranty that the fxb/fxp data is compatible on load. The same uniqueid is no warranty. Will update the loader package the next days after some testing.
- HerrFornit
- Posts: 435
- Joined: Sat Feb 25, 2017 12:27 pm
- Location: Dortmund
- Contact:
Re: Redirecting saved VST's to new VST path
Hey polac, when you are going into the code, if it is not to much work, could you please change the display length oft the path in plugin information (full path?)?
Many thanx !!
Many thanx !!
Re: Redirecting saved VST's to new VST path
I'm not sure. Firstly it checks the id of the fxb/fxp, if it doesn't fit to the vst the loading is aborted. If it's a chunkbased fxb it could load wrong data, if it's parameterbased fxb it's no problem.Thanks polac! Good point about data compatibility. Will it crash Buzz if the data is different or would the loader catch it and just crash that machine?
Re: Redirecting saved VST's to new VST path
You still can resize the rightmost column in the topright, then scroll to the right.Hey polac, when you are going into the code, if it is not to much work, could you please change the display length oft the path in plugin information (full path?)?
Re: Redirecting saved VST's to new VST path
So it probably depends on the individual VSTs. Not to worry, it's amazing it works at all! Much respect for the apparently seamless 32/64 bridging. You rok!polac wrote:I'm not sure. Firstly it checks the id of the fxb/fxp, if it doesn't fit to the vst the loading is aborted. If it's a chunkbased fxb it could load wrong data, if it's parameterbased fxb it's no problem.
- HerrFornit
- Posts: 435
- Joined: Sat Feb 25, 2017 12:27 pm
- Location: Dortmund
- Contact:
Re: Redirecting saved VST's to new VST path
o jesus, yes !polac wrote:You still can resize the rightmost column in the topright, then scroll to the right.Hey polac, when you are going into the code, if it is not to much work, could you please change the display length oft the path in plugin information (full path?)?
to simple for me
thanx!!
Re: Redirecting saved VST's to new VST path
Well there could be also non-resizable list view columns, but these are resizable.
Re: Redirecting saved VST's to new VST path
Sorry to keep pestering Polac but are you any closer to releasing this fix? The wait is killing me!
Re: Redirecting saved VST's to new VST path
It's ready, i only have to upload it, i'm lazy sorry.