Hello linux-audio-dev-request(a)music.columbia.edu
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 @ philc(a)europlex.ie
Regards
Richard Caldwell
> 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 don't know enough about linux module coding. If we can get a
60% functional version in less than a week, I'd be dead chuffed! ;)
We're effectively talking about a driver for the Motorola DSP onboard (I can't
remember what the no is.) We first need to get it to C code- isn't that what
the CPP used to do?
Sorry, it's been a while. 8-)
Hi there,
Waldorf from Germany has made an analog VCF which
could be connected via USB to a computer system:
http://www.waldorf-music.com/afb/
Regards,
Joachim Backhaus
> -----Original Message-----
> From: Thomas Webb [mailto:magusofthedark@yahoo.com]
> Sent: Mittwoch, 19. März 2003 14:52
> To: linux-audio-dev(a)music.columbia.edu
> Subject: Re: [linux-audio-dev] Interface with real modules
>
>
> > However you can still have a lot of fun e.g. having
> > FM or Ringmod between
> > software and true analogue VCOs. It would also be a
> > very good idea to
> > combine a true analogue VCF with a digital synth as
> > it's the filter that
> > is the weakest point of digital synthesis. It is
> > then however difficult to
> > implement proper VCF tracking. This could only be
> > done by using a true
> > analogue MIDI to CV converter, let this control the
> > VCF tracking and send
> > the same notes to the softsynth and the true
> > analogue MCV connected to the
> > VCF.
> yeah, the main thing I was thinking of was using an
> analogue filter.. The medical company I work for has
> this real hightech voltmeter (high res and
> everything). I can probably get that to work
> perfectly with any modules. The only problem is it's
> freaky expensive. Too bad a standard soundcard won't
> work quite right.
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
Hello linux-audio-dev-request(a)music.columbia.edu
I have received your e-mail regarding 'linux-audio-dev digest, Vol 1 #405 - 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 @ 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 #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