Playing the devil's advocate, is everything up to date??mrrap4food wrote:HI,k0llege wrote:If you come here through a google search and still have the Problem in lets say FL Studio 11, the workaround is as follows (GfX-Related issue as stated above is the cause):
Load the Waveshell in FL (it will be black)
Click the Gear symbol of the Wrapper (options)
On the first (options) Page that you see select the option "DPI-Aware"
Click the Gear symbol again to return to the Plugin in the Wrapper (still black)
Close the Wrapper
Bring the Wrapper up again through the Mixer panel.
-- should be fixed. (Win7 x64, x32 and x64 VST version)
im having a problem where when i try to open certain files that contained this plugin, it shows up as a black box and fl studio says "The zeta+2 plugin can not be found", but if i open up a new channel with this, it works but i cant open older sessions with the already made sounds, i tried your method, but when i try to get the gear symbol to open the options it says "select a plugin from fl studio " so it wont load the zeta plug in from a existing session, i can only open it to make new sounds which i cant find what sound it was, im using the 64bit and im assuming when i made it , it was a 32 bit?
thx
Waves Black screen problem ( help )
-
simon.a.billington simon.a.billington https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=341278
- KVRAF
- 2375 posts since 12 Nov, 2014
-
- KVRer
- 5 posts since 15 Nov, 2007
Your Problem is not related to this topic, because what you are describing only occurs if you have a changed version of the .dll installed. Meaning: formerly you might have used Zeta V1 and the .dll was called zeta1.dll and then you made a new setup, all was lost or changed alot of things and now you reinstall but you install the V2 of zeta and the installed .dll is called zeta2.dll ...
Think about this. Anything like this might have happened in your past.
Now if you open your flp, the reference in the flp is still the dll that you used in the first place. FL Studio relies on .dll names! (And then, the VST Wrapper also expects *EXACTLY* that .dll version, renaming it will only help if you know what you are doing)
If you can make new sounds whith some (Zeta is just a placeholder for every synth here) Synth that you think you formerly had: it has to be the *exact* same version you had installed when you made that track in the first place. Otherwise: crash, burn, SNAFU, FUBAR.
tl;dr: FL Studio relies on the .dll names of the VST Plugins installed in the first place and then, the Wrapper inside FL Studio expects it to be exactly that version - tampering with names or installing updates of Synths should be done only IF YOU KNOW WHAT YOU ARE DOING.
NOTE: i'll give no further support on this. RTFM
Think about this. Anything like this might have happened in your past.
Now if you open your flp, the reference in the flp is still the dll that you used in the first place. FL Studio relies on .dll names! (And then, the VST Wrapper also expects *EXACTLY* that .dll version, renaming it will only help if you know what you are doing)
If you can make new sounds whith some (Zeta is just a placeholder for every synth here) Synth that you think you formerly had: it has to be the *exact* same version you had installed when you made that track in the first place. Otherwise: crash, burn, SNAFU, FUBAR.
tl;dr: FL Studio relies on the .dll names of the VST Plugins installed in the first place and then, the Wrapper inside FL Studio expects it to be exactly that version - tampering with names or installing updates of Synths should be done only IF YOU KNOW WHAT YOU ARE DOING.
NOTE: i'll give no further support on this. RTFM
"It was a nice day, then he was run over by a truck."