19 Jun
2003
19 Jun
'03
8:25 p.m.
Hi,
I'm looking for solution where we can record multiple input
streams of audio to individual files which can then be processed
by other programs on Linux. I've searched the ecasound list and
also the archive of this list.
The best I could find was a similar requirement by someone
using a Delta 1010 card. One of the solutions that was proferred
was to use the JACK audio server.
Is it possible to connect multiple input streams of audio (think
multiple phones or line-in from multiple VCRs or any audio
device) and individually record the streams as a digital file ?
For example - 911 calls , or financial transaction calls etc
I'm looking for a Linux based solution that can do that -
Ideal would be -
a. Well Supported card that has multiple line-in ( so if I want
to record 8/16 audio inputs, it should have 8/16 line-in sockets)
b. Software to record the line-in audio
c. Software to encode it
if b & c can be combined to record and encode like ecasound, it
would be perfect.
I asked around on the ecasound list and was directed to this
list. We're not looking to do any mixing or sound editing.
Our requirements are very simple. Ecasound works very well
for us when using one sound card. We now need to scale this
solution so that we can record the equivalent of 8/12/16 sound
cards each having an instance of ecasound recording and encoding.
A similar solution on the Windows platform seems to be
http://www.dictaphone.com/products/freedom/freedomps/
Any help is highly appreciated,
--
Hiren
----------------------------------------------------------------------
19 Jun
19 Jun
8:44 p.m.
The answer is Ardour. First beta is coming out shortly but I've been
using it from CVS for about 5-6 months. Check out
http://sourceforge.net/projects/ardour also
http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html also
http://ccrma-www.stanford.edu/planetccrma/software/. You can use
qjackconnect to route anything JACK to anything else JACK. Delta 1010,
ST Audio DSP 2000 C-Port, Terratec EWS88MT, or, on the high end, the
Hammerfall cards (digital).
Jan
On Thu, 2003-06-19 at 17:12, Hirendra Hindocha wrote:
Hi,
I'm looking for solution where we can record multiple input
streams of audio to individual files which can then be processed
by other programs on Linux. I've searched the ecasound list and
also the archive of this list.
The best I could find was a similar requirement by someone
using a Delta 1010 card. One of the solutions that was proferred
was to use the JACK audio server.
Is it possible to connect multiple input streams of audio (think
multiple phones or line-in from multiple VCRs or any audio
device) and individually record the streams as a digital file ?
For example - 911 calls , or financial transaction calls etc
I'm looking for a Linux based solution that can do that -
Ideal would be -
a. Well Supported card that has multiple line-in ( so if I want
to record 8/16 audio inputs, it should have 8/16 line-in sockets)
b. Software to record the line-in audio
c. Software to encode it
if b & c can be combined to record and encode like ecasound, it
would be perfect.
I asked around on the ecasound list and was directed to this
list. We're not looking to do any mixing or sound editing.
Our requirements are very simple. Ecasound works very well
for us when using one sound card. We now need to scale this
solution so that we can record the equivalent of 8/12/16 sound
cards each having an instance of ecasound recording and encoding.
A similar solution on the Windows platform seems to be
http://www.dictaphone.com/products/freedom/freedomps/
Any help is highly appreciated,
--
Hiren
----------------------------------------------------------------------
20 Jun
20 Jun
3:45 p.m.
Ardour and JACK are powerful (but still rapidly evolving) answers to a
different question than the one asked here. I think that ecasound + ALSA + 1
or more Delta 1010LT cards would be a plausible basis for addressing this
application, but I don't actually have any of those cards and I'm still
waiting for the day when someone explains ALSA configuration files in a way
that I can understand....
The funny thing about this list is, no matter what question you ask, the
question that gets answered is usually "how do I build a Linux-based musical
recording studio?"
On Thursday 19 June 2003 06:06 pm, Jan Depner wrote:
The answer is Ardour. First beta is coming out
shortly but I've been
using it from CVS for about 5-6 months. Check out
http://sourceforge.net/projects/ardour also
http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html also
http://ccrma-www.stanford.edu/planetccrma/software/. You can use
qjackconnect to route anything JACK to anything else JACK. Delta 1010,
ST Audio DSP 2000 C-Port, Terratec EWS88MT, or, on the high end, the
Hammerfall cards (digital).
Jan
On Thu, 2003-06-19 at 17:12, Hirendra Hindocha wrote:
> Hi,
>
> I'm looking for solution where we can record multiple input
> streams of audio to individual files which can then be processed
> by other programs on Linux. I've searched the ecasound list and
> also the archive of this list.
>
> The best I could find was a similar requirement by someone
> using a Delta 1010 card. One of the solutions that was proferred
> was to use the JACK audio server.
>
> Is it possible to connect multiple input streams of audio (think
> multiple phones or line-in from multiple VCRs or any audio
> device) and individually record the streams as a digital file ?
> For example - 911 calls , or financial transaction calls etc
> I'm looking for a Linux based solution that can do that -
> Ideal would be -
>
> a. Well Supported card that has multiple line-in ( so if I want
> to record 8/16 audio inputs, it should have 8/16 line-in sockets)
> b. Software to record the line-in audio
> c. Software to encode it
>
> if b & c can be combined to record and encode like ecasound, it
> would be perfect.
>
> I asked around on the ecasound list and was directed to this
> list. We're not looking to do any mixing or sound editing.
> Our requirements are very simple. Ecasound works very well
> for us when using one sound card. We now need to scale this
> solution so that we can record the equivalent of 8/12/16 sound
> cards each having an instance of ecasound recording and encoding.
>
> A similar solution on the Windows platform seems to be
> http://www.dictaphone.com/products/freedom/freedomps/
>
>
> Any help is highly appreciated,
> --
> Hiren
> ----------------------------------------------------------------------
4:01 p.m.
Paul Perkins wrote:
Ardour and JACK are powerful (but still rapidly
evolving) answers to a
different question than the one asked here. I think that ecasound + ALSA + 1
or more Delta 1010LT cards would be a plausible basis for addressing this
application, but I don't actually have any of those cards and I'm still
waiting for the day when someone explains ALSA configuration files in a way
that I can understand....
Halt who goes there lurker?
What don't you understand?
Have you read the docs? wiki et al...
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
21 Jun
21 Jun
10:51 a.m.
On Friday 20 June 2003 01:30 pm, Patrick Shirkey wrote:
Paul Perkins wrote:
What don't I understand? I would like to see each concept that the ALSA
configuration file language is intended to be able to express, and then the
syntax used to express that concept. Then some examples with clear
explanations of why each thing in the config file was put there. As in a good
programming language tutorial. What I've seen instead is a lot of chunks of
strange-looking syntax "explained" by saying "try stuffing this in <some
file
somewhere>, and good luck." Which leaves me blundering around in the dark,
hoping to get lucky :-).
I've read a lot of the docs, but of course not everything on the whole web,
especially as new stuff appears all the time. What would you recommend that I
read specifically?
-- Paul Perkins
... and I'm still waiting for the day when
someone explains ALSA
configuration files
in a way that I can understand....
Halt who goes there lurker?
What don't you understand?
Have you read the docs? wiki et al...
23 Jun
23 Jun
2:26 a.m.
Paul Perkins wrote:
On Friday 20 June 2003 01:30 pm, Patrick Shirkey
wrote:
Well there is the documents in the online install guide, The alsa wiki,
Jans howto, and finally the programmer docs have detailed info on the
alsa plugins which you use in the asoundrc.
The latter is the one you will find most revealing about all the syntax
variations. Be aware that after reading that you will have crossed over
from being determined newbie to partly educated newbie. The doc is
designed for programmers and anyone who wants to use an asoundrc at that
level is expected not to be averse to getting their hands dirty.
Paul Perkins wrote:
What don't I understand? I would like to see each concept that the ALSA
configuration file language is intended to be able to express, and then the
syntax used to express that concept. Then some examples with clear
explanations of why each thing in the config file was put there. As in a good
programming language tutorial. What I've seen instead is a lot of chunks of
strange-looking syntax "explained" by saying "try stuffing this in
<some file
somewhere>, and good luck." Which leaves me blundering around in the dark,
hoping to get lucky :-).
... and I'm still waiting for the day when
someone explains ALSA
configuration files
in a way that I can understand....
Halt who goes there lurker?
What don't you understand?
Have you read the docs? wiki et al... I've read a lot of the docs, but of course not
everything on the whole web,
especially as new stuff appears all the time. What would you recommend that I
read specifically?
This really depends on how far you are willing to go. "Don't bend the
spoon... Let the spoon bend you..."
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
10:47 a.m.
Well, the WIKI page on ALSA config files at
http://alsa.opensrc.org/index.php?page=.asoundrc
has evolved to where it is beginning to sound useful. But it doesn't take you
all that far, and it needs explanations of basic terms like "pcm" (in its
peculiar ALSA meaning), "slave", and "plugin". The
"detailed" material on
plugins it references
(http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html) is just a
list of plugin names and plugin argument names, padded with some boiler-plate
text that rarely adds anything that isn't implicit in the names.
I don't measure the power of a computer or of software by what it can do. I
measure power by how much faster or better I can do what I want to do with
the computer or software, than without it. Including the learning time. By
this definition, good documentation makes software more powerful, and
documentation that requires a lot of hunting around and trial-and-error to
make sense of, makes software less powerful.
As for how far I am willing to go, that depends on what I expect to find when
I get there. I'm a pretty good C and Python programmer with a smattering of
C++ and Java, I'll edit fstab, modules.conf, XF86Config, and so on with vi
when I have to (but these days count it as a bug in the distribution when I
do have to). I use Linux for pretty much all my computer activities these
days, except music recording / synthesizing / effects / mixing. I'd like to
use Linux for that as well, but it just doesn't seem to be ready yet. When
Ardour is stable it might be time for me to make another attempt to switch
over (from the evil empire os). Music is enough of a challenge for me, I
don't need to be on the software bleeding edge at the same time.
On Sunday 22 June 2003 11:55 pm, Patrick Shirkey wrote:
Paul Perkins wrote:
> On Friday 20 June 2003 01:30 pm, Patrick Shirkey wrote:
>>Paul Perkins wrote:
>>>... and I'm still waiting for the day when someone explains ALSA
>>>configuration files
>>>in a way that I can understand....
> What don't I understand? I would like to see each concept that the ALSA
> configuration file language is intended to be able to express, and then
> the syntax used to express that concept. Then some examples with clear
> explanations of why each thing in the config file was put there. As in a
> good programming language tutorial. What I've seen instead is a lot of
> chunks of strange-looking syntax "explained" by saying "try stuffing
this
> in <some file somewhere>, and good luck." Which leaves me blundering
> around in the dark, hoping to get lucky :-).
...
"Don't bend the
spoon... Let the spoon bend you..."
Maybe if I had any idea what you mean by "let the spoon bend you" I would also
find the ALSA documentation crystal clear ;-).
Paul Perkins
sigmotto: Liberty is theft.
7622
days inactive
7626
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Hirendra Hindocha -
Jan Depner -
Patrick Shirkey -
Paul Perkins