When I try and install Scarbee VKFX on the receptor, it fails. Looking in the log it says that it fails in the 'signing'.
I think that there is a previous version from a previous user of the receptor that is blocking it.
Scarbee VKFX does not list on the 'uninstall plugins', but there is a folder for it on 'Banks and Patches'.
Any ideas how I can deal with this?
Thanks
Peter
Scarbee VKFX on receptor
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Peter,
I have VKFX working for me, and it was installed as a typical "unsupported app".
Here are some things you might try:
1.) remove the VST and any associated files with it (eg. from another computer, mount the receptor drive, go into the unsupported folder, and trash any version that you see).
2.) Flush the plugin cache
(You should be able to do this via the front panel as such: Hold down the "Multi" button, and quickly press the "power" button 3 times (keep holding the multi while receptor resets. After the GUI returns, you should hear the drive chugging away - Receptor is now rescanning your plugins, and it should take something like 10 minutes to complete. Afterwards, you should check your FX list, and verify that you do not see VXFX available).
3.) Reinstall VKFX as an unsupported plugin.
I try to create a separate subfolder or hierarchy under my 'unsupported vstis' folder. eg, create 'unsupported vstis/scarbee/vkfx'). Place the vkfx dll and associated files in this folder. Make sure that you do not have any of the "Receptor Created" xml files here (eg. reset.xml or various config.xml files) - only the files supplied by Scarbee).
4.) go to the 'System' Tab, check the 'check unsupported folder' checkbox, and verify that receptor wishes to install 1 item. Go ahead and install.
5.) At this point VXFX should be available to you in your FX list.
6.) If a previous receptor owner had VKFX installed, and had specific patches in "Banks and Patches" that you wanted removed, you should be able to delete these from the ('save') banks page.
This is all from memory, hope it helps.
Regards,
Kevin L
I have VKFX working for me, and it was installed as a typical "unsupported app".
Here are some things you might try:
1.) remove the VST and any associated files with it (eg. from another computer, mount the receptor drive, go into the unsupported folder, and trash any version that you see).
2.) Flush the plugin cache
(You should be able to do this via the front panel as such: Hold down the "Multi" button, and quickly press the "power" button 3 times (keep holding the multi while receptor resets. After the GUI returns, you should hear the drive chugging away - Receptor is now rescanning your plugins, and it should take something like 10 minutes to complete. Afterwards, you should check your FX list, and verify that you do not see VXFX available).
3.) Reinstall VKFX as an unsupported plugin.
I try to create a separate subfolder or hierarchy under my 'unsupported vstis' folder. eg, create 'unsupported vstis/scarbee/vkfx'). Place the vkfx dll and associated files in this folder. Make sure that you do not have any of the "Receptor Created" xml files here (eg. reset.xml or various config.xml files) - only the files supplied by Scarbee).
4.) go to the 'System' Tab, check the 'check unsupported folder' checkbox, and verify that receptor wishes to install 1 item. Go ahead and install.
5.) At this point VXFX should be available to you in your FX list.
6.) If a previous receptor owner had VKFX installed, and had specific patches in "Banks and Patches" that you wanted removed, you should be able to delete these from the ('save') banks page.
This is all from memory, hope it helps.
Regards,
Kevin L
-
- KVRist
- 387 posts since 24 Aug, 2004
Try this if it is different than what you did:hutchi0 wrote:Many thanks for taking the time to suggest these things. The VKFX still refuses to install.
Peter
1.Do all that was suggested above again
2. Forget about the receptor for a bit, and Install and authorize the plugin on your PC.
3. Now copy the entire folder created by the above process into "Unsupported Plugins" on the Receptor, and install as per usual.
This has worked for me both times I needed to install VKFX.
-
- KVRian
- 1116 posts since 22 Apr, 2005 from Nashville, TN USA
Also make sure you have the 1.5 OS on Receptor. The older release has certificates that are old/expired so any "signing" operation will fail.
-
Bryan@MuseResearch Bryan@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9067
- MUSEician
- 618 posts since 18 Sep, 2003 from Silicon Valley
Hi there
I just installed VKFX on a Receptor for a customer, and it works fine. There are actually instructions that come with VKFX on how to install it on Receptor. Only one caution though: once you enter in the serial number into the PREFS window on the plugin, you don't want to click on that button again... it is very easy to wipe out the entered serial number info and the plug-in will commit suicide...
And Hybernation makes a great point... you really need to be up to 1.5 for this to go smoothly...
Cheers
Groovology
I just installed VKFX on a Receptor for a customer, and it works fine. There are actually instructions that come with VKFX on how to install it on Receptor. Only one caution though: once you enter in the serial number into the PREFS window on the plugin, you don't want to click on that button again... it is very easy to wipe out the entered serial number info and the plug-in will commit suicide...
And Hybernation makes a great point... you really need to be up to 1.5 for this to go smoothly...
Cheers
Groovology
-
- KVRer
- 10 posts since 19 Jun, 2006
Hi there,
I also am having problems installing Vintage FX. Or more correctly, it installs correctly, but when instantitated, it presents only a black screen with no UI. I've had a similar problem on my PC if I attempt to move the DLL to a different directory after installing it. In fact, that is what happened when I first grabbed the DLL to install on my Receptor - I accidentally grabbed the wrong DLL, forgetting that I had installed to an external hard drive.
At any rate, after I realized my mistake, I uninstalled the previous installation as per the instructions, and was able to reinstall a version from another system that I verified was working properly before copying over. I'm still getting the black screen when I instantiate the DLL. Has anyone run into a similar problem on the Receptor and know how to fix it?
Thanks,
Matt
I also am having problems installing Vintage FX. Or more correctly, it installs correctly, but when instantitated, it presents only a black screen with no UI. I've had a similar problem on my PC if I attempt to move the DLL to a different directory after installing it. In fact, that is what happened when I first grabbed the DLL to install on my Receptor - I accidentally grabbed the wrong DLL, forgetting that I had installed to an external hard drive.
At any rate, after I realized my mistake, I uninstalled the previous installation as per the instructions, and was able to reinstall a version from another system that I verified was working properly before copying over. I'm still getting the black screen when I instantiate the DLL. Has anyone run into a similar problem on the Receptor and know how to fix it?
Thanks,
Matt
-
Bryan@MuseResearch Bryan@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9067
- MUSEician
- 618 posts since 18 Sep, 2003 from Silicon Valley
I've installed it on two different Receptors, and have never seen this problem. Is it the latest version? What version of Receptor software are you using?
Cheers
Groovologyh
Cheers
Groovologyh
-
- KVRer
- 10 posts since 19 Jun, 2006
Version 1.2 of FX - I just did a crossgrade of Vintage Keys, but not the FX as I already had it and had read on this forum that it could be installed as an unsupported plugin. The Receptor is running the latest OS version.
Thanks much,
Matt
Thanks much,
Matt
-
- KVRer
- 10 posts since 19 Jun, 2006
Well, third time's the charm I guess. I just retried with the suggestion to copy over the entire folder from the source Windows system and that did the trick. 
Thanks for the tip!
Matt
Thanks for the tip!Matt
-
- KVRer
- 7 posts since 26 Dec, 2004
Hello matt,denkom67 wrote:Well, third time's the charm I guess. I just retried with the suggestion to copy over the entire folder from the source Windows system and that did the trick.
Matt
I'm having the same problem. What folder do you copy from your PC? Is it Programs files/Scarbee folder you are copying from?
Thank You
Dadmac