Re: [linux-audio-dev] Lock Free Ringbuffer in C ?

2003-04-05 Thread David Olofson
On Friday 04 April 2003 17.15, [EMAIL PROTECTED] wrote: [...] > res = sfifo_write(sf, &buf, j); > if(res != j) > { DOH! Sorry, I'm in a hurry and misread your code. Well, we're talking about a basic lock free FIFO here, based on atomic reads and writes of two indices. Proper bl

Re: [linux-audio-dev] Lock Free Ringbuffer in C ?

2003-04-05 Thread David Olofson
On Friday 04 April 2003 17.15, [EMAIL PROTECTED] wrote: > On Fri, Apr 04, 2003 at 12:47:28PM +0200, David Olofson wrote: > > On Thursday 03 April 2003 15.36, [EMAIL PROTECTED] wrote: > > > i remember i have read a statement about a lock free ringbuffer > > > implemented in C somewhere. > > > > > >

Re: [linux-audio-dev] LADSPA Taxonomy

2003-04-05 Thread Steve Harris
On Sat, Apr 05, 2003 at 10:44:01AM -0500, Dave Phillips wrote: > Steve, what about time compression/expansion, the harmonics generator, > and the all-important karaoke plugin ? Hmm... I hadn't though about time compression etc. as its not allowed in LADSPA. I suggest that a system that categorise

Re: [linux-audio-dev] lock-free ring buffer code

2003-04-05 Thread Steve Harris
On Sat, Apr 05, 2003 at 06:15:09 +0200, Ingo Oeser wrote: > Now make that thread-safe and esp. thread-safe on an architecture > with weak memory ordering and all the fun stuff. Sure, it will only work on architectures where 32bit reads and writes are atomic. > If you have that all working and lo

Re: [linux-audio-dev] lock-free ring buffer code

2003-04-05 Thread Ingo Oeser
Hi, On Sat, Apr 05, 2003 at 01:08:30PM +0100, Steve Harris wrote: > There are many cases in audio software when you are only concerned with > reading single values at a time from the fifo and relative delays, then > its much simpler [from memory, syntax might be wrong]: > > unsigned int siz

[linux-audio-dev] session management and LADCCA ?

2003-04-05 Thread Dave Phillips
Greetings: While helping out a client with his PlanetCCRMA installation I've realized the intense need for session management software. I'll start working with LADCCA, but I wondered if anyone else has been using it and if they have any particularly useful experience to share yet. I realize LADC

Re: [linux-audio-dev] LADSPA Taxonomy

2003-04-05 Thread Dave Phillips
Steve Harris wrote: > I recon that something like this is a good start, but feedback would really help: > > Utilities > > Generators > Oscillators > > Delays > Phasers + Allpass > Flangers > Chorus > > Reverbs > > Filters > Lowpass > Highpass > Bandpass > Combs

[linux-audio-dev] [OT] LJ Karlsruhe report update

2003-04-05 Thread Dave Phillips
Greetings: At this time the /. effect is in full swing. The main page now reports more than 10,000 reads, far more than any other article currently listed. I feel that this is because it's really the time to notice Linux audio. Linux audio development has 'way outstripped my expectations, thanks

[linux-audio-dev] Demolition pre-release (LADSPA testing)

2003-04-05 Thread Nick Lamb
Demolition, my destruction testing tool for LADSPA plugins is now available as a pre-release version. This is fully functional, but I want to get some feedback from "users" (ie other LADSPA developers) before I call it version 1.0 http://www.ecs.soton.ac.uk/~njl98r/code/ladspa/ (Don't be distrac

[linux-audio-dev] Re: [linux-audio-user] LADSPA Taxonomy

2003-04-05 Thread Jan \"Evil Twin\" Depner
Looks good to me. On Sat, 2003-04-05 at 08:44, Steve Harris wrote: > Hi all, > > After the LAD Conference and using apps which used the lrdf taxoomy > (putting plugins into categories) code it became obvious the the current > taxonomy wasn't really useful. > > the current taxnomy looks like: >

[linux-audio-dev] LADSPA Taxonomy

2003-04-05 Thread Steve Harris
Hi all, After the LAD Conference and using apps which used the lrdf taxoomy (putting plugins into categories) code it became obvious the the current taxonomy wasn't really useful. the current taxnomy looks like: Utilities Generators Oscillators Simulators Reverbs Time Delays Phas

Re: [linux-audio-dev] Lock Free Ringbuffer in C ?

2003-04-05 Thread Ingo Oeser
On Fri, Apr 04, 2003 at 07:43:40AM -0500, Paul Davis wrote: > there are several solutions, none of them particularly good. the best > is to wait on a FIFO. these provide a fast, 99% non-blocking way to > get 1 process to wake up another. the "real" solution needs to be > provided by the kernel, and

Re: [linux-audio-dev] lock-free ring buffer code

2003-04-05 Thread Steve Harris
There are many cases in audio software when you are only concerned with reading single values at a time from the fifo and relative delays, then its much simpler [from memory, syntax might be wrong]: unsigned int size = some_power_of_two unsigned int write_ptr = 0 float buff

Re: [linux-audio-dev] lock-free ring buffer code

2003-04-05 Thread Ingo Oeser
On Fri, Apr 04, 2003 at 08:00:36PM +0100, Bob Ham wrote: > On Thu, 2003-04-03 at 21:14, rm wrote: > > > below is what i use (i think it works). the primary thing to notice > > is that readers and writers are kept in line by the atomicity of > > integer assignment (though in general, we should prob