Hello linux-audio-dev-request(a)music.columbia.edu
I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #403 - 17 msgs' I will be out of the office until the 24th of March. Please refer any queries that require immediate attention to Phil Carroll @ philc(a)europlex.ie
Regards
Richard Caldwell
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 descriptions.
Changes in ALSA-0.9 support improve usability of ecasound with
the new ALSA dmix PCM plugin. There have been many important
bugfixes including correct handling of short parameter fades,
broken chainsetup level looping, problems with creating temporary
files and minor build system issues.
---
2. What is ecasound?
Ecasound is a software package designed for multitrack audio
processing. It can be used for simple tasks like audio playback,
recording and format conversions, as well as for multitrack effect
processing, mixing, recording and signal recycling. Ecasound supports
a wide range of audio inputs, outputs and effect algorithms.
Effects and audio objects can be combined in various ways, and their
parameters can be controlled by operator objects like oscillators
and MIDI-CCs. A versatile console mode user-interface is included
in the package.
Ecasound is licensed under the GPL. The Ecasound Control Interface
(ECI) is licensed under the LGPL.
---
3. Changes since last release
Full list of changes is available at
<http://www.wakkanet.fi/~kaiv/ecasound/history.html>.
---
4. Interface and configuration file changes
None.
---
5. Contributors
Patches
Janne Halttunen (the new Python ECI implementation)
Mario Lang (ecasound.el 0.8.2)
Junichi Uekawa (pyecasound.so build)
Kai Vehmanen (various)
Bug Hunting (items closed)
William Goldsmith (2)
Michael Hellwig (1)
Janno Liivak (1)
Raoul Megelas (1)
Feature requests (items implemented)
Oliver Thuns (1)
---
6. Links and files
Web sites:
http://www.eca.cxhttp://www.eca.cx/ecasound
Source packages:
http://ecasound.seul.org/downloadhttp://ecasound.seul.org/download/ecasound-2.2.2.tar.gz
Distributions with maintained ecasound support:
Agnula - http://www.agnula.org
Debian - http://packages.debian.org/unstable/sound/ecasound2.2.html
DeMuDi - http://www.demudi.org
FreeBSD - http://www.freebsd.org/ports/audio.html
Gentoo Linux - http://www.gentoo.org
PLD Linux - http://www.pld.org.pl
PlanetCCRMA - http://www-ccrma.stanford.edu/planetccrma/software
SuSE Linux - http://www.suse.de/en
Contrib Packages for Distributions:
Mandrake - http://rpm.nyvalls.se/sound9.0.html
Note! Distributors do not necessarily provide packages for
the very latest ecasound version.
--
http://www.eca.cx
Audio software for Linux!
> 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 me; David and Brad have experience of Linux
coding, and you have the test and packaging experience. I really want to get
into Linux coding, and am quite happy to do the admin and docs as req'd.
I think we could both learn some new things :)
As you said, David, asm isn't really used, as the goal is portability. It
might come in handy once we've got a driver working and we want to improve
its latency on a specific platform. (I'm thinking Intel and ARM from my
side.)
Wrt pages of code per model, I agree with you that hopefully we can get round
that, perhaps by having a glue layer to different cards. I don't know, it's
been ages since I looked at the code. Have you seen the Echo code, Brad? I'd
suggest we make sure we all have a copy, even if we can't post it to a
central site, so that we are starting from the same point.
We need to classify all the operations that we must provide (the API) and the
operations we can build on from the cards. I'd imagine there's a core set..
What do you think?
> Odd things like the top jack of a two-jack stack becoming inoperative after
> plugging in the bottom plug (in balanced mode).
Sounds like you've got a short in there somewhere.
Regards,
Ranjit.
Hello linux-audio-dev-request(a)music.columbia.edu
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 @ philc(a)europlex.ie
Regards
Richard Caldwell
Hello linux-audio-dev-request(a)music.columbia.edu
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 @ philc(a)europlex.ie
Regards
Richard Caldwell
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
that it can only record sound at a 48000 Hz sampling rate,but playing back
the recorded sound it is a noise.
I wrote a little program myself and I reached the same conclusion that I
can not set other sampling rate than 48000.
My soundcard under Windows records good sound with other sampling
rates.
I have my soundcard on my VIA motherboard.
In my harware Browser looks like this:
Manufacturer: VIA Technologies
Driver: via82cxxx_audio
Can anybody give me a hint?
Best regards
Laci
Hi list,
maybe someone can explain this to me (me==stupid :-) )
In a system/application, that recieves external midi data of any kind,
is there anything one can assume about _when_ some midi data is recieved?
i mean, with audio data, you have the buffer size of the dac/adc, which
(together with sampling rate) enforces some kind of "global clock"
impulse/trigger in your system.
Is there anything similar with midi data?
Still waiting for enlightenment,
Lukas
ps:
oh and btw, i would like to say another BIG THANK YOU to Frank and
Matthias and all the others involved in making the lad conference
possible. i had a realy great time there. Hope we can have something
like this again in not to far future.
Sorry not to respond sooner, can't work out the Konqueror history thing= it
doesn't even sort by date, for crying out loud.. ;)
I downloaded the Event code as well, although not sure where it is on the
machines, since I've converted eveything to Linux. Since the code was put out
publically, can't we just put it up on a project site (eg sourceforge,
freshmeat) as a central resource?
>From what I read we have:
2 x20 bit Layla (David Olofson and Lamar Owen)
Darla 24 and Gina 20 (Brad Arant)
and I have a Darla 20 bit, one of the originals ;) so between us I reckon we
have enough hardware to test a generic driver, and also enough code knowledge
(from your comments) to get something together.
I don't know loads of Intel TBH, my experience is: 6502, Z80, 68000, ARM, and
i386+ only in the last year or so.
What do you reckon about sorting a project out between us? I don't know loads
of Linux module stuff either- Brad and David it sounds like you're the men on
that. I have done quite a bit of coding, and would love to try and keep the
project on track, since you guys know the setting better.
Lamar, since you're on Internet Radio and that, maybe you'd like to do the
testing from an engineer's perspective? (ie with stability and throughput as
your main goals.) Do you have any coding experience?
Let me know what you reckon; it's really cool to hear from other coders who
like a nice sound from their boxes! (And don't want to pay M$ for the
privilege of using their hardware ;)
Regards,
Ranjit.
I Saw the Scratchamp driver for linus is now opensource. Do you think
it's possible now to change the external soundcards in the scratchamp
can be replaced in the driver by internal soundcards?
grtz,
Modnogg