Re: [ecasound] RIFF header problem

Excerpts from Joel Roth's message of 2010-09-15 13:09:12 +0200:
> On Wed, Sep 15, 2010 at 12:57:06PM +0200, Philipp ??berbacher wrote:
> > Excerpts from Joel Roth's message of 2010-09-15 12:18:18 +0200:
> > > Kai,
> > >
> > > I'd just like to thank you for Ecasound's -ddd debugging
> > > mode, which enabled me to catch a significant bug in Nama.
> > >
> > > It seems that a mono RIFF header written to output file
> > > "great_1.wav" in a previous engine configuration step, was
> > > forcing a subsequent stereo recording into mono:
> > >
> > > (eca-chainsetup) NOTE: using existing audio parameters
> > > -f:s16_le,1,44100
> > > ... for object 'great_1.wav'
> > > (tried to open
> > > ... with -f:s16_le,2,44100).
> > >
> > > Regards,
> > >
> > > Joel
> > >
> > > --
> > > Joel Roth
> >
> > If it's the same file that's what I'd expect to happen, never thought
> > about that though. It's something to keep in mind, thanks.
>
> Philipp,
>
> Ecasound respecting the format of an existing WAV file *is*
> expected.
>
> Having the RIFF stub file sitting around there was *not*
> expected but Ecasound told me what influenced its decision.
>
> > What did ecasound do exactly? Downmix stereo to mono or just forget
> > about additional channels?
>
> It was a user bug report, so I didn't inspect the files
> directly.
>
> I am pretty sure that Ecasound just threw away the other
> channel. (Ecasound doesn't usually reconfigure itself without
> being directed to do so.)
>
> Joel
>
> > --
> > Philipp
> >
> --
> Joel Roth

Thanks, so I'll watch out for nasty stubs :)

Sadly I won't need to do this very soon, I've currently very little time
to work on my frontend. I hope this gets better in one or two weeks.
There are so many little things that could be done and would really be
improvements, but the big nasty message wrapping task for the reconnect
workaround has to be done before that.

Oh, I talked to Torben Hohn, the head behind jack-session, a few weeks
ago. The automatic shutdown of the engine do get in the way of
jack-session and he said the problem could be solved by decoupling the
jack part, or something, but apparently it's not trivial. Well, there's
hope that he'll do it and add jack-session support sometime. This would
likely happen in a way that ecasound handles the low-level stuff and
exposes what's necessary for frontends to handle the rest.
I'm looking forward to it, but I guess I'll have to show some active
development on my part first ;)

-- 
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Ecasound-list mailing list
Ecasound-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list