Re: [linux-audio-dev] Re: desktop audio resumed
Hi, The Project Utopia people seem to have another approach to fix some issues of sound-card configuration, but I'm not quite sure wheter I like this or not ;) http://mail.gnome.org/archives/utopia-list/2005-July/msg1.html -Richard
Re: [linux-audio-dev] LADSPA plugin IDs needed
Steve: Thanks for the info. But maybe if Richard is that busy (which is something I understand of course) would it be more convenient if several trustworthy people involved in LADSPA would take care of a common available IDs range stored in a file on some FTP site accessible only by them? Tim: Oh my, I have no words! Thanks so much. I will be developing more plugins this week, and maybe in a few days I will release them. They are nothing complicated in design since I've just started learning DSP, but they're interesting anyway and I haven't seen anything like this in the available range of the LADSPA plugins. Thanks again guys! Artemiy.
Re: [linux-audio-dev] best soundcard revisited
Aaron wrote: I plan to have all the computers dual booting lin/win and want the best quality sound card I can get that will run on both lin and win with the least trouble and the most bang for the buck. I don't need multitrack recording necessicarily. And what _do_ you need? Neither best quality nor bang are very specific. ;-) Stereo playback? 5.1 playback? Stereo recording? Mic and/or Line input? SPDIF input and/or output? 16 or 24 bits? 48 or 96 kHz? MIDI? .. Regards, Clemens
[linux-audio-dev] best LL kernel options with ingo molnar's patch
hello, any advice on what would be the best kernel options when using ingo molnar's patch for an audio setup? CONFIG_PREEMPT_DESKTOP: Preemptible Kernel (Low-Latency Desktop) or CONFIG_PREEMPT_RT: Complete Preemption (Real-Time) CONFIG_PREEMPT_SOFTIRQS: Thread Softirqs CONFIG_PREEMPT_HARDIRQS: Thread Hardirqs yes or no? right now i am building with CONFIG_PREEMPT_DESKTOP, CONFIG_PREEMPT_SOFTIRQS and CONFIG_PREEMPT_HARDIRQS maarten
Re: [linux-audio-dev] linking multiple .o plugins into a single .so library
On Thu, 2005-06-30 at 19:32 +0200, fons adriaensen wrote:
On Thu, Jun 30, 2005 at 07:59:51PM +0300, Artemio wrote:
As I understand I cannot change the names of _init and _fini because
these are standard for libraries (or not?) and names of
g_psStereoDescriptor and g_psMonoDescriptor are standard for a LADSPA
plgin (or not?)... But what should I do? Or is is better to keep the
plugins in separate .so files?
Just combine the two _init() functions into one, and the same
for _fini(). Or change their names and add _init() and _fini()
that call both. Or use static declarations of all the required
LADSPA structs and then you don't need _init() and _fini() at all.
and if you want to be really portable, don't use _init() or _fini(),
which are officially deprecated by gcc/glibc/ld.so, and use
void
myinitfunction() __attributes__((constructor))
{
}
void
myfinifunction() __attributes__((destructor))
{
}
i may have the syntax slightly wrong for that; the gcc info page will
reveal all. this will allow your plugins to be built on OS X, where they
have gone beyond deprecating support for _init()/_fini() and actually
removed it.
note that with this design, you can have multiple initialization and
finalization functions, which is why the _init()/fini() design was
deprecated in the first place.
--p
Re: [linux-audio-dev] best soundcard revisited
Ok youre right, Here is what I am using it for: 1. taking hundreds of hours of analog recordings of single people singing and recording them to harddisk then editing them and restoring them. The recordings are both mono and stereo. 2. Do the same thing with digital recordings from minidisk or mp3 recorders. 3. possibly creating demo mixes. In summation for the current project at most stereo recording and if it makes a quality difference 2496, if not cd quality. mic and line in spdif in and out why not? The main issue I was asking about was the best sound card as far as linux support. Multitrack is not needed. Thanks Aaron On Tue, Jul 05, 2005 at 11:56:14AM +0200 or thereabouts, Clemens Ladisch wrote: Aaron wrote: I plan to have all the computers dual booting lin/win and want the best quality sound card I can get that will run on both lin and win with the least trouble and the most bang for the buck. I don't need multitrack recording necessicarily. And what _do_ you need? Neither best quality nor bang are very specific. ;-) Stereo playback? 5.1 playback? Stereo recording? Mic and/or Line input? SPDIF input and/or output? 16 or 24 bits? 48 or 96 kHz? MIDI? .. Regards, Clemens
Re: [linux-audio-dev] best soundcard revisited
Aaron wrote: Ok youre right, Here is what I am using it for: 1. taking hundreds of hours of analog recordings of single people singing and recording them to harddisk then editing them and restoring them. The recordings are both mono and stereo. 2. Do the same thing with digital recordings from minidisk or mp3 recorders. 3. possibly creating demo mixes. In summation for the current project at most stereo recording and if it makes a quality difference 2496, if not cd quality. mic and line in spdif in and out why not? The main issue I was asking about was the best sound card as far as linux support. Multitrack is not needed. For what you are doing, the M-Audio Audiophile 2496 may be just what you need. It has two analog in, two analog out, one stereo SPDIF in, and one stereo SPDIF out (plus MIDI in/out). I think you get it for under $100, and it has great Linux support (including the envy24control utility), plus it has 36-bit DSP, hardware mixing and monitoring. This card does NOT have microphone inputs, you will need a mike pre-amp or mixer w/pre-amps for that (M-Audio makes a nice little mike pre-amp also). -- Brett --- Programmer by day, Guitarist by Night http://www.chapelperilous.net http://www.alhazred.com http://www.revelmoon.com
Re: [linux-audio-dev] linking multiple .o plugins into a single .so library
Paul Davis wrote on Thu, 30-Jun-2005:
and if you want to be really portable, don't use _init() or _fini(),
which are officially deprecated by gcc/glibc/ld.so, and use
void
myinitfunction() __attributes__((constructor))
{
}
void
myfinifunction() __attributes__((destructor))
{
}
The proper syntax is:
void __attribute__((constructor)) myinitfunction() {}
void __attribute__((destructor)) myfinifunction() {}
jlc
[linux-audio-dev] So what are these spufs anyway?
Article about Linux and the upcoming Cell processor at Linux Devices: http://www.linuxdevices.com/news/NS6219524044.html Link at the end of article to IBM: http://www-128.ibm.com/developerworks/power/library/pa-cell/?ca=dgr-lnxw09SpufsCell --
Re: [linux-audio-dev] linking multiple .o plugins into a single .so library
On Thu, Jun 30, 2005 at 02:31:04PM -0400, Paul Davis wrote:
(this only dropped into my mailbox today, for some reason)
and if you want to be really portable, don't use _init() or _fini(),
which are officially deprecated by gcc/glibc/ld.so, and use
void
myinitfunction() __attributes__((constructor))
{
}
void
myfinifunction() __attributes__((destructor))
{
}
Looks very C++ish. Upon load, call all constructors for static
objects. Before unload, all destructors for the same.
--
FA
