Subject: Re: [ecasound] s32_le in ecasound
From: Jeremy Hall (email@example.com)
Date: Sun Jul 15 2001 - 17:39:07 EEST
hmm this is really wierd!
ecasound -f:s32_le,26,44100,n -i alsahw,0 -f:s16_le,2,44100 -o test.raw
-erc:3,1 -erc:4,2 -r -b:64
and the machine began making a humming noise that it usually does just
after it had crashed. why does it play, PLAY a sound when it is told to
hmmph this computer is STRANGE!
In the new year, Kai Vehmanen wrote:
> On Sat, 14 Jul 2001, Jeremy Hall wrote:
> > I eed s32_le to be supported in ecasound. Can this be added?
> It's supported.
> > I'm trying to get hardware level of RME9652 working and the only data
> > format it supports is s32_le. but trying to use it in ecasound results in
> > segmentation fault. Is s32_le supported? the manpage doesn't seem to think
> > so, and I am not quite sure how to add it. I'm trying to improve upon
> > performance by avoiding the plug layer of alsa if possible.
> Hmm, from 2.0.1's man page (doc entry for -f):
> fied, host byte-order is used. Currently supported
> formats are "u8" (same as "8"), "s16_le" (same as
> "16"), "s16_be", "s24_le", "s24_be", "s32_le",
> "s32_be", "f32_le" and "f32_be".
> :) But of course, as I can't fully test these pro audio related features,
> there might bugs. You should also try "s24_le". This is also a 32bit
> data format, but the lower 8bits are always null. This is used at least in
> a few higher end cards.
> But I'd be interested in strace and gdb traces.
> Audio software for Linux!
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <firstname.lastname@example.org>.
-- To unsubscribe send message 'unsubscribe' in the body of the message to <email@example.com>.
This archive was generated by hypermail 2b28 : Sun Jul 15 2001 - 17:39:09 EEST