Sorry, but IMO...
::Climbs on a soapbox::
VST paths are a never ending nightmare imo. They vary from system to
system, and there is no "good" standard for VST isolation. As it stands
there are over a half a dozen standard paths for the base VST foder.
"Program Files/Vst", "Program Files/Plugins", "Program
Files/Steinberg/Vst", "Program Files/Steinberg/VstPlugins", "Program
Files/Common Files/VST", "Program Files/Common Files/Steinberg/VST" etc.
Then you have 32bit and 64 bit VST isolation so have all the previous
variations with "Program Files(x86)/" and then you have the three
variations of VSTs so end up with several of the previous paths with the
variations "VST2" and "VST3" mixed in. Put the wrong VST in the wrong
folder and you can have endless random DAW crashes. The best solution is
honestly make a dummy place holder that loads when a given VST isn't found
or when a VST stops responding so that the VST data isn't lost, then allow
the user to replace the dummy with the correct VST on their system. that
being said LMMS only has a single VST path, and while that is great if it
were the only DAW a person ever needed, but the fact is due to the need to
manually isolate VSTs for other DAWs, multiple VST paths are going to exist
on virtually any serious persons system. The fact LMMS can only specify one
base VST path is severely limiting in this area.
::climbs off soapbox, and hands out tomatoes for people to throw at him::
On Mon, Feb 24, 2014 at 2:19 PM, Tres Finocchiaro <
tres.finocchi...@gmail.com> wrote:
> I've been burned so many times by 64 bit hosts not being able to load 32bit
>
>
> I own a copy of jBridge for PC and I'm happy to say that I don't need it
> with LMMS.
>
> I've been using 64-bit Windows LMMS since the day Toby released it to the
> wild. Although some builds have had 32-64-bit issues, I can say that for a
> while now both 32-bit and 64-bit VSTs load great (I believe Mike Choi
> helped with this last time), and in addition to this, Toby fixing the
> "working path" has made VSTs even that more reliable.
>
> The only standing complaint I have is the lack of relative paths for
> loading VSTs, but that is relatively minor at this point (I would guess
> this is due to the fact that VST effects and VST plugins are treated with
> the same default path, i.e. %PROGRAMFILES%\VstPlugins).
>
> Here's an archive of the last conversation about vst paths:
>
> http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Re-Lmms-users-VST-bug-td3606.html
>
> -Tres
>
> - tres.finocchi...@gmail.com
>
>
>
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
