ecanormalize

Subject: ecanormalize
From: bart_AT_solozone.com
Date: Thu Dec 11 2003 - 04:36:15 EET

• Next message: Eric Dantan Rzewnicki: "Re: [ecasound] ecasound bug, bad chainsetup or stupid user?"
• Previous message: Eric Dantan Rzewnicki: "Re: [ecasound] inputs in ecs, output on command line (was: .ecs file format)"
• Next in thread: Kai Vehmanen: "Re: [ecasound] ecanormalize"
• Reply: Kai Vehmanen: "Re: [ecasound] ecanormalize"

I also get error in ecanormalize latest version 2.3.2

us_0001.wav us_0002.wav us_0004.wav us_0006.wav
us_0001.wav.gwc us_0003.wav us_0005.wav us_0007.wav
bart_AT_linux:~/normal> ecanormalize -h
Unexpected interrupt... cleaning up.
bart_AT_linux:~/normal> ecanormalize --help
Unexpected interrupt... cleaning up.
bart_AT_linux:~/normal> man ecanormalize
Reformatting ecanormalize(1), please wait...
bart_AT_linux:~/normal> ecanormalize *.wav

(ecasoundc_sa) Error='read() error', cmd='' last_error='' cmd_cnt=1 last_cnt=0.

***********************************************************************
* Message from libecasoundc:
*
* A null client handle detected. This is usually caused by a bug
* in the ECI application. Please report this bug to the author of
* the program.
***********************************************************************

Warning: DBC_CHECK failed - "eci_rep != NULL", ecasoundc_sa.c, 641.
bart_AT_linux:~/normal> ecanormalize -v
Unexpected interrupt... cleaning up.
bart_AT_linux:~/normal>

bart_AT_solozone.com

• Next message: Eric Dantan Rzewnicki: "Re: [ecasound] ecasound bug, bad chainsetup or stupid user?"
• Previous message: Eric Dantan Rzewnicki: "Re: [ecasound] inputs in ecs, output on command line (was: .ecs file format)"
• Next in thread: Kai Vehmanen: "Re: [ecasound] ecanormalize"
• Reply: Kai Vehmanen: "Re: [ecasound] ecanormalize"

This archive was generated by hypermail 2b28 : Thu Dec 11 2003 - 04:31:22 EET