[ecasound] Bugreport ecasound v2.8.1

Hi Guys,

I'm not quite sure if this a bug, but I noticed a strange bwehavior of
ecasound. I wanted to call ecasound like this:

ecasound -t:15 -a:1 -i:louds.wav -f:16,48,44100 -o:jack,CLIENT1 -a:2
-i:mic.wav -f:16,10,44100 -o:jack,CLIENT2 -a:3 -i:jack,CLIENT3 -o:error.wav

But what a actually did was:

ecasound -t:15-a:1 -i:louds.wav -f:16,48,44100 -o:jack,CLIENT1 -a:2
-i:mic.wav -f:16,10,44100 -o:jack,CLIENT2 -a:3 -i:jack,CLIENT3 -o:error.wav

please note the missing blank in "-t:15-a:1". However, the ecasound
output didn't show something unusual:

==========================================================================
**************************************************************************
* ecasound v2.8.1 (C) 1997-2011 Kai Vehmanen and others
**************************************************************************
(eca-chainsetup-parser) Set processing time to 15.00.
(audioio_jack_manager) JACK transport: send/receive disabled (mode:
notransport)
(eca-chainsetup) Chainsetup "untitled-chainsetup"
(eca-chainsetup) WARNING: Input "louds.wav" is not connected to any
chain. (3.1-DISCON-INPUT)
(eca-chainsetup) WARNING: Output "jack" is not connected to any chain.
(3.2-DISCON-OUTPUT)
(eca-chainsetup) Multitrack-mode enabled.
(eca-chainsetup) "rt" buffering mode selected.
(eca-chainsetup) NOTE: using existing audio parameters
-f:s16_le,48,44100 for object 'louds.wav' (tried to open with
-f:s16_le,2,44100).
(eca-chainsetup) Opened input "louds.wav", mode "read". Format: s16_le,
channels 48, srate 44100, interleaved (locked params).
(eca-chainsetup) NOTE: using existing audio parameters
-f:s16_le,10,44100 for object 'mic.wav' (tried to open with
-f:s16_le,48,44100).
(eca-chainsetup) Opened input "mic.wav", mode "read". Format: s16_le,
channels 10, srate 44100, interleaved (locked params).
(eca-chainsetup) NOTE: using existing audio parameters
-f:f32_le,10,44100 for object 'jack' (tried to open with
-f:s16_le,10,44100).
(eca-chainsetup) Opened input "jack", mode "read". Format: f32_le,
channels 10, srate 44100, noninterleaved (locked params).
(eca-chainsetup) NOTE: using existing audio parameters
-f:f32_le,48,44100 for object 'jack' (tried to open with
-f:s16_le,48,44100).
(eca-chainsetup) Opened output "jack", mode "write". Format: f32_le,
channels 48, srate 44100, noninterleaved (locked params).
(eca-chainsetup) NOTE: using existing audio parameters
-f:f32_le,10,44100 for object 'jack' (tried to open with
-f:s16_le,10,44100).
(eca-chainsetup) Opened output "jack", mode "write". Format: f32_le,
channels 10, srate 44100, noninterleaved (locked params).
(eca-chainsetup) Opened output "error.wav", mode "read/write (update)".
Format: s16_le, channels 10, srate 44100, interleaved (locked params).
- [ Connected chainsetup: "untitled-chainsetup" ] ------------------------
- [ Controller/Starting batch processing ] -------------------------------
- [ Engine - Driver start ] ----------------------------------------------
=======================================================================

However, my self-written application CLIENT1, did not work at all. After
some bugging I found out that ecasound acutally sent NaN values to
CLIENT1, breaking all further processing stages. Is in an intended
behavior of ecasound to send Nan values under certain conditions?

Regards,

Martin

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list