Fruity Loops Plugins Pack Torrent
Myong Killings
I use Fl Studio and since some updates of Fl Studio and Native Access my plugins in the Komplete Kontrol player and Maschine doesnt work any more. Also in my Kontakt player comes the issue, Player too Old on my new ashlight instrument but all other ones work.
I have updated everything, in standalone everything works normal. But when i open it in Fruity loops my Plugin folder is empty. All locations are correct. Ive already, reinstalled everything, tried to relocate everything. I did not delete or move any folders.
First Check that the Version numbers of the Plugins are the same as the version Numbers of the Standalone Apps (All Three), if not, then when you upgraded, more than likely the Plugins did not get updated which would cause this issue. Make sure that Fruity Loops is scanning the Latest Versions of the plugins.
Hi, I Installed yesterday Fruity Loops which installed ASIO and ASIO4ALL. Today I noticed that EQ APO stoppped working in a weird way. If I start a song or any audio playback, there is no audio. I have to interract with any setting in the EQ APO Editor, like toggle a VST plugin or click on any VST slider, knob. Then the audio starts playing like I would have opened a gate. So when there is no sound ouput then this gate closes again. A workaround for this is to open a song in MPC-HC and click on pause. Then the "audio gate" stays opened. This is kinda a workaround.
So I uninstalled Fruity Loops with everything that came with it and also unistalled audio, display drivers, deleted all audio drivers in the device manager. Installed EQ APO again. I can not get my normal functionality back. I had the same behaviour on my Windows 7 machine, so this can't be a coincidence.
It could be that the same faulty driver(s) are automatically installed again after uninstalling it/them in the Windows device manager. On the other hand, what you did was the correct way. Uninstalling the problem audio driver(s) should have been enough.
This "audio gate" issue has been reported on this forum a few times. The workaround by stopping and starting audio is also noted. Most of the time it was a VST plugin issue but I'm not sure if it was always the case.
Okay it's "nice to hear" that I'm not the only one with this issue, this way it is more likely to get solved at some point. I also had the same behaviour on Windows 11. So it seems not to be OS related.
At the end of the day it is EQ APO that has issues working as intended. Every other program runs normally. So EQ APO should "know" what it needs to run properly (registry, drivers, system settings etc.) and give you something like "reset to default" function. So you could always rely on it. Because now the only thing left is to wipe the system and start from scratch, and this wouldn't even work for me because I need fruity loops installed.
I wish this was really wish true but it can't, well not easily. Usually when a serious problem arise which can't be dealt with through the available trouble shooting options this problem isn't Equalizer APO. It's commonly the poor implementation of the manufacturers of audio drivers. But to their defense it isn't easy to create an audio driver as the documentation of Microsoft is quite poor. Or the usage of VST plugins can be troublesome too. Unfortunately the developer hasn't provided us with an answer.
This doesn't happen often. Only a few occurrences are reporting and they may not even be Equalizer APO related. However, there are 2 issues. First, uninstalling Equalizer APO by simply deleting its program files map is a no go. This means that the audio drivers aren't properly reset and must be installed again. Second, a Windows update might come with a problem driver. Of course such a driver might work perfectly without Equalizer APO. But putting Equalizer APO on it might prove difficult.
Unfortunately I'm not aware of this. Of people I've supported a tiny few have installed Windows again to get an audio device working (which is a good reset, I guess). I'm guessing this is about the default (old) drivers being installed. In some occasions the Windows update process that follows after installing Windows again made things worst again. It's all quite fuzzy that I haven't got a good grip on it. Then again Equalizer APO has always work for me (on 3 laptops and 3 computers). Anyway, I'll keep on trying to help although I haven't got a solution.
You welcome :) Actually I was thinking of reaching out to you. I guess this isn't possible but would there be a way of having peace as a VST plugin? I am so familiar with the way the EQ works that it would be awesome to use it inside Cubase.
I actually also never had real problems, it always worked but with this "audio gate" workaround.
There could be a dark mode, and also profiles would be awesome.
I recently moved from Win7 to 10 and it was a big upgrade to not have to deal with this issue and now having it back is frustrating ^^
Hey I made some progress, it turns out that fabfilter plugins are causing this issue. When I use plugins from other vendors it works. Most of my setup is fabfilter though ^^
So I guess fruityloops scanned all installed plugins on startup and in this interaction something bricked.
You can reach on the Peace forum.
Unfortunately Peace can't by used as a VST plugin. As it's an interface for Equalizer APO it isn't an audio program. Btw. Equalizer APO can't be used as plugin either as it's different to the VST plugin structure. It's structure is according to a Windows Audio Processing Object, APO. However, it is possible to take both source code, Peace and Equalizer APO as a base for creating a VST plugin. But I won't take that on as it's a big project.
"Fabfilter" mmm sounds familiar. This topic on the forum also is about a same issue with Fabfilter plugins. On this topic I suggest that it could be license related. As Equalizer APO runs in the Windows audio service as every APO does (btw. an APO is just a sound effect/improvement) it has limited access to the computer folders and files (as it should). When a plugin checks its own license it may not find it thus starts running in demo mode (see "Access rights, permissions, ACL issues when running APOs" chapter of Etienne Dechamps APO explanation).
You won't believe what I found out. It turns out that this isn't related to fruity loops or asio at all. I have read a post that fabfilter plugins break after 30 days, after they are activated. It's like the trial timer code is still running, or there is a conflict with EQAPO. So I checked when I installed my system and it was exactly 30 days before. So this rabbit hole goes deeper and deeper ^^
Still there seems to be no solution to this. And also I tested a fabfilter plugin that I wasnt using yet, reverb. It wasn't activated, so I activated it and it is running normally
So this timer theory is true... ^^'