Does that mean that you have to put all the dlls in the same folder?
Can't we just have a piece of code that seaches the needed dll in a list
of folders edited by users in a text file?
Il 20/10/2014 15:19, Tres Finocchiaro ha scritto:
If you use the paths properly, this issue has been mostly fixed in 1.1
with this patch:
https://github.com/LMMS/lmms/issues/383
This patch allows the VSTs on Windows to be loaded via a relative
path, which was broken since the beginning of time.
The reason for this was Window's use of the backslash versus the
forward slash.
It doesn't directly address your request (about fixing the paths on
launch), but it certainly helps for sharing mmpz files.
-Tres
- tres.finocchi...@gmail.com <mailto:tres.finocchi...@gmail.com>
On Mon, Oct 20, 2014 at 9:09 AM, DeRobyJ <dero...@gmail.com
<mailto:dero...@gmail.com>> wrote:
One of the best features of LMMS is how easy is to share a project.
When you open someone else's project, all the internal plugins are
perfectly loaded, also Zyn tracks are loaded, and when there are wave
sounds and such it's easy to add them again, if you have that sound in
another folder.
This all works fine but for VSTs: when you load a project with a VST,
VeSTige will fail in loading the dll, since it won't be in the folder
where it should. For example if you open this project:
http://lmms.io/lsp/?action=show&file=5399
it won't load Synth1.
There are two ways of fixing this problem right now:
- Changing the location of your VST, or creating another copy of it
- Editing the project file with a text editor
The first is no good, since you don't want neither to move your VSTs
(and in Synth1 case, to reset its settings) or to copy it (it'll take
some space on your HD!).
The second is ok, but it only works for .mmp files! Zipped projects
don't let you edit them.
If you open the project with LMMS and then load the VST, it will lose
the preset it was set to by the author.
How to fix this?
I see two different ways:
- When you open a project, you can tell the program the location of
missing VSTs, if you have them
- When you use a new VST, the program detects it and asks you give a
"name" for it. When a project is loaded, you can tell the program that
the VST seached at the missing location is that VST with the name you
had given.
First is a bit easier to implement, but the user have to search
his own
VST through folders. The other one is cool imo, because you won't have
to search the VST again and again every time you use it.
~DeRobyJ
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push
notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
<mailto:LMMS-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/lmms-devel
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
