Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Melanie
On 2003.11.17 05:15 Jack O'Quin wrote: That's right. Separating the `realtime' from the `audio' seems logical to me. Not all audio is realtime, and not all realtime is necessarily audio. Video or other applications could also benefit from this mechanism. Maybe we should just invent a group

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Tim Hockin
On Mon, Nov 17, 2003 at 08:39:10AM +0100, Melanie wrote: userspace and runs as root. Errm, since when does PAM run as root?

Re: [linux-audio-dev] Demolition results, attention LADSPA developers

2003-11-17 Thread Mike Rawes
On Sun, 16 Nov 2003 18:21:08 + Steve Harris [EMAIL PROTECTED] wrote: On Sun, Nov 16, 2003 at 11:30:36 +, Mike Rawes wrote: ERROR: port 0 is LOGARITHMIC but LowerBound isn't positive Is this really an error? Dealing with the aymptote is trivial, and needs to be done anyway if a

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Melanie
On 2003.11.17 05:32 Tim Hockin wrote: On Mon, Nov 17, 2003 at 08:39:10AM +0100, Melanie wrote: userspace and runs as root. Errm, since when does PAM run as root? Hm, thought it did... during login... does it run as the user? Melanie

Re: [linux-audio-dev] Demolition results, attention LADSPA developers

2003-11-17 Thread Alfons Adriaensen
On Sat, Nov 15, 2003 at 02:30:17PM +, Nick Lamb wrote: Fons Adriaensen [EMAIL PROTECTED] mvclpf24.so cs_phaser.so (all plugins in each library) ERROR: Label contains illegal white-space character Indeed. Seems like I've been confusing the roles of 'name' and 'label', using the latter

[linux-audio-dev] Re: [Jackit-devel] Re: POSIX caps/realtime/root processes

2003-11-17 Thread Kjetil Svalastog Matheussen
On Mon, 16 Nov 2003, Fernando Pablo Lopez-Lezcano wrote: I couldn't wait til you found it, so I wrote one from scratch instead. :) The url below point to a hackish patch againt 2.4.23-rc1, and yes, it is very simple. Works by setting /proc/sys/kernel/setschedandmlock to 1.

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Martin Voelkel
On 2003.11.17 05:15 Jack O'Quin wrote: from this mechanism. Maybe we should just invent a group named `realtime'. totally agree. that's even better than an extra rtaudio group. Melanie writes: The mechanism you're looking for may be a PAM module. It has all the don't know too much

[linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Alfons Adriaensen
Hello LAD, I'd like to propose an extension of the LADSPA specs, or more correctly, a particular interpretation of the current specs, in order to support the use of plugins in a 'polyphonic' context. The problem to be solved is this: In a host such as AMS, a plugin can be loaded as part of a

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Steve Harris
On Mon, Nov 17, 2003 at 02:14:41 +0100, Alfons Adriaensen wrote: I'd like to propose an extension of the LADSPA specs, or more correctly, a particular interpretation of the current specs, in order to support the use of plugins in a 'polyphonic' context. FWIW, I dont think this is the correct

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Alfons Adriaensen
On Mon, Nov 17, 2003 at 03:01:40PM +, Steve Harris wrote: I'd like to propose an extension of the LADSPA specs, or more correctly, a particular interpretation of the current specs, in order to support the use of plugins in a 'polyphonic' context. FWIW, I dont think this is the

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Steve Harris
On Mon, Nov 17, 2003 at 04:26:23 +0100, Alfons Adriaensen wrote: This is exactly what AMS is doing in polyphonic mode. Most internal modules (PCM out is the obvious exception) are created as many times as there are voices, but still look like a single module to the user. Plugins can be created

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Alfons Adriaensen
On Mon, Nov 17, 2003 at 03:36:06PM +, Steve Harris wrote: On Mon, Nov 17, 2003 at 04:26:23 +0100, Alfons Adriaensen wrote: This is exactly what AMS is doing in polyphonic mode. Most internal modules (PCM out is the obvious exception) are created as many times as there are voices, but

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Steve Harris
On Mon, Nov 17, 2003 at 04:57:07PM +0100, Alfons Adriaensen wrote: The purpose of my proposition is to enable a plugin writer (if he/she wishes to do so) to detect when the plugin is used in this way, and maybe optimise his code. For example, control rate computations (which can be elaborate

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Jack O'Quin
Fernando Pablo Lopez-Lezcano [EMAIL PROTECTED] writes: As far as I understand these are the current options: a) capabilities b) simple sysctl patch to the kernel (like the one that Kjetil posted) c) security module, with possible additional control through sysctl b is better than a (more

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Alfons Adriaensen
On Mon, Nov 17, 2003 at 04:04:46PM +, Steve Harris wrote: I see, but I still dislike the idea FWIW :) Well if you want the functionality (and I do) I see no other way, except by doing something that would break the existing API. I have some plugins that are able to create their own GUI

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Steve Harris
On Mon, Nov 17, 2003 at 05:46:20PM +0100, Alfons Adriaensen wrote: It doesn't depend on the host's support in any way. The host doesn't even have to be an X client - the same library can be called by for example an internal JACK client. That sounds like incredibly useful software. Plugin

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Paul Davis
It doesn't depend on the host's support in any way. The host doesn't even have to be an X client - the same library can be called by for example an internal JACK client. The shared library creates a thread for the X code, connects to the X-server as a new client, and provides a set of widgets

