search

apohl79 / audiogridder

DSP servers using general purpose computers and networks
https://audiogridder.com
MIT License
767 stars 79 forks source link

"Failed" plugin loading #115

Closed goshawker2012 closed 4 years ago

goshawker2012 commented 4 years ago

Hi guys,

Things are working surprisingly well on my client side Windows 10 PC (Studio One 4.6 and 5) as well as server side MacBook Pro 2015. Running heavy AA plugins well. But for some reason on my Windows 10 laptop server the plugin list shows all modules but in red letters with a"failed" message. I can't seem to find any settings to address this.

Any clues as to where I should be looking to troubleshoot?

Thanks for the great work on this project.

apohl79 commented 4 years ago

You can check the logs for loading errors (https://github.com/apohl79/audiogridder#bug-report-diagnostics-locations). AG failed to load the plugins and marked them as failed.

In the plugin manager you can selectively mark failed plugins (right click on a plugin) for rescanning or you enforce a full rescan from the tray context menu.

goshawker2012 commented 4 years ago

Thanks for the assistance.

I tried a few times to remove them from the plugin manager and re-scan but with no success. So I decided to do a complete clean installation of Windows 10 and start over. Once that was done I installed all of my Acustica plugins but this time I included VST2 as well. All of the VST2's loaded perfectly well but again all VST3's failed. So I entered the VST3 folder location into the manager (just in case) and re-scanned but again they failed.

Here is a sample log for each format.

(VST3)

Log started: 15 Aug 2020 3:11:45pm [15:11:45.394|app|2105648052560] commandline: -scan "C:\Program Files\Common Files\VST3\PINK4PRE.vst3\Contents\x86_64-win\PINK4PRE.vst3|VST3" [15:11:45.395|app|2105648052560] scan mode: format=VST3 id=C:\Program Files\Common Files\VST3\PINK4PRE.vst3\Contents\x86_64-win\PINK4PRE.vst3 [server] scanning id=C:\Program Files\Common Files\VST3\PINK4PRE.vst3\Contents\x86_64-win\PINK4PRE.vst3 fmt=VST3 [15:11:45.568|app|2105648052560] ...failed [15:11:45.585|app|2105648052560] initialise complete [15:11:45.586|app|2105648052560] shutdown

(VST2)

Log started: 15 Aug 2020 3:12:42pm [15:12:42.298|app|2483690633472] commandline: -scan "C:\Program Files\Steinberg\VstPlugins\MAGENTA4COMPST.dll|VST" [15:12:42.299|app|2483690633472] scan mode: format=VST id=C:\Program Files\Steinberg\VstPlugins\MAGENTA4COMPST.dll [server] scanning id=C:\Program Files\Steinberg\VstPlugins\MAGENTA4COMPST.dll fmt=VST Attempting to load VST: C:\Program Files\Steinberg\VstPlugins\MAGENTA4COMPST.dll Creating VST instance: MAGENTA4COMPST Initialising VST: MAGENTA4COMPST (1.2.0.0) [15:12:45.588|app|2483690633472] ...success [15:12:45.590|app|2483690633472] initialise complete [15:12:45.591|app|2483690633472] shutdown

Any ideas?

apohl79 commented 4 years ago

Looks like some compatibility issues with the VST3 versions and JUCE, as the scan just fails. That seems to leave you with the VST2 versions, which should be ok for now I hope. Could be, that the latest JUCE framework, which the next AG release will be using, is working for you, but I don't know.

goshawker2012 commented 4 years ago

Hi Andreas,

Thanks for the follow up again.

The older Acqua versions in VST2 are indeed working well (Sand 2, Ultramarine 3, etc). Interestingly, newer Acqua plug-ins such as Pink 4, Ultramarine 4, Magenta 5 etc. don’t load either. So maybe it’s something to do with the new Core 16 roll out which I believe is still experimental. Maybe a clue?

Yet everything works perfectly well on my MacBook Pro server. I love what you guys are doing so wanted to share what I’m seeing on the Windows laptop in case it helps.

And of course I’ll test with the next AG release and report back if it’s helpful.

On Fri, Aug 21, 2020 at 6:29 PM Andreas Pohl notifications@github.com wrote:

Looks like some compatibility issues with the VST3 versions and JUCE, as the scan just fails. That seems to leave you with the VST2 versions, which should be ok for now I hope. Could be, that the latest JUCE framework, which the next AG release will be using, is working for you, but I don't know.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/apohl79/audiogridder/issues/115#issuecomment-678542114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQPXSUXKJ5F7OMAROBQBLGLSB3YN7ANCNFSM4P7MEESQ .