12 Feb
2006
12 Feb
'06
9:40 a.m.
Dear Linux audio people,
sverb 0.90 is out at:
http://sed.free.fr/sverb
sverb is an order 15 cfdn reverb.
Changes:
More presets were added.
If someone wants to contribute a ladspa support, it's welcome.
We could have one effect for each preset (with names like
"short reverb 1", "huge reverb").
Then, for each preset, we can control the reverb with two parameters
(t60(0) and t60(pi)), which would make a nice and tiny GUI.
(Maybe also add a dry/wet control.)
We also need to handle stereo, with a basic decorrelation
for example (different delays for left and right channel).
Since sverb has three internal operating modes (float, int, asm),
I think three .so would be nice. For the asm and int libraries,
we could add a third control for the bit resolution (or leave
it to a default, currently 14, but which could be set at compile
time why not).
Before going to 1.0, I need some feedback about the quality of
the various reverbs (I know that big 2 is not that good).
Also, if someone knows how to define good parameters (by hand
or algorithmically) for the delay lines, help is very welcome.
Take care of yourself,
Cedric.
20 Feb
20 Feb
4:28 a.m.
Hi Cedric!
Can sverb work without a gui, like a simple command-line utility? I'm blind,
yet would like to use this piece of software. It sounds great!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
9:43 a.m.
Hi Julien,
I'll try to work on it.
What about a pipe-approach?
I don't want to deal with the zillions of audio file formats,
so I'll take raw mono input on stdin (float or short, little or
big endian) and produce raw data (float or short) on stdout.
You could set parameters with zillions of command line arguments
(mostly: choose a preset, a t60(0), a t60(pi), a float/int/asm
choice of calculatin a bit resolution for the fixed arithmetic,
a dry/wet control, a bypass-t60 toggle, controls for input/output
formats).
Maybe it should handle stereo input and/or output?
Algorithm has been implemented with 44.1 KHz resolution but
can work with anything (of course the same set of parameters
won't give the same reverberation time).
What do you think of it?
I don't have much time for the moment, but as soon as I get
some, I'll do it. Tell me what you absolutely need, so I can
provide you with it as soon as I can. (Of course if someone
has got some brain's idle, any contribution is welcome.)
Take care,
Cédric.
On Mon, 20 Feb 2006, Julien Claassen wrote:
Hi Cedric!
Can sverb work without a gui, like a simple command-line utility? I'm blind,
yet would like to use this piece of software. It sounds great!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
28 Feb
28 Feb
3:48 p.m.
Hi Cedric!
I think this will be perfectly nice for a start. But what about libsndfile?
I'm not such a good programmer, but I think it makes handling those formats
relatively easy. But this is just an idea to get it more comfortable. If it's
not so easy and quick after all, just go ahead.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
4:49 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Hi folks
A while ago there was some talk on the newsgroup about my Juce library,
and people were asking if/when I'd add support for audio under Linux..
well it's taken me a while to get round to it, but I finally battled
through the hostile, undocumented jungle of ALSA, and the latest Juce
release does finally make a noise under Linux!
Some quick background info for those of you who won't be familiar with
Juce - it's a cross-platform (Windows/Mac/Linux) GUI + everything else
library, similar to Qt, wxWindows, etc, released under the GPL. Because
of my background (I wrote Tracktion), there's a lot of audio stuff in
there, and it's got cross-platform support for DirectSound, ASIO,
CoreAudio.. and now ALSA.
So anyway, if anyone's interested in having a go, that'd be great, as so
far I've only been able to test it on my laptop's built-in soundcard!
The Juce demo app has an audio page which monitors incoming audio, plays
wavefiles and has a simple synthesizer. It lets you pick a soundcard,
change its sample rate, etc.
Hope this is of interest to people! More info here:
http://www.rawmaterialsoftware.com/juce
and downloads here:
http://www.rawmaterialsoftware.com/juce/download.php
(Oh - and before anyone asks "does this mean Tracktion is going to come
out on Linux soon", the answer is "I don't know"!)
Cheers!
Jules
5:02 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Tue, 2006-02-28 at 21:49 +0000, Julian Storer wrote:
the hostile, undocumented jungle of ALSA
Please, stop repeating the myth that ALSA is undocumented.
http://www.alsa-project.org/documentation.php
http://www.alsa-project.org/alsa-doc/alsa-lib/
http://www.alsa-project.org/alsa-doc/alsa-lib/examples.html
Lee
5:27 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Tue, 2006-02-28 at 21:49 +0000, Julian Storer wrote:
Hi folks
A while ago there was some talk on the newsgroup about my Juce library,
and people were asking if/when I'd add support for audio under Linux..
well it's taken me a while to get round to it, but I finally battled
through the hostile, undocumented jungle of ALSA, and the latest Juce
release does finally make a noise under Linux!
why did you decide to add ALSA support rather than JACK (which is 200%
simpler than ALSA, 150% closer to ASIO/CoreAudio's callback model and
200% more useful to 50% of users) ? or at least, why not portaudio?
;)
--p
5:34 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
I could (and probably will) add Jack support later, but assumed that
ALSA's the lowest-common-denominator sound API.
Paul Davis wrote:
On Tue, 2006-02-28 at 21:49 +0000, Julian Storer
wrote:
Hi folks
A while ago there was some talk on the newsgroup about my Juce library,
and people were asking if/when I'd add support for audio under Linux..
well it's taken me a while to get round to it, but I finally battled
through the hostile, undocumented jungle of ALSA, and the latest Juce
release does finally make a noise under Linux!
why did you decide to add ALSA support rather than JACK (which is 200%
simpler than ALSA, 150% closer to ASIO/CoreAudio's callback model and
200% more useful to 50% of users) ? or at least, why not portaudio?
;)
--p
6 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Hi all,
<rant>
I am sorry but the alsa documentation is poor. I
always resort to looking at other peoples applications
to see what they have done. A case in point is the
alsa sequencer. It does have a nice page which
explains just enough to get you going but the api is
much larger than this and some of the function
documentation is banal to say the least.
The audio stuff is even worse!
There is some conceptual documentation which seems
very old and I am not sure whether it is up to date.
</rant>
<caveat>
For an open source project that is not used
commercially the documentation is amongst the best
that I have seen and we all know how difficult it is
to find time to spend on this stuff. I have been
trying for years but between work, study and actually
trying to make some music I have ended up making no
contribution (so who am I to talk!).
</caveat>
sorry but that's my opinion,
Kev
--- Lee Revell <rlrevell(a)joe-job.com> wrote:
On Tue, 2006-02-28 at 21:49 +0000, Julian Storer
wrote:
http://www.alsa-project.org/alsa-doc/alsa-lib/examples.html
the hostile, undocumented jungle of ALSA
Please, stop repeating the myth that ALSA is
undocumented.
http://www.alsa-project.org/documentation.php
http://www.alsa-project.org/alsa-doc/alsa-lib/
Lee
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security
Centre. http://uk.security.yahoo.com
6:31 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Tue, 2006-02-28 at 22:33 +0000, Julian Storer wrote:
I could (and probably will) add Jack support later,
but assumed that
ALSA's the lowest-common-denominator sound API.
ALSA is a good choice for a "consumer" app like a movie or CD player.
For musician stuff, JACK has been the standard for a few years now.
Lee
10:56 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Hi Julian,
Just compiled juce and tried the demo programme. Got
the error contained in the attached screen capture. I
don't normally have any problems running alsa audio
apps, however the fault may be in my alsa setup.
Kev
--- Julian Storer <jules(a)rawmaterialsoftware.com>
wrote:
Hi folks
A while ago there was some talk on the newsgroup
about my Juce library,
and people were asking if/when I'd add support for
audio under Linux..
well it's taken me a while to get round to it, but I
finally battled
through the hostile, undocumented jungle of ALSA,
and the latest Juce
release does finally make a noise under Linux!
Some quick background info for those of you who
won't be familiar with
Juce - it's a cross-platform (Windows/Mac/Linux) GUI
+ everything else
library, similar to Qt, wxWindows, etc, released
under the GPL. Because
of my background (I wrote Tracktion), there's a lot
of audio stuff in
there, and it's got cross-platform support for
DirectSound, ASIO,
CoreAudio.. and now ALSA.
So anyway, if anyone's interested in having a go,
that'd be great, as so
far I've only been able to test it on my laptop's
built-in soundcard!
The Juce demo app has an audio page which monitors
incoming audio, plays
wavefiles and has a simple synthesizer. It lets you
pick a soundcard,
change its sample rate, etc.
Hope this is of interest to people! More info here:
http://www.rawmaterialsoftware.com/juce
and downloads here:
http://www.rawmaterialsoftware.com/juce/download.php
(Oh - and before anyone asks "does this mean
Tracktion is going to come
out on Linux soon", the answer is "I don't know"!)
Cheers!
Jules
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security
Centre. http://uk.security.yahoo.com
11:14 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed, 2006-03-01 at 03:56 +0000, Kevin Hremeviuc wrote:
Hi Julian,
Just compiled juce and tried the demo programme. Got
the error contained in the attached screen capture. I
don't normally have any problems running alsa audio
apps, however the fault may be in my alsa setup.
Kev
It appears that Juce is opening the "hw" PCM which only support S32_LE
on your device. It should be opening the "default" PCM which will
automagically convert whatever format Juce uses to S32_LE.
Lee
1 Mar
1 Mar
4:02 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Ok, thanks Lee - I deliberately used the hw pcm devices though, as they
gave better performance than the default one. I guess it just needs
support for some extra data formats.
Lee Revell wrote:
On Wed, 2006-03-01 at 03:56 +0000, Kevin Hremeviuc
wrote:
Hi Julian,
Just compiled juce and tried the demo programme. Got
the error contained in the attached screen capture. I
don't normally have any problems running alsa audio
apps, however the fault may be in my alsa setup.
Kev
It appears that Juce is opening the "hw" PCM which only support S32_LE
on your device. It should be opening the "default" PCM which will
automagically convert whatever format Juce uses to S32_LE.
Lee
5:42 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Julian Storer wrote:
Ok, thanks Lee - I deliberately used the hw pcm
devices though, as
they gave better performance than the default one. I guess it just
needs support for some extra data formats.
What do you mean? Better performance in what way?
The "default" will have no performance hit is the sound card supports
the same format as the application, otherwise, "default" will
automatically do sample format conversion.
In any case, the ALSA device name to use should be user configurable.
James
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.
6:56 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Am I right in assuming that by default you mean the "plughw:" devices?
On my machine the plughw: device glitched constantly, but the hw:
devices worked really well. There was also some other reason I chose
that.. can't remember offhand what it was though.
James Courtier-Dutton wrote:
Julian Storer wrote:
Ok, thanks Lee - I deliberately used the hw pcm
devices though, as
they gave better performance than the default one. I guess it just
needs support for some extra data formats.
What do you mean? Better performance in what way?
The "default" will have no performance hit is the sound card supports
the same format as the application, otherwise, "default" will
automatically do sample format conversion.
In any case, the ALSA device name to use should be user configurable.
James
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be
copied, disclosed to, retained or used by, any other party. If you are
not an intended recipient then please promptly delete this e-mail and
any attachment and all copies and inform the sender. Thank you.
7:31 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Julian Storer wrote:
Am I right in assuming that by default you mean the
"plughw:" devices?
On my machine the plughw: device glitched constantly, but the hw:
devices worked really well. There was also some other reason I chose
that.. can't remember offhand what it was though.
"default" means
just that. use the name "default" instead of plughw:....
or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA or
your application.
How is you application deciding on sample rate?
There is no sensible reason to ever use the "hw:0,0" device. Always use
the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
James
P.S. Please don't top post.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.
7:44 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed Mar 01, 2006 at 12:31:09PM +0000, James Courtier-Dutton wrote:
what does this mean. put the reply below the quoted content? in most readers i can think
of off the top of myy head, the top is the best place to put a reply,. since it is more
likely to show up in a brief synopsis, ,and not require paging down.. but then most of the
world likes to prewrap their messages which is annoyingly narrow on a big screen or
suffers from linebreak-hell on a cellphone, , so i guess i'll remain on the fringes of
acceptability
Julian Storer wrote:
yeah, this is good news , a windows/mac developer who has ventured into the fray. awfully
rare in this day and age. to most of these people, its as if this world doesnt exist.
Am I right in
assuming that by default you mean the "plughw:" devices?
On my machine the plughw: device glitched constantly, but the hw:
devices worked really well. There was also some other reason I chose
that.. can't remember offhand what it was though.
"default" means
just that. use the name "default" instead of plughw:....
or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA or
your application.
How is you application deciding on sample rate?
There is no sensible reason to ever use the "hw:0,0" device. Always use
the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
James
P.S. Please don't top post.
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.
7:52 a.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
James Courtier-Dutton wrote:
Julian Storer wrote:
Am I right in assuming that by default you mean
the "plughw:"
devices? On my machine the plughw: device glitched constantly, but
the hw: devices worked really well. There was also some other reason
I chose that.. can't remember offhand what it was though.
"default" means just that. use the name "default" instead of
plughw:.... or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA
or your application.
How is you application deciding on sample rate? There is no sensible reason to ever use the
"hw:0,0" device. Always
use the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
Ok, at the risk of "spreading the myth" that the ALSA documentation is
bad... is this stuff actually explained anywhere?? It took me a day of
googling just to find out what the two numbers after "hw" meant! I never
saw anything mention "default" or "plug:front", etc.
Not sure if it'd be appropriate anyway, though, as my API exposes a list
of drivers and lets the user choose which one to use, and the sample
rate, rather than just using the default driver.
James
P.S. Please don't top post.
12:23 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed, 2006-03-01 at 09:02 +0000, Julian Storer wrote:
Ok, thanks Lee - I deliberately used the hw pcm
devices though, as they
gave better performance than the default one. I guess it just needs
support for some extra data formats.
This is broken - you'd have to embed knowledge of every single format
that ALSA supports in your app, or else your app will only support
certain soundcards!
Please, at least make this configurable.
Lee
12:26 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed, 2006-03-01 at 12:51 +0000, Julian Storer wrote:
James Courtier-Dutton wrote:
Yes, see the links to the ALSA documentation I posted in my last
message. You also could have searched the mailing list archives.
Lee
Julian Storer wrote:
Am I right in assuming that by default you mean
the "plughw:"
devices? On my machine the plughw: device glitched constantly, but
the hw: devices worked really well. There was also some other reason
I chose that.. can't remember offhand what it was though.
"default" means just that. use the name "default" instead of
plughw:.... or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA
or your application.
How is you application deciding on sample rate? There is no sensible reason to ever use the
"hw:0,0" device. Always
use the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
Ok, at the risk of "spreading the myth" that the ALSA documentation is
bad... is this stuff actually explained anywhere?? It took me a day of
googling just to find out what the two numbers after "hw" meant! I never
saw anything mention "default" or "plug:front", etc.
Not sure if it'd be appropriate anyway, though, as my API exposes a list
of drivers and lets the user choose which one to use, and the sample
rate, rather than just using the default driver.
12:59 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed, 2006-03-01 at 12:51 +0000, Julian Storer wrote:
James Courtier-Dutton wrote:
Here is some information:
http://www.sabi.co.uk/Notes/linuxSoundALSA.html
You are right that there's not a lot of "user-level" documentation for
ALSA, because it's not really intended to be used by end users - ALSA
provides a complete HAL which more user friendly APIs like JACK are
built on top of. You would not write a complex app in straight Xlib...
The standard approach for open source development is to ask about it on
one of the many mailing lists or IRC channels, rather than forging ahead
on your own with only Google as your guide. Due to the proliferation of
Wikis by less informed users, most of the information that Google
returns is half-wrong.
Lee
Julian Storer wrote:
Am I right in assuming that by default you mean
the "plughw:"
devices? On my machine the plughw: device glitched constantly, but
the hw: devices worked really well. There was also some other reason
I chose that.. can't remember offhand what it was though.
"default" means just that. use the name "default" instead of
plughw:.... or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA
or your application.
How is you application deciding on sample rate? There is no sensible reason to ever use the
"hw:0,0" device. Always
use the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
Ok, at the risk of "spreading the myth" that the ALSA documentation is
bad... is this stuff actually explained anywhere?? It took me a day of
googling just to find out what the two numbers after "hw" meant! I never
saw anything mention "default" or "plug:front", etc.
Not sure if it'd be appropriate anyway, though, as my API exposes a list
of drivers and lets the user choose which one to use, and the sample
rate, rather than just using the default driver.
1:42 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
Lee Revell wrote:
On Wed, 2006-03-01 at 12:51 +0000, Julian Storer
wrote:
Thanks for the link - I'd not seen that page before. I'll have another
look at all this asap.
James Courtier-Dutton wrote:
Here is some information:
http://www.sabi.co.uk/Notes/linuxSoundALSA.html
You are right that there's not a lot of "user-level" documentation for
ALSA, because it's not really intended to be used by end users - ALSA
provides a complete HAL which more user friendly APIs like JACK are
built on top of. You would not write a complex app in straight Xlib...
The standard approach for open source development is to ask about it on
one of the many mailing lists or IRC channels, rather than forging ahead
on your own with only Google as your guide. Due to the proliferation of
Wikis by less informed users, most of the information that Google
returns is half-wrong.
Lee
Julian Storer wrote:
Ok, at the risk of "spreading the myth" that the ALSA documentation is
bad... is this stuff actually explained anywhere?? It took me a day of
googling just to find out what the two numbers after "hw" meant! I never
saw anything mention "default" or "plug:front", etc.
Not sure if it'd be appropriate anyway, though, as my API exposes a list
of drivers and lets the user choose which one to use, and the sample
rate, rather than just using the default driver.
Am I right in assuming that by default you mean
the "plughw:"
devices? On my machine the plughw: device glitched constantly, but
the hw: devices worked really well. There was also some other reason
I chose that.. can't remember offhand what it was though.
"default" means just that. use the name "default" instead of
plughw:.... or hw:0,0
If the device glitched when using "plughw:" then it is a bug in ALSA
or your application.
How is you application deciding on sample rate?
There is no sensible reason to ever use the "hw:0,0" device. Always
use the "plug:front" and friends.
If an application only works with "hw:0,0" it has been written wrongly.
1:53 p.m.
New subject: [linux-audio-dev] Juce now has ALSA support!
On Wed, 2006-03-01 at 18:42 +0000, Julian Storer wrote:
Thanks for the link - I'd not seen that page
before. I'll have another
look at all this asap.
Really, your time would be better spent getting to know JACK, or even
PortAudio, than trying to get your brain around ALSA. But feel free to
ask here or on alsa-devel or alsa-user at lists.sourceforge.net if you
have any ALSA questions...
Lee
6636
days inactive
6653
days old
linux-audio-dev@lists.linuxaudio.org
22 comments
8 participants
participants (8)
-
cdr -
Cedric Roux -
James Courtier-Dutton -
Julian Storer -
Julien Claassen -
Kevin Hremeviuc -
Lee Revell -
Paul Davis