Re: [linux-audio-dev] linux audio and ppc

2003-11-17 Thread Joern Nettingsmeier
Antonio Willy Malara wrote: On 2003.11.11 08:56, Joern Nettingsmeier wrote: powerbook g3 pismo. those are the white snow ibooks? no, the black old powerbooks with the translucent brownish keyboard. -- To someone whose only tool is a hammer, each problem looks like a nail. - Edsger W.

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Roger Larsson
On Monday 17 November 2003 06.17, Fernando Pablo Lopez-Lezcano wrote: On Sun, 2003-11-16 at 08:02, Paul Davis wrote: I've been thinking about ways to use this feature to improve and simplify the current security situation for Linux audio. No conclusions, but here are some thoughts for

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Fons Adriaensen
Hi Paul, have you considered the possibility that Xlib is not statically thread-safe? if there are any globals in the implementation of Xlib, this scheme will fail as soon as the host is using Xlib as well. Yes, and if X does its bookkeeping in terms of 'processes' and not 'clients' the same

[linux-audio-dev] re: JACK tutorial

2003-11-17 Thread james
On Mon, 17 Nov, 2003 at 04:12AM +, Paul Brossier spake thus: Thanks for this tut. Just one thought : the include statements in your code snipnets do not appear correctly because of the . You could pass them through vim to take care of the html characters (and add some color :). Gah!

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Paul Davis
All this would be a lot simpler if the common GUI toolkits would provide a call that would allow one to create a raw X window that wil be connected to their internals and that gets its raw X events delivered to a user specified callback. From there on, the toolkit or library used by the plugin

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Fernando Pablo Lopez-Lezcano
i'd be interested to hear from fernando about this kind of thing. many of us on LAD work on what are to all effects and purposes single user machines. i'd like to hear how policies like 1-4 above, or others, appear in the context of an academic shared resource environment.

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Paul Davis
All this would be a lot simpler if the common GUI toolkits would provide a call that would allow one to create a raw X window that wil be connected to their internals and that gets its raw X events delivered to a user specified callback. From there on, the toolkit or library used by the

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Taybin Rutkin
On Mon, 2003-11-17 at 17:33, Luke Yelavich wrote: At 11:52 PM 17/11/2003, Martin Voelkel wrote: Melanie writes: The mechanism you're looking for may be a PAM module. It has all the don't know too much about pam, but sounds to be a good solution. Not all distributions use pam, Slackware

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Jack O'Quin
Fernando Pablo Lopez-Lezcano [EMAIL PROTECTED] writes: - Can not provide mlockall since it has no pid parameter - the monitor can't do it for another process. (I would say that it is unlikely that pages used in a tight audio loop would be thrown out - big buffers might... Add additional

Re: [linux-audio-dev] LADSPA: proposition for polyphonic use of plugins

2003-11-17 Thread Tim Hockin
On Mon, Nov 17, 2003 at 07:48:53PM -0500, Paul Davis wrote: Well, we COULD discuss this with the QT/GTK folk. However, I personally i already am :) Excellent. Please keep us appraised :) QT and GTK would take care of the majority of Linux issues.

[linux-audio-dev] ladspa-1.2 diff

2003-11-17 Thread Taybin Rutkin
Can this get applied? We discussed it in September, and I thought it was going to be applied, but it never was. It includes defines for: LADSPA_HINT_MOMENTARY LADSPA_HINT_RANDOMISIBLE Taybin --- /usr/include/ladspa.h 2003-04-05 01:10:32.0 -0500 +++ ladspa-1.2.h 2003-09-08

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread martin rumori
Fernando Pablo Lopez-Lezcano writes: I would say (as in Kjetil's patch): echo 0/proc/sys/kernel/setschedandmlock -- normal behavior I suggest picking a clearer name, like /proc/sys/kernel/realtime. I agree, sounds better. It does not say what it does as the original ++votes

Re: [linux-audio-dev] Re: linux-audio-dev Digest, Vol 2, Issue 24

2003-11-17 Thread Jack O'Quin
martin rumori [EMAIL PROTECTED] writes: Also, 0 is a valid group ID, `root', which might be a reasonable choice if groups like `audio' and `realtime' are undefined. How about using -1, instead? Or, maybe `nogroup' (65534 on my system). Yes, probably nogroup is the best option. I