Re: [linux-audio-dev] recording, sample rate problem

2003-03-18 Thread Turos László Zsolt
Nick Bailey wrote: Turos Laszlo wrote: Hi I'm trying to write a soundrecorder application under linux. I have Redhat 7.2 with kernel 2.4. Playing sound on my soundcard works fine,but I'm having problems recording. I was using GNOME Sound recorder 1.2.3 to record sound but it seems

[linux-audio-dev] RE:linux-audio-dev digest, Vol 1 #400 - 12 msgs

2003-03-18 Thread RichardC
Hello [EMAIL PROTECTED] I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #400 - 12 msgs' I will be out of the office until the 24th of March. Please refer any queries that require immediate attention to Phil Carroll @ [EMAIL PROTECTED] Regards Richard Caldwell

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread Immanuel Litzroth
rm == rm [EMAIL PROTECTED] writes: rm hi all, so i've tried to make a new scheduling policy for rm linux. i've called it SCHED_USERFIFO. the intent is rm basically to allow a process ask for x amount of processor rm time out of every y jiffies. (the user part is in the hope

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread Josh Green
On Mon, 2003-03-17 at 23:45, rm wrote: hi all, so i've tried to make a new scheduling policy for linux. i've called it SCHED_USERFIFO. the intent is basically to allow a process ask for x amount of processor time out of every y jiffies. (the user part is in the hope that the

[linux-audio-dev] Re: [jmax] Running a patch as a LADSPA plugin

2003-03-18 Thread Francois Dechelle
On Tue, 2003-03-18 at 10:36, Steve Harris wrote: Thats OK as a quick fix, but it doesn't solve the broader problem, if you save state from a host using jMax LADSPA plugins then it wont necceserily be the same set when you reload. I think LADSPA needs self assigned ID's, if the UID space

Re: [linux-audio-dev] Re: [jmax] Running a patch as a LADSPA plugin

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 12:04:46 +0100, Francois Dechelle wrote: A better solution would be to expand the ID space to 64bits, and reserve the top bit's worth, which is plenty, but will break binary compatibility of course. In any case, hosts that save the ID cannot restore the plugin

[linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Lukas Degener
Roman Kaljakin wrote: I am pleased to announce Octavian - a realtime software synthesizer for GNU\Linux operating system. Octavians's design is like analog modular synthesizers,(...) Well, here we have another modular synth framework. :-) Hi Roman, i realy like parts of your ui design. just

Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Ranjit Singh
I am a broadcast engineer by profession, but a hacker by hobby. I maintain the PostgreSQL RPMset, the nspostgres AOLserver database driver, and do a little bit of coding. I wouldn't consider myself fluent in C++, however. But I enjoy learning new things Well, that sounds perfect to

Re: [linux-audio-dev] Re: [jmax] Running a patch as a LADSPA plugin

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 01:31:28 +0100, Francois Dechelle wrote: On Tue, 2003-03-18 at 12:46, Steve Harris wrote: Yes, but the ID number would be created from a hash of the unqiue identifier (eg. a URI), so it would be consistant between sessions. What would be this unique identifier in

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Thomas Webb
The Big Question(tm): How can we avoid redundant work? My (somewhat utopious) suggestion: maybe we should think in components that use/modify a common datastructure/model. I like the sound of that. There shouldn't be any code that we share. Because we all have different styles, goals,

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Paul Davis
I think the bulk of redundant work is on standard effects or modules. We don't want to define anything as to how the modules work with each other, but maybe draft some sort of a file that compliant programs either a) convert to code and integrate into the app at compile-time or b) can open as

[linux-audio-dev] RE:linux-audio-dev digest, Vol 1 #401 - 11 msgs

2003-03-18 Thread RichardC
Hello [EMAIL PROTECTED] I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #401 - 11 msgs' I will be out of the office until the 24th of March. Please refer any queries that require immediate attention to Phil Carroll @ [EMAIL PROTECTED] Regards Richard Caldwell

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread Paul Davis
Anyway, I think this patch has its place on linux-kernel. It will most likely be rejected but it shows that people are interested in these issues... (Who knows Ingo might get another bright idea... :-) i agree, but i also raise another angle that i spoke about a couple of times at zkm this last

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread ico
How about having all apps implement Open Sound Control (some of them already have, such as pd, csound etc.)? Then you could control them all from one source (i.e. RTMix). Then, suddenly there would be no redundancy ;-)... Ico From: Lukas Degener [EMAIL PROTECTED] Date: 2003/03/18 Tue AM

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Brad Arant
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ranjit Singh Sent: Tuesday, March 18, 2003 6:12 AM To: [EMAIL PROTECTED] Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux .. I think we could both learn some new things :) As we all

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread rm
On Tue, Mar 18, 2003 at 06:07:24PM +0100, Roger Larsson wrote: On Tuesday 18 March 2003 08:45, rm wrote: hi all, With 2.4 kernels there are very few jiffies to share, 2.5 kernels have more. But jiffies are not a good unit... that would depend on the period you set, but point taken. The

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Thomas Webb
How about having all apps implement Open Sound Control (some of them already have, such as pd, csound etc.)? Then you could control them all from one source (i.e. RTMix). Then, suddenly there would be no redundancy ;-)... I'm new to LADSPA, but isn't that what LADSPA control protocol

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Thomas Webb
I was very impressed by the XML representation of LADSPA plugins presented by Steve Harris at the LAD conference last weekend. He writes the code and parameter specifications of his LADSPA plugins in XML and then converts (compiles) them to the C code according to ladspa.h. Here's an

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread Dr. Matthias Nagorni
On Tue, 18 Mar 2003, Thomas Webb wrote: I also already devised an xml-based format for modular synth patches. It needs some work if it's to be an I was very impressed by the XML representation of LADSPA plugins presented by Steve Harris at the LAD conference last weekend. He writes the code

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread Lukas Degener
LADSPA: its not great for instruments, but IMHO works at precisely the correct level for synth modules. Agreed. Well, ok there are some issues, but no real problems. Actualy i would like arbitrary datatypes. And it would sure be nice to have more information on the semantics of the ports. The

