25 Jun
2009
25 Jun
'09
6:13 p.m.
Windows (i.e.
"%ProgramFiles%\LADSPA Plugins\rdf"). ?Not that I
generally build with LRDF support on Windows anyway.
This makes sense to me, if only it could be made "official"...
(windows paths too) 
25 Jun
25 Jun
6:24 p.m.
New subject: RFC: Default discovery paths for LADSPA, LRDF, LV2 and DSSI (and more?)
On Thu, Jun 25, 2009 at 9:13 PM, Jeff McClintock<jef(a)synthedit.com> wrote:
Windows has official rules for this. Users are no
longer allowed to add
random files to an application's directory in "/Program Files/Appname".
Oh! This is news to me -- interesting news too, given that I
distribute Windows versions of SV without an installer and just expect
the user to copy it to %ProgramFiles% if they want it to go there, and
that it only looks in immediate subdirectories of %ProgramFiles% for
plugins of any sort.
I don't recall anyone complaining to me that they couldn't install
plugins for it -- maybe this just means nobody is using it?!
Can you point to any documentation for this? I'd like to know what
other rules I might be falling afoul of.
User installed plugins go in
CSIDL_PROGRAM_FILES_COMMON , e.g. typically
"C:\Program Files\Common Files\LADSPA Plugins..."
I don't suppose you happen to know whether any Windows-based LADSPA
hosts are actually using this path?
Chris
6:39 p.m.
New subject: RFC: Default discovery paths for LADSPA, LRDF, LV2 and DSSI (and more?)
Chris Cannam wrote:
On Thu, Jun 25, 2009 at 9:13 PM, Jeff
McClintock<jef(a)synthedit.com> wrote:
I'm going to delete my Windows installation, but if I can help by
keeping it and you ask me explicit to test some behaviour I will do it.
--
Secret of Tux:
http://images.wallaceandgromit.com/user_uploads/forum_thumbnails/5/75/355.j…
"Gromit bit me" says HMV dog:
http://img.dailymail.co.uk/i/pix/2007/03_03/GomitHMVPA_468x319.jpg
Windows has official rules for this. Users are
no longer allowed to add
random files to an application's directory in "/Program Files/Appname".
Oh! This is news to me -- interesting news too, given that I
distribute Windows versions of SV without an installer and just expect
the user to copy it to %ProgramFiles% if they want it to go there, and
that it only looks in immediate subdirectories of %ProgramFiles% for
plugins of any sort.
I don't recall anyone complaining to me that they couldn't install
plugins for it -- maybe this just means nobody is using it?!
Can you point to any documentation for this? I'd like to know what
other rules I might be falling afoul of.
User installed plugins go in
CSIDL_PROGRAM_FILES_COMMON , e.g. typically
"C:\Program Files\Common Files\LADSPA Plugins..."
I don't suppose you happen to know whether any Windows-based LADSPA
hosts are actually using this path?
Chris 
7:02 p.m.
New subject: RFC: Default discovery paths for LADSPA, LRDF, LV2 and DSSI (and more?)
Ralf Mardorf wrote:
Chris Cannam wrote:
Pardon, I need some time to understand that it was ironic, I will be
quiet now ;) ... sorry.
On Thu, Jun 25, 2009 at 9:13 PM, Jeff
McClintock<jef(a)synthedit.com>
wrote:
I'm going to delete my Windows installation, but if I can help by
keeping it and you ask me explicit to test some behaviour I will do it. Windows has official rules for this. Users are
no longer allowed to
add
random files to an application's directory in "/Program Files/Appname".
Oh! This is news to me -- interesting news too, given that I
distribute Windows versions of SV without an installer and just expect
the user to copy it to %ProgramFiles% if they want it to go there, and
that it only looks in immediate subdirectories of %ProgramFiles% for
plugins of any sort.
I don't recall anyone complaining to me that they couldn't install
plugins for it -- maybe this just means nobody is using it?!
Can you point to any documentation for this? I'd like to know what
other rules I might be falling afoul of.
User installed plugins go in
CSIDL_PROGRAM_FILES_COMMON , e.g.
typically
"C:\Program Files\Common Files\LADSPA Plugins..."
I don't suppose you happen to know whether any Windows-based LADSPA
hosts are actually using this path?
Chris
6:34 p.m.
New subject: RFC: Default discovery paths for LADSPA, LRDF, LV2 and DSSI (and more?)
Jeff McClintock wrote:
Windows has official rules for this. Users are no longer allowed to add
random files to an application's directory in "/Program Files/Appname".
Permissions are set to prevent it and that directory is virtualized to
prevent it.
The exception is - Applications can install their own bundled plugins in
"/Program Files/Appname" at install time only (because the installer has
elevated privilege).
User installed plugins go in CSIDL_PROGRAM_FILES_COMMON , e.g. typically
"C:\Program Files\Common Files\LADSPA Plugins..."
Best Regards,
Jeff McClintock
I need to take a look at my Windows installation, that I will delete,
because Linux now is fine on my machine, but as far as I remember VSTs
are in \Blabla\Steinberg\VST or similar to this and a user can rename
and add what ever he likes to this path AND Cakewalk or what ever, will
take a look too, to this directory. It might be different for LADSPAs on
Windows, but there seems to be still an advantage the way VSTs are used.
Windows (i.e. "%ProgramFiles%\LADSPA
Plugins\rdf"). ?Not that I
generally build with LRDF support on Windows anyway.
This makes sense to me, if only it could be made "official"...
(windows paths too)
5418
days inactive
5418
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Chris Cannam -
Jeff McClintock -
Ralf Mardorf