I just realized that it would actually work. I didn't understand that the
project file would point to the links in the VST directory, which could
link to the actual VST's wherever the current user was storing them. I
don't love the lack of elegance, but it would be effective nonetheless.
My suggestion? Relative paths with multiple base points(or whatever I
should be calling the root of a relative path.) This would require more
work, yes, but it would give us a solution that is easy for the users-all
they have to do is point LMMS to their VST directories-and would be
slightly more elegant, but very easy to debug and work with.
On Wed, Feb 13, 2013 at 12:13 AM, Jonathan Aquilina
<eagles051...@gmail.com>wrote:
> John not necessarily true imho. In another email I put in my 2 cents about
> this. Wouldn’t an OS check be sufficient to determine how things get linked
> together?****
>
> ** **
>
> *From:* John Serafino [mailto:lzrbl...@gmail.com]
> *Sent:* Wednesday, February 13, 2013 3:50 AM
> *To:* Dave Peterson; lmms-devel@lists.sourceforge.net
>
> *Subject:* Re: [LMMS-devel] [Lmms-users] VST bug?****
>
> ** **
>
> Actually, symlinks take up *very* little space. The biggest problem with
> that, IMO, is that it sticks us with another system that is not friendly to
> project portability and sharing.****
>
> ** **
>
> On Tue, Feb 12, 2013 at 8:19 PM, Dave Peterson <da...@kimanddave.com>
> wrote:****
>
> I'll chime in with a different viewpoint. I do alot of my composition
> while traveling so use a netbook with limited disk space. I'd much
> prefer not to be forced to install my VSTs in multiple places on my
> machine if that could be helped. Why not simply make a config option
> for locating the root VST plugin folder and default it to something
> within the LMMS install? That way people like me can point it as a
> common install location if we want to and we can still use relative
> paths when saving in a project?
>
> -- Dave****
>
>
> On 2013.02.13 10:28, oeai wrote:
> > On 13.02.2013 03:17, Mike Choi wrote:
> >> Hi,
> >> I think it would be good to agree on a general way how those relative
> >> paths should be handled (If this is not done already). I would say its
> >> not good idea e.g. to search for VST plugins in more common folders,
> >> to avoid version conflicts, but maybe someone has better idea?
> >>
> >>
> > Maybe you can create a vst folder inside main app directory, so all
> > needed dll's of common folders will be symlinked to that folder and all
> > unusual copies can be found by users in search trees and after user pick
> > will be added as symlinks into that folder too?
> >****
>
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmms-devel****
>
>
>
> ****
>
> ** **
>
> --
> Johnny ****
>
--
Johnny
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
