Problem installing unsupported vsts'

[schubert]

I ahve tried to install the SR202 drum machine and the superwav synth, I have dragged the files to the drop installer and nothing happens apart from a great big 0 files installed x amount of files failed. These are supposedly two unsupported VSTs' that will work on the receptor and two virtual instruments that I use extensively. Has anybody got any ideas about what I'm doing wrong?

[looneytunes]

Hi Schubert,

Probably nothing you are doing wrong - probably some extra windows dlls required. Check the system log (In the reports folder).

Also for more info, see this post.

Regards,
Kevin L

[schubert]

Cheers looneytunes, I've had a look in the system log but unfortunately all I get is this message
Aug 23 05:44:42 Receptor-1 rm-host: SystemInterface.cpp::install_patches[913]: Not a patch file: /c/Drop Installers Here/superwave-p8-16/SUPERWAVEP8.dll

Heeeeeeeeeeeeeeeeeeeeelp!

[ajswanson]

This is not how you install unsupported VSTs. You need to drop them in the Unsupported folder. Place them in the /Program Files/VST Plugins/Unsupported Plugins/ folder. I think those are the names, I am not in front of my Receptor right now.

This is covered in the manual so that is another good place to look. IN the Setup tab on the Remote, make sure "include Unsupported Plugins folder" is checked. Then it will detect new plugins that you drop in there.

The Drp Installers Here folder is for Official Plugs only.

[looneytunes]

Hi again,

I think you are mixing up install methods. For an unsupported install, you typically copy your program files or folders (eg. superwave-p8-16) under Receptors 'Unsupported' folder (ie /c/Program Files/VSTi Plugs/Unsupported Plugins/superwave-p8-16) (I'm not sure of exact dir names, but that path should be close). Then you go to the System Tab, where the 'Install' button is. Make sure the checkbox 'Install Unsupported' is checked. The Install button should update to tell you the number of newly scanned .dll's it is ready to install. Click the install button, and then SUPERWAVE should be available in your instruments list.

The 'Drop Installers Here' folder is typically for (Muse Provided) plugin bundles (eg. bundles that have the suffix '.mrpk'). You can also drop FXP/FXB patch bundles in that folder, and Receptor will install them.

Remove your contents from the 'Drop Installers Here' folder, and try what I described - that should get you going.

Regards,
Kevin L

[schubert]

Thanks guys I am indebted to you, I must admit I do have a tendency to man read manuals. Thanks guys I don't know what I'd have done without your help, respect is due.

[apex14]

Hi Listers,

I have installed the Superwave P8 in my Receptor C, and while it sounds wonderful, everytime I try to go to the edit screen, it resets the Receptor. Does anyone know a fix for this? I really want to tweak my P8!

Thanks,

Steve

[looneytunes]

Hi Steve,

Not sure what is happening from your description. You should get some clues of what is happening by looking at the entries in the system log. If you are missing a .dll or some other such problem, you can typically figure this out by the messages there.

Regards,
Kevin L

[apex14]

Thanks Kevin. I actually have checked the system logs as well as the initializing logs and they don't even show the Superwave being installed! I heard back from Superwave and they have no idea, then I heard back from Muse and they think the P8 may be trying to access a .dll that isn't found on the Receptor like it is on Windows machines. Superwave confirmed that the P8 does not in fact search out any .dll files to run, so I think I'm just stuck until an epiphany presents itself.

Thanks very much for the help, and please let me know if you have any other thoughts regarding this.

Steve

[looneytunes]

Hi Steve,

One other quick thought - I think I once came across a windows dependency tool that could somehow determine which .dlls a given app is dependent on. You can probably find something like this with a quick web search. If you can run something like this on a windows machine, you should be able to then apply the missing .dlls to your Receptor system. Typically you don't need to go this route, because you usually find system messages that tip you off to missing .dlls in the log (so I'm a bit surprised that you saw nothing).

I'll see if I can try out P8. Which Receptor Model / OS are you trying to install on?

Regards,
Kevin L

[johnrule]

I think I once came across a windows dependency tool that could somehow determine which .dlls a given app is dependent on.

Dependency Walker

JR

[apex14]

Hey Kevin,

I am using a Receptor 1 Rev C, 1.7 OS. Thanks for all your help. I have not heard of the dependancy tool you're talking about. Is that something I would need to install onto the Receptor, or is it something for me to run on a Windows machine to figure out which files I might be missing, and then translating those to the Receptor?

Again, thanks,

Steve

[looneytunes]

Hi Steve,

I was suggesting that you use the Dependency walker on your PC. One other thing to look for - often PC installers have a checkbox that opens some installation log, showing what the installer is putting on your PC. If you look at this log (during an install on a PC) you can often find .dlls (and registry keys) that are being created/installed by the installer. With this knowledge, you can put the appropriate .dlls/keys on your Receptor.

Good Luck!
Kevin L

PS. Thanks John for the link!

[apex14]

Thanks tons Kevin, and also thanks John for the link. I have opened the P8.dll on Dependency Walker. I have no idea what I'm looking at, but I'll figure it out!

Have a great night guys,

Steve

PS... This is why I think sites such as KVR are so valuable.

[looneytunes]

Hi Steve,

I was able to install (normal unsupported method) SuperWave P8 and Tarkus both on my Receptor 2 (OS 1.8 ) yesterday without adding any .dlls. This could mean that either (1) I already had any .dlls required for these plugs (unlikely), (2) there are differences in system plugins/support between OS 1.7 and OS 1.8 (most likely), (3) some other configuration issue.

I have a Receptor 1 Pro (Rev C), and I'll try to install on this tonight.

Hope this helps. Regards,
Kevin L