headers
Eric Dantan Rzewnicki | 2 Jul 2005 03:45

Re: Unattended Audio Recording / Archiving

check out jack time machine.

Free Lunch wrote:
>>I'm now trying to get ecasound to save automatically every hour with a
>>timestamped file, seemlessly starting a new file.
> 
> 
> I have numerous similar requirements and unfortunately, ecasound can't
> do it today.
> 
> In addition to my own live concert recording needs, I have a friend
> who is in a band.. They are just some guys in a basement.  We want to
> have a microphone in his studio start recording whenever it is turned
> on and there is sound present. It should continue until there is
> silence for a configurable amount of time after.  In this case, the
> mic is plugged into a headless Linux box with a sound card.
> 
> What ecasound could really use is the ability to set a file size or
> time limit. That way, at every 200 MB or 2GB or 20 minutes, it could
> start a new recording file (ideally, gapless).  There are a Lot of
> folks who could use that feature.  It seems to ecome up here in one
> form or another pretty regularly.
> 
> With that feature, it would be easy to write a wrapper script which
> automatically restarted ecasound over and over. Since ecasound already
> has a feature to not start recording until the volume reaches a
> certain level, that part is done.   If the file splits were set at 10
> minutes, it would mean that there would be at most 10 minutes of
> silence following a session, etc.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eric Dantan Rzewnicki | 3 Jul 2005 17:35

DBC_REQUIRE failed

Is this anything to be worried about? I'm guessing not, because it's
just a Warnning. But, I would like to understand what's happening.

Warning: DBC_REQUIRE failed - "to_pos < length_in_samples()",
samplebuffer.cpp, 295.

I get it when playing looping .ewf files. It occurs once per pass
through the source .wav file.

$ cat loop-2005-0703-0829-05-EDT.ewf
source = /mnt/audio/in_progress/amisstt/loops/loop-2005-0703-0829-05-EDT.wav
offset = 0
start-position = 0
length = 11.0986875
looping = true

$ ecalength -f loop-2005-0703-0829-05-EDT.wav
loop-2005-0703-0829-05-EDT.wav: 11.099s         (0m11s)     s24_le,1,48000

So if I play the above with -t:60 the DBC warning is printed 5 times.
With -t:40 warning is printed 3 times, and so on. It's the same for
output to jack_alsa or to alsaplugin.

It doesn't seem to cause any problems in the sound.

ecasound 2.4.1

Thanks,
ERic Rz.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eric Dantan Rzewnicki | 3 Jul 2005 17:47

longlived pyeca.ECA_CONTROL_INTERFACE(0) looses sync

In a python eci script I tried starting one 
pyeca.ECA_CONTROL_INTERFACE(0) and reusing it for many chainsettups. If 
I reuse the same ecasound instance in this way for long enough 
eventually cmd_cnt and last_cnt get out of sync:

(ecasoundc_sa) Error='read() error', cmd='ctrl-add 
-klg:1,0,98,3,0,0,0.168,0.044,0.575354166667,0' last_error='' 
cmd_cnt=1978 last_cnt=1977.

***********************************************************************
* Message from libecasoundc:
*
* Connection to the processing engine was lost. Check that ecasound
* is correctly installed. Also make sure that ecasound is either
* in some directory listed in PATH, or the environment variable
* 'ECASOUND' contains the path to a working ecasound executable.
***********************************************************************


(ecasoundc_sa) Error='sync error', cmd='cop-add -ev' last_error='' 
cmd_cnt=1979 last_cnt=1977.

After the cmd_cnt continues to grow further out of sync for a while 
ecasound eventually fails.

If I instead put the eci instantiation inside a loop that causes
a new ecasound/eci to be spawned for each pass instead of reusing the 
same one over and over again it seems to prevent the problem. Maybe 
there is some bug that only shows for high values of cmd_cnt?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eric Dantan Rzewnicki | 5 Jul 2005 04:34

interaction of -eac and -erc

In a multichannel chain where every channel but 1 is a copy of channel 1 
what is the effect of an -eac:0,1 on channels 1+n?

psuedo example chain:
ecasound -i:foo_mono_input -f:32,4,48000 -o:foo_quad_output \
     -eac:0,1 \
     -erc:1,2 -eac:100,2 \
     -erc:1,3 -eac:100,3 \
     -erc:1,4 -eac:100,4

will channels 2-4 be silent because -eac:0,1 sets amplitude of channel 1 
to zero before it gets copied to the other channels?

or would the other channels get copies of channel one from before the -eac?

I'm guessing the former ...

-ERic Rz.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
(Continue reading)

Permalink | Reply | 1 comment |
headers
oliver oli | 5 Jul 2005 13:47
Picon

Re: OSC ECI?

Mario Lang wrote:
> Hi.
> 
> Are there any plans to move ECI to OSC?
> 
> There are quite some musical applications around which can speak
> OSC these days, but far less can do proper TCP sockets.
> It would be a breeze to write ecasound automations in say, SuperCollider,
> or in Pd...
> 

