Hi LS devs!

I'm sure some of you already know me off the LAU/LAD lists as I've
been the main tester of MIDI in Ardour 3 and I've FINALLY got round to
concentrating on using LS under A3! Aren't you lucky? :D

I'm addressing the list as I'm hoping we can make some small
adjustments to the LS LV2 plugin and/or libgig and maybe LS itself
which will make it much easier (read: possible) to transfer Ardour 3
or qtractor sessions that use the LS LV2 plugin between machines/users
because at the moment the engine just gives a "sorry can't find the
instrument file" type of error if the instrument isn't located at
precisely the original path.

I don't know if the LV2 spec or any of its extensions cater for this
yet but if the instrument file isn't found in the original path then I
would like to see LS looking for the files in the same folder as the
A3 or qtractor session/project file, which is where I would like to
store them most of the time- certainly when collaborating on a
project. Paul tells me A3 wouldn't have any probs with such files
being stored within an A3 session directory. Ideally, if LS fails to
find an instrument in neither the original path nor in the same folder
as the current session/project file then it would display a dialogue
prompting you for the path to the missing file.

Big thanks to all the LS devs and contributors for bringing us such a
powerful sampler and the first really useful, poweful LV2 plugin!

Thanks for your help and a fantastic app!

Dan

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to