Kai Vehmanen | 1 Aug 21:37 2005

Re: Can I RealignTime-Offset For Output

Hi,

On Fri, 29 Jul 2005, Janina Sajka wrote:

> Is it possible to have a second chain introduce output some seconds
> later then the other chains?
>
> For example, how can I have -a:2 start it's -o:xxx 5 seconds
> after -a:1 has started? iOr reading its -i:yyy 5 seconds after -a:1
> starts? Is this possible?

yes, you can use the ewf-wrapper format for it. See Ecasound User's Guide, 
and section on "7.2 Ecasound wave files - the .ewf format".

--

-- 
  http://www.eca.cx
  Audio software for Linux!

-------------------------------------------------------
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

Kai Vehmanen | 7 Aug 11:52 2005

Re: triming silence in sound files

Hi,

On Tue, 14 Jun 2005, Louis-David Mitterrand wrote:

>> ecasound -i foo.wav -o foo-cropped.wav -ge:0.5,0.5,0
>>
>> See ecasound(1) for more info about the -ge operator. You probably need to
>> tune the first two parameters (0.5% example) to get optimal results.
> Yes, after looking through the examples I found that operator, and
> indeed it does what I am looking for. However if a file has some silence
> embedded (a sentence with several words) it will be truncated at the
> first silence, which is expected behavior. So I had to use "-ge:1,0" and
> forego end trimming.
[...]
> To effectively trim the end silence, one could maybe process the file in
> reverse with that same operator? Or some other trick?

yep, that would do the trick:

# remove silence at start
sh> ecasound -i foo.wav -o tmp.wav -ge:1,0,0
# reverse, remove silence at start 
sh> ecasound -i reverse,tmp.wav -o tmp2.wav -ge:1,0,0
# reverse to get the original direction
sh> ecasound -i reverse,tmp2.wav -o foo-cropped.wav

I did a quick test, and seems to work ok.

--

-- 
  http://www.eca.cx
(Continue reading)

Kai Vehmanen | 7 Aug 12:48 2005

Re: triming silence in sound files

Hi again,

On Sun, 7 Aug 2005, Kai Vehmanen wrote:
> # remove silence at start
> sh> ecasound -i foo.wav -o tmp.wav -ge:1,0,0
> # reverse, remove silence at start sh> ecasound -i reverse,tmp.wav -o 
> tmp2.wav -ge:1,0,0
> # reverse to get the original direction
> sh> ecasound -i reverse,tmp2.wav -o foo-cropped.wav

doh, stupid me, the 3rd step is of course unnecessary, two runs
will do. Here's a complete script:

ecatrimsilence.sh
--cut--
#!/bin/sh
#
# description: removes silence from the beginning and the end
#              of a file
# version: 20050807-1
# usage: ecatrimsilence.sh <inputfile>

tmp=ecatrimsilence-tmp.wav

if test -e $tmp ; then
   echo "error: temp file $tmp exists, unable to continue..."
   exit 1
fi

if test ! -e $1 ; then
(Continue reading)

Kai Vehmanen | 7 Aug 13:30 2005

reverse audio-obj broken (was: fwd: Re: batch sample editing)

Ugh,

it seems that today is just not my day. There's a hugely embarrassing bug 
in the "reverse" operator, that I noticed only today (see my post to lau 
below). It's sad to say this bug has gone unnoticed for over 3 years. :(

---------- Forwarded message ----------
Date: Sun, 7 Aug 2005 14:27:20 +0300 (EEST)
From: Kai Vehmanen <kvehmanen <at> eca.cx>
To: A list for linux audio users <linux-audio-user <at> music.columbia.edu>
Subject: Re: [linux-audio-user] batch sample editing

Arghghg,

quick update to my previous mail:

** NOTE to all, don't use this script to process anything important! **

