I have seen this used with Libreoffice which is a massive project and it
works for them, the sad thing is I don't have the time to look into this or
have the coding know how L
From: John Serafino [mailto:lzrbl...@gmail.com]
Sent: Wednesday, February 13, 2013 7:24 AM
To: Jonathan Aquilina; lmms
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 sugges
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.source
I am no expert here, but paths in windows are handled differently then on
linux. I think the best way would to be an os check and if the os is windows
link the way windows recognizes them otherwise if its linux or mac link them
the way they are supposed to be if that makes any sense.
-Original
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 wrote:
> I'll chime in with a different viewpoint. I do alot of m
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
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
Okay, I will check for older versions, I am not sure if its a good idea to
mix VST effects and VSTi inside one common folder, but maybe it should be
not problem if you open VSTi from sub-floders.
-Mike
On Wed, Feb 13, 2013 at 12:19 AM, John Serafino wrote:
> Hooray! We need this in order to be
Hooray! We need this in order to be able to share projects properly for
collaboration and such.
On Tue, Feb 12, 2013 at 5:17 PM, 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 it
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?
I pushed test commit
10 matches
Mail list logo
