On Sat, 15 Nov 2003 14:30:17 +
Nick Lamb [EMAIL PROTECTED] wrote:
Here are my latest test results from running Demolition
http://www.ecs.soton.ac.uk/~njl98r/code/ladspa/demolition.html
237 plugins were tested from 117 plug-in libraries, including all the
ones in BLOP, CMT, SWH, MCP and
Paul Davis:
Since mainstream capabilities support seems always to be somewhere
over the horizon, I am interested in the patch Paul and Steve
mentioned. IIUC, it defines a control file in /proc which, if
enabled, allows any process access to scheduling and memory locking
privileges. No
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 discussion:
(1) There should a simple way for the sysadmin to reliably disallow
[ .. ]
(2) Using sysctl, set a
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 host allows the user to change the range hints.
Well, LOGARITHMIC was never
Attached is a patch to add OSS audio driver support to the
jack-audio-connection-kit 0.90.0. This is a first quick hack of 0.80.0
driver to 0.90.0, but better one is coming..
Apply patch and run autoreconf --force --install to regenerate
configure stuff.
RPMs for RedHat 9 and source .tar.gz is
Kjetil Svalastog Matheussen [EMAIL PROTECTED] writes:
(4) Let the user that is currently physical logged in to the machine
get realtime privileges.
Jack O'Quin writes:
It does seem difficult within the context of X11 to prove that a user
is actually local to the machine. Some people may
Jussi Laako [EMAIL PROTECTED] writes:
Does PortAudio support 24/32 bit formats and more than 2 channels or
samplerates over 48 kHz?
All my experience is with my home system, which runs ALSA drivers
using the OSS emulation interfaces. I suspect things would probably
work differently using one
Looks like I forgot to attach the patch...
i don't think this patch isn't ready to be added to CVS yet:
1) the null cycle callback is wrong. it will generate random noise, and
should instead generate silence.
2) the buffer size callback is wrong. you have to stop the hardware,
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 :).
$ vim +f +syntax on +so $VIMRUNTIME/syntax/2html.vim +wq +q *.c
cheers,
Jack O'Quin writes:
One of the things I like about the `audio' group approach is that
it is easy to administer and simple to verify who has access to
those privileges.
martin rumori [EMAIL PROTECTED] writes:
i think, that's a clean solution. to be able to distinguish between
Paul Davis:
Since mainstream capabilities support seems always to be somewhere
over the horizon, I am interested in the patch Paul and Steve
mentioned. IIUC, it defines a control file in /proc which, if
enabled, allows any process access to scheduling and memory locking
privileges. No
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 discussion:
(1) There should a simple way for the sysadmin to
12 matches
Mail list logo