There seems to be a bug in the reverse op used in the script, which hasn't been 
noticed before. I noticed this just a few mins after sending the original mail. 
Ugh, this is embarrassing. :(

On Sun, 7 Aug 2005, Kai Vehmanen wrote:
> here's yet another way to this (with ecasound this time). First a script to 
> trim one file:
> 
> ecatrimsilence.sh:

Problem is in ecasound and will be fixed in 2.4.2, which will be released very 
soon now.
(Continue reading)

Kai Vehmanen | 7 Aug 19:29 2005

Re: reset "over" counters in ecasignalview?

Hi,

a follow-up to an older issue.

On Fri, 20 May 2005, Kai Vehmanen wrote:

> On Fri, 20 May 2005, Peter Lutek wrote:
>> shouldn't the ecasound-iam "start" be the trigger for file-writing, rather
>> than the start of a separate ecasignalview process?
> All these problems are caused by the fact that both ecasound and 
> ecasignalview are JACK-transport aware. So when you issue "start" in 
> ecasound, also ecasignalview will start, and when issue "stop", also
[...]
> Now when JACK-transport support was introduced initially, there was some 
> discussion on what the default behaviour should be. It was decided that full 
> support ("-G:jack,ecasound,sendrecv") is the best default. But, but,
> I guess for ecasignalview this really doesn't make that much sense. I'll add 
> this for my 2.4.2 todo-list.

I just committed a change to CVS (will be in 2.4.2), that causes 
ecasignalview to disable sending/receiving JACK-transport events. This 
should be the best solution from "least-surprises" design perspective.

--
  http://www.eca.cx
  Audio software for Linux!

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
(Continue reading)

Kai Vehmanen | 7 Aug 19:36 2005

Re: Jack transport problem

Hi,

and more will-be-part-of-2.4.2 issues...

On Mon, 7 Mar 2005, Jack O'Quin wrote:
> Interpreting the transport state transition from Rolling to Stopped as
> an EOF certainly makes sense in many situations.  But, I recall trying
> to do something similar to Olivier, repeatedly stopping and starting a
> non-interactive ecasound session.  That would be nice to have (as an
> option, perhaps).

Ok, I've now committed a new "--keep-running" (or just "-K") option
which will cause ecasound to run forever, or until an error is found.
This option has no affect to interactive mode ("-c") operation. The new 
options are also documented in CVS version of ecasound(1).

> This raises the question of how to terminate a non-interactive
> ecasound.  Olivier's suggestion (Ctrl-C) seems OK to me.

And as mentioned already earlier, Ctrl-C has always been a valid way to 
stop an ecasound session (be it interactive or not).

--

-- 
  http://www.eca.cx
  Audio software for Linux!

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
(Continue reading)

Kai Vehmanen | 7 Aug 20:21 2005

Re: 2.4.1 daemon mode

Hi,

On Sun, 10 Jul 2005, Pierre Lorenzon wrote:

> Thank you for your answer. I would simply suggest not to
> inhibit the deamon mode to run in conjunction with
> the interactive mode i.e. to allow the user to enter both
> --daemon and -c one the command line but to allow
> --daemon -C as well.

and this is now possible (CVS + will be in 2.4.2).

It turned out that there was also a technical reason between the daemon 
and interactive mode linkage. In non-interactive mode, ecasound normally 
exits when one round of processing has finished. This is usually what 
users want in daemon mode, which led to the requirement of also enabling 
interactive mode. This has now been changed in CVS.

--

-- 
  http://www.eca.cx
  Audio software for Linux!

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
(Continue reading)

Kai Vehmanen | 7 Aug 23:41 2005

Ecasound 2.4.2 released

Hello list,

time for another release. CVS is tagged with 'v2_4_2' as usual.
Here are the release notes:

--
1. Summary of changes

Ecasignalview user-interface has been improved. A set of new commands 
for modifying effect parameters was added to interactive mode. Many 
bugs have been fixed in documentation, JACK transport support, build 
system and elsewhere. A severe bug in the "reverse" audio object was 
fixed.

---
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.

Primary platform for running Ecasound is GNU/Linux. Ecasound can 
also be run on many UNIX-derived systems such as FreeBSD, Mac OS X 
and Solaris. Limited support for Windows is available through 
(Continue reading)

Picon

problems with cs-set-position

hi all,
when i made successively "cs-set-position time-in-seconds" a have two 
problems:
- i have a littler "jump" or "silent" in the reproduction
- if i made a "cs-get-position" and a "ai-get-position" the return value 
is correct if the reference i took is the value sended with 
set-position, but it wasn`t the real time position of the song. This 
didn`t happen if i made a big jump in the time position. E.g., i make 
four "cs-set-position 100" every 2 seconds (or less), a cs-get-position 
and a ai-get-position give me 100 but i can listen the real time is over 
105-108. If i make ai-set-position i haven`t this problem.

I tried it with ecasound 2.4.1 and 2.4.2
some with there problems?

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

Kai Vehmanen | 8 Aug 13:31 2005

Re: problems with cs-set-position

Hi,

On Mon, 8 Aug 2005, Pedro Antonio Fructuoso Merino wrote:

> when i made successively "cs-set-position time-in-seconds" a have two 
> problems:
> - i have a littler "jump" or "silent" in the reproduction

yes, this is unavoidable due to double-buffering performed by the
disk i/o subsystem. You can minimize by disabling the double-buffer 
(-z:nodb), but you will increase the risk of xruns.

> - if i made a "cs-get-position" and a "ai-get-position" the return value is 
> correct if the reference i took is the value sended with set-position, but it 
> wasn`t the real time position of the song. This didn`t happen if i made a big 
> jump in the time position. E.g., i make four "cs-set-position 100" every 2 
> seconds (or less), a cs-get-position and a ai-get-position give me 100 but i 
> can listen the real time is over 105-108. If i make ai-set-position i haven`t 
> this problem.

Ok, this sounds a possible bug. There will be some delay between the 
cs-get-position and what is currently played out caused by audio device 
output latency, but this should not be multiple seconds. Do you get the
same results with -z:nodb ...?

One thing to be careful is mixing ai-set-position and cs-set-position. The 
two can be independently set - i.e. if you set ai-set-position to 102, 
cs-get-position (the chainsetup level position) is unaware of this. And 
also, ai-set-position is not a real-time command (see ecasound-iam(1) man
page for details) which means that the whole engine is stopped and restarted
(Continue reading)


Gmane