an OSC interface for ecasound would be nice. but besides OSC-ECI, i
would like to see an OSC interface only for changing control parameter,
not for creating and changing chain setups.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Permalink | Reply | 1 comment |
headers
Pierre Lorenzon | 6 Jul 2005 15:28
Picon

Daemon mode ? ?


Hi,

I got no answer to my question about ecasound's daemon
mode. Indeed why does this mode necessarily run together
with the interactive mode even if you want ecasound
to behave as a server and hence a priori no interaction
in a console but only the possibility to connect
via a client ?

Bests

Pierre

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Permalink | Reply | 0 comments |
headers
Free Lunch | 7 Jul 2005 15:12
Picon

Re: Joining wav via command line

I can do this under sox but ecasound is a bit more tricky for me. 
Give this a try:

Join wav files:

sox file1.wav file2.wav bothout.wav

Mix wav files:

soxmix file1.wav file2.wav mixed.wav

I believe you can use the -v argument to control the volume of the
various mixed audio sources.

Hope this helps,

  FL

On 6/29/05, jacob strachotta <jacob <at> hypnose.dk> wrote:
> Hi¹
> 
> I¹m going to give it a try. Don¹t know if this is the correct mailing list.
> If not then please direct me to one you think would be appropriate for my
> question.
> 
> Question?
> --------------
> I need to join two soundfiles (or more ) wav format 44.1Khz and 16bit. The
> result would be a soundfile that last appx. 15 minutes.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kai Vehmanen | 10 Jul 2005 18:51

new features to EIAM and ecasignalview, 2.4.2-snapshot-20050710

Hello list,

first, sorry for the lack of responses lately, I've been on vacation
without access to email/computers for a while.

I've processed my mailbox from those mails which have contained patches to 
Ecasound. Today I committed two of these, one from Jeffrey Cunningham and 
one from Stuart Allie. These were both very nice additions to Ecasound -- 
thanks guys for the patches!

The ecasignalview user-interface has changed a bit, let me know what do 
you think.

Snapshot that includes all the recent changes is available at:
http://ecasound.seul.org/download/snapshots/ecasound-2.4.2-cvs-20050710.tar.gz

Here're the changes since 2.4.1 release:
 	- added: eiam - ctrlp-list, ctrlp-selected, ctrlp-get, ctrlp-select
 	         and ctrlp-set commands; the last two are RT-commands;
 		 see ecasound-iam(1) for more info [allies]
 	- added: ecasignalview - ability to reset stats with 'spacebar'
 		 and quit with 'q/Q/Esc'; separate logarithmic mode (enable
 	 	 with -L, see also -I which is still the default);
 		 display of per-channel average amplitude; see
 		 ecasignalview(1) man page for details [jeffrey]
 	- changed: various small updates to User's Guide
 	- changed: ecasound user-visible copyright string changed
 	- changed: minor changes to ecasignalview user-interface
 	           [jeffrey,kaiv]
 	- fixed: using ecasound.spec with recent versions of rpm
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kai Vehmanen | 10 Jul 2005 18:58

Re: 2.4.1 daemon mode

Hi,

On Sat, 25 Jun 2005, Pierre Lorenzon wrote:

> Why is the daemon mode always associated
> with the interactive mode ? Indeed even if you
> start ecasound in daemon mode i.e. as a server,
> there is still console with an ecasound running.
> It means that you may not this console for other tasks.

yes, that's how it works now.

As a little background, the daemon mode has been in ecasound
for quite a while, but so far I know only of one or two people besides
me who are actually using it. There are probably more, but still,
I've received very littly feedback on it.

Now personally I use it solely in combination with ecamonitor (comes
with ecasound). I use the main console (one running in --daemon mode)
for controlling my recording and mixing sessions, and the ecamonitor 
running in a second console to see what is happening in the setup while 
I'm recording myself playing something (cannot type commands while
playing :)).

So this probably explains why --daemon behaves as it does currently.
But I'm open to suggestions...

> Finally ecasound's behavior depends on the order the
> options on the command line and not only on the options
> themselves. It might confuse the user !
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kai Vehmanen | 10 Jul 2005 19:06

Re: OSC ECI?

On Tue, 5 Jul 2005, oliver oli wrote:

> Mario Lang wrote:
>> Are there any plans to move ECI to OSC?

Answering to the original question first - yes, I've been closely 
following the OSC discussions on lad/lau, and development of various
helper libraries (especially Steve's liblo).

But I'm still not sure what is the correct approach to take - how much, 
and what, functionality to expose via OSC. That brings us to Oliver's 
comment:

> an OSC interface for ecasound would be nice. but besides OSC-ECI, i
> would like to see an OSC interface only for changing control parameter,
> not for creating and changing chain setups.

Yes, this seems like a good idea. Exposing all of EIAM would be a massive 
task, and we don't really know whether anyone would use the OSC interface. 
But, but, exposing a subset might be a good way to start the OSC work. If 
people use it, then expand functionality. One potential set of functions 
to start with are the EIAM realtime-capable commands (see ecasound-iam(1) 
manpage for the list and description).

Comments, ideas?

--

-- 
  http://www.eca.cx
  Audio software for Linux!
(Continue reading)

Permalink | Reply | 0 comments |

Gmane