[linux-audio-dev] RE:linux-audio-dev digest, Vol 1 #402 - 13 msgs

2003-03-18 Thread RichardC
Hello [EMAIL PROTECTED] I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #402 - 13 msgs' I will be out of the office until the 24th of March. Please refer any queries that require immediate attention to Phil Carroll @ [EMAIL PROTECTED] Regards Richard Caldwell

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Paul Davis
problem of the hosts not completly implementing everything that is supported by ladspa (until recently, i didn't know about this rdf thingy, for instance.) that isn't actually part of LADSPA. its an example of the extreme ease of adding wrappers and new layers to LADSPA precisely because it

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread Lukas Degener
I'm new to LADSPA, but isn't that what LADSPA control protocol does? Dunno. have to do some reading. What is Open Sound Control? Say I wanted to make a snazzy analogue modelled filter. Someone else wanted to integrate it into their modular. They could do that and make it just another module

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Ranjit Singh
I have downloaded the C++ sample code from the echo site. Has anybody developed it beyond that point? I will go ahead and set up a web site for the management of the development. Are there any suggestions as to the tools we will need to collaborate? Well, base would be CVS and bugzilla. A

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread Simon Jenkins
Thomas Webb wrote: I was very impressed by the XML representation of LADSPA plugins presented by Steve Harris at the LAD conference last weekend. He writes the code and parameter specifications of his LADSPA plugins in XML and then converts (compiles) them to the C code according to ladspa.h.

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread jfm3
i've said many times before: i don't believe that the desktop is something that developers of music apps should concern themselves with. [...] i think we should focus on writing good applications that are independent of what a desktop does. Yes. It is more useful to think of real time CHI

Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Paul Davis
I have downloaded the C++ sample code from the echo site. Has anybody developed it beyond that point? I will go ahead and set up a web site for the management of the development. Are there any suggestions as to the tools we will need to collaborate? Well, base would be CVS and bugzilla.

Re: [linux-audio-dev] Modular synths of the world, unite and takeover :-)

