Others not able to use compiled VST
-
So I made a VST plugin, compiled it, tested it locally, and it worked without any issue. When I sent the .VST3 file to a friend of mine so he could test it, the plugin was not receiving any audio input from the track, thus causing it to be silent. I'm not certain what the issue is given that on my machine it works without flaw. I even tried compiling it as a VST2 DLL file, which yielded the same result. It worked fine for me, but not for the person I sent it to.
-
@RedFireTF2 Stick with VST3. I'm assuming it's an FX plugin? Did your friend test with the same DAW and input audio that you tested with? Have you tested on other systems?
-
@d-healey Yes---the plugin is an FX (amp sim) plugin. We both were using the same DAW (Studio One 7), and were using the same VST instrument plugin. Both of us use Windows 10 and I have a way to test it on another system.
-
@RedFireTF2 said in Others not able to use compiled VST:
I have a way to test it on another system.
Let us know if it works.
-
@d-healey Sorry---typo, I meant to say I do NOT have a way to test it on another system.
-
@RedFireTF2 You can use a virtual machine for testing. There's not much we can do without any more information.
-
@d-healey Alright, will try that. I'll also try sending the VST to a few others I know to see if they're able to use it.
-
@d-healey The people I have sent it to have all had the same issue---no sound is being output from the VST. I haven't had an opportunity yet to set up a virtual machine to test it, but I can at least confirm that more than one person has run into this issue (also being used on different DAWs as well).
I wonder if there is somehow some sort of dependency that I have that others don't have when it comes to the VST, since it works without issue on my main PC. I'm not certain this is the case... all I know is that there is no audio being output from a track which has the VST applied, which to me suggests that there may not be any audio going into the plugin itself.
-
@RedFireTF2 said in Others not able to use compiled VST:
The people I have sent it to have all had the same issue
Send it to me
-
@d-healey Sorry for the late response, here's a link to a .rar file containing it: https://drive.google.com/file/d/1siTKtVI4yFiJ2-XxxCiGKBuAVvRlUpwB/view?usp=sharing
This also has the .lib and .exp file, I'm not sure how necessary it is that you have those but I've included them here just in case.
-
@RedFireTF2 OK, after more testing it seems the issue is with the cabinet IR. I was using the filters.convolution with a .wav file. Originally, I didn't have the file located in the "AudioFiles" folder of the project. I do have "Embed Audio Files" turned on in the project. The audio may have been being considered as an external file for whatever reason and so it was reading it from whatever directory it was in.
However, when I put the IR .wav in the AudioFiles folder and compiled, I was now no longer able to use the VST on my own machine. Compiling it with no convolution/IR and sending it to someone did yield good results as both me and the person I sent it to could use it, but just having to use a different VST for an impulse response (not ideal).
Is there a way I can ensure that the convolution IR .wav will be correctly compiled with the VST? I don't understand why the file isn't being embedded correctly.
-
@RedFireTF2 Ah makes sense, someone else ran into this yesterday, solution in the thread - https://forum.hise.audio/topic/13054/convolution-reverb-wet-level-seemingly-not-working
-
@d-healey Finally got it to work---I swapped from filters.convolution to the separate Convolution Reverb and used the script in the documentation for loading a single .wav file. Worked on my end, sent it to someone else and it works on his end. Very glad to have gotten this all fixed now, thanks for the help!