2003-03-18 Thread Lukas Degener
that isn't actually part of LADSPA. Ah ok, i mixed that up. sorry. there actually isn't really any commonality between what, say, pd versus beast do. or between jMax and gAlan. the similarity exists only on an abstract conceptual plane, which is where algorithms live. however software isn't

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 10:27:42 -0800, Thomas Webb wrote: Here's an idea: find a way to conver these same XML files into dsp assembler. All the sudden, the same stuff you use to make a softsynth can be reused for a hardware synth! You cant generate normal DSP code from C as it tends to be

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Thomas Webb
The tricky bit would be making the generated C code agnostic enough with regard to issues like: ~floating vs fixed point arithmetic ~block processing vs blockless ~control value representation and rate ~code calling conventions ~the nature of connections between modules Even ignoring

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 02:38:49 -0500, Paul Davis wrote: problem of the hosts not completly implementing everything that is supported by ladspa (until recently, i didn't know about this rdf thingy, for instance.) that isn't actually part of LADSPA. its an example of the extreme ease of

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 10:25:47 -0800, Thomas Webb wrote: I'm new to LADSPA, but isn't that what LADSPA control protocol does? I think it would be better if there was something like that, but the plugin can work with or without the gui. LCP is mostly hypothetical. There are some sample UIs

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Thomas Webb
You cant generate normal DSP code from C as it tends to be fixedpoint, and C doesn't support it. - Steve Yeah, fixed point DSPs are cheaper, no? I wasn't suggesting using a C compiler to generate assembler. I was thinking more along the lines of making a new compiler/converter kinda thingy

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Steve Harris
On Tue, Mar 18, 2003 at 08:35:30 +0100, Lukas Degener wrote: I'm new to LADSPA, but isn't that what LADSPA control protocol does? Dunno. have to do some reading. What is Open Sound Control? Its a synthesis focused message passing protocol. Generally run over UDP. Pretty popular in the

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Brad Arant
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Davis Sent: Tuesday, March 18, 2003 12:24 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux with all due respect, you are talking about

[ot] Re: [linux-audio-dev] RE:linux-audio-dev digest, Vol 1 #402 - 13 msgs

2003-03-18 Thread Frank Barknecht
Hallo, [EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote: I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #402 - 13 msgs' I will be out of the office until the 24th of March. Okay, I'm fed up, this guy went into my spam blacklist. Sorry for interrupting. Please

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Paul Davis
Hey, the broken-record technique works ;) it sure does. what would you like me to repeat next ? probably at least a half-dozen companies doing this today - should they all sit down and work out how to make their stuff interoperable beyond a 12V/octave standard? Er, actually several of the

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread rm
ok, new patch. with sysctl for /proc/sys/kernel/rtsched_{period,reserved}. a single limit for all rt fifo processes. same caveats as last time. rob --- pristine/linux-2.4.20/kernel/sched.c2003-03-17 23:24:02.0 -0500 +++ linux/kernel/sched.c

[linux-audio-dev] ecasound 2.2.2 released

2003-03-18 Thread Kai Vehmanen
1. A short summary of changes A new native Python implementation of the ECI API has been added to the package. Ecasound.el (ecasound-emacs) has been updated to version 0.8.2. Oggs and mp3s can be now streamed directly from network. Author information is now visible in the LADSPA plugin

Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Ranjit Singh
with all due respect, you are talking about somewhere between 1-5000 lines of code that would take someone experienced about 3 days to get to 60% functionality. once it reaches that point, ALSA will happily take it on, and you get CVS and the ALSA mailing lists to use. Fair enough, I

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread Brad Arant
Im on it! I will throw the questions out to the board and regular progress - hopefully I can get through this pretty quick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Olofson Sent: Tuesday, March 18, 2003 3:07 PM To: [EMAIL PROTECTED] Subject: Re:

Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

2003-03-18 Thread David Olofson
On Wednesday 19 March 2003 00.49, Ranjit Singh wrote: [...] We're effectively talking about a driver for the Motorola DSP onboard (I can't remember what the no is.) No, that stuff is secret. The microcode is available only as raw binaries, and the driver's job is to talk to the microcode; not

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Martin Voelkel
Steve Harris writes: On Tue, Mar 18, 2003 at 08:35:30 +0100, Lukas Degener wrote: Dunno. have to do some reading. What is Open Sound Control? Its a synthesis focused message passing protocol. Generally run over UDP. Pretty popular in the academic world. It could/should be a canditate for

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Roman Kaljakin
On Tue, 18 Mar 2003 19:20:29 +0100 (CET) Dr. Matthias Nagorni [EMAIL PROTECTED] wrote: On Tue, 18 Mar 2003, Thomas Webb wrote: I also already devised an xml-based format for modular synth patches. It needs some work if it's to be an I was very impressed by the XML representation of

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

2003-03-18 Thread Roman Kaljakin
On Tue, 18 Mar 2003 21:37:00 +0100 Lukas Degener [EMAIL PROTECTED] wrote: that isn't actually part of LADSPA. Ah ok, i mixed that up. sorry. there actually isn't really any commonality between what, say, pd versus beast do. or between jMax and gAlan. the similarity exists only on an

Re: [linux-audio-dev] new realtime scheduling policy

2003-03-18 Thread rm
On Tue, Mar 18, 2003 at 12:23:55PM -0500, Paul Davis wrote: i agree, but i also raise another angle that i spoke about a couple of times at zkm this last weekend. using SCHED_(USER)?FIFO makes no sense if you do not also call mlockall(2). (for us...i can think of cases where this isn't