Tommi Sakari Uimonen | 4 Jan 2005 19:08
Picon
Picon

segfault with 24bit recording on ice1712

Hi. I have Audiophile 2496 card (ice1712 alsa driver) and recording 24bit 
gives a segmentation fault after stopping the recording.

ecasound -f:24,2,96000 -i alsa,plughw -o temp.wav

When played, temp.wav is only noise.

ecasound -f:24,2,96000 -i alsa,plughw -o alsa

doesn't segfault but the output is not quite the same as input, sounds 
distorted but it is recognizeable (not pure noise like in the temp.wav)

Is this alsa driver issue or ecasound problem?

Tommi

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.

Aaron Heller | 4 Jan 2005 19:55

Re: segfault with 24bit recording on ice1712


--On Tuesday, January 4, 2005 20:08 +0200 Tommi Sakari Uimonen
<tuimonen <at> cc.hut.fi> wrote:

> Hi. I have Audiophile 2496 card (ice1712 alsa driver) and recording 24bit
> gives a segmentation fault after stopping the recording.
> 
> ecasound -f:24,2,96000 -i alsa,plughw -o temp.wav
> 

When using the hw interface  for ice1712, you have to read 32-bit samples.
You can then then convert to 24 for output, e.g., this works on my machine
(Delta 1010 also an ice1712):

  ecasound -f:s32_le,2,96000 -i:alsa,plughw -f:s24_le,2,96000 -o:temp.wav

Aaron <heller <at> ai.sri.com>
Menlo Park, CA  US

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.

Tommi Sakari Uimonen | 5 Jan 2005 09:14
Picon
Picon

Re: segfault with 24bit recording on ice1712

>> Hi. I have Audiophile 2496 card (ice1712 alsa driver) and recording 24bit
>> gives a segmentation fault after stopping the recording.
>>
>> ecasound -f:24,2,96000 -i alsa,plughw -o temp.wav
>>
> When using the hw interface  for ice1712, you have to read 32-bit samples.

But I'm not using hw interface, I'm using plughw which does the correct 
conversion already in the alsa layer. The only format in which direct hw 
access works, is 32,12,96000 but the conversion to 24 sounds crap:

ecasound -f:s32_le,12,96000 -i:alsa,hw -f:s24_le,2,96000 -o:temp.wav

> You can then then convert to 24 for output, e.g., this works on my machine
> (Delta 1010 also an ice1712):
>
>  ecasound -f:s32_le,2,96000 -i:alsa,plughw -f:s24_le,2,96000 -o:temp.wav
>

Strange, since they have the same chip, but this sounds crap on my card.
I suspect that the 32->24 conversion loses wrong 8 bits or the ordering of 
the three bytes left is wrong. I should do some researching before I can 
truly say what happens. (That is, record 32 then convert it to 24 with 
some other program and compare it to ecasound's conversion)

Tommi

ps. I guess my subscription to the list has lost since my mails go through 
the moderator.

(Continue reading)

Kai Vehmanen | 5 Jan 2005 09:38

Re: segfault with 24bit recording on ice1712

On Wed, 5 Jan 2005, Tommi Sakari Uimonen wrote:

> But I'm not using hw interface, I'm using plughw which does the correct 
> conversion already in the alsa layer. 

Hmm, true, but the segfault might be coming from ALSA. A back-trace
with gdb would help to trace the cause...

> The only format in which direct hw 
> access works, is 32,12,96000 but the conversion to 24 sounds crap:
> ecasound -f:s32_le,12,96000 -i:alsa,hw -f:s24_le,2,96000 -o:temp.wav

Really? What application you used for verifying temp.wav? Does it 
also sound bad when played with ecasound? You could try using libsndfile's 
conversion routines and compare the results:

ecasound -f:s32_le,12,96000 -i:alsa,hw -f:s24_le,2,96000 -o:sndfile,temp.wav

> Strange, since they have the same chip, but this sounds crap on my card.
> I suspect that the 32->24 conversion loses wrong 8 bits or the ordering of 
> the three bytes left is wrong. I should do some researching before I can 
> truly say what happens. (That is, record 32 then convert it to 24 with 
> some other program and compare it to ecasound's conversion)

If that's really the case, then there is a bug ... which should be fixed
asap.

> ps. I guess my subscription to the list has lost since my mails go through 
> the moderator.

(Continue reading)

Krigler Pavol | 5 Jan 2005 22:40
Picon

How to stop ecasound non interactively or via network ?

Hello,

I use jack and multiple ecasound recording processes because I need to 
overlay the recorded tracks. After sending ecasound to background using 
& character I can not stop recording. There are several ecasounds 
running and I don't know how to stop the ecasound. I try to use --daemon 
and --daemon-port and the connect using telnet but there I can stop only 
recording but ecasound process is still running in background.
When recording starts I don't know exact time when to stop recording so 
I can't use -t option. Is it possible to stop ecasound process in non 
interactive mode or via telnet ?

regards,

Krigler Pavol
Slovakradio

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.

Tommi Sakari Uimonen | 5 Jan 2005 23:01
Picon
Picon

Re: segfault with 24bit recording on ice1712

> Hmm, true, but the segfault might be coming from ALSA. A back-trace
> with gdb would help to trace the cause...

I tried to gdb ecasound, but got only this:

gdb ecasound

(gdb) r -f:s32_le,2,96000 -i:alsa,plughw -f:s24_le,2,96000 -o:temp.wav
Starting program: /usr/local/bin/ecasound -f:s32_le,2,96000 -i:alsa,plughw 
-f:s24_le,2,96000 -o:temp.wav
[Thread debugging using libthread_db enabled]
[New Thread -1212301184 (LWP 12262)]
[New Thread -1212302416 (LWP 12263)]
****************************************************************************
*               ecasound v2.3.2 (C) 1997-2003 Kai Vehmanen
****************************************************************************
- [ Session created ] 
------------------------------------------------------
- [ Chainsetup created (cmdline) ] 
-----------------------------------------
- [ Connecting chainsetup ] 
------------------------------------------------
(eca-chainsetup) 'rt' buffering mode selected.

Program exited normally.

>
>> The only format in which direct hw
>> access works, is 32,12,96000 but the conversion to 24 sounds crap:
>> ecasound -f:s32_le,12,96000 -i:alsa,hw -f:s24_le,2,96000 -o:temp.wav
(Continue reading)

Krigler Pavol | 5 Jan 2005 23:42
Picon

How to stop ecasound non interactively or via network ?

Hello,

I use jack and multiple ecasound recording processes because I need to 
overlay the recorded tracks. After sending ecasound to background using 
& character I can not stop recording. There are several ecasounds 
running and I don't know how to stop the ecasound. I try to use --daemon 
and --daemon-port and the connect using telnet but there I can stop only 
recording but ecasound process is still running in background.
When recording starts I don't know exact time when to stop recording so 
I can't use -t option. Is it possible to stop ecasound process in non 
interactive mode or via telnet ?

regards,

Krigler Pavol
Slovakradio

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.

Problem with encoding AAC


Hi all,

	First of all, Happy new year 2005 ! ;)

	I'm trying to convert a file to AAC for months now...

	I use this line to test it
ecasound -C -f:16,2,44100 -b:2048 -t:50 -i:myfile.ogg -o:myfile.aac,32000

	Everything works but at the end of the process I get those lines :
- [ Controller/Batch processing finished ] ---------------------------------
(eca-controller) Disconnecting chainsetup:  "command-line-setup".

	But faac stay in memory. If I kill faac, everything works, including
the generated AAC file.
	I know that faac itself seems to have some problems with "piped
stream", but I can't figure out that nobody can convert a file (even a WAV
file) using ecasound. So is there any solution ? Any tips ?

	Thanks for your reply.

Best regards

Didier BELLAMY
DIGITALDEEJAY
Artists & Labels promotion, WorlWide Electronic Database, MP3, ... and so
more...
http://www.digitaldeejay.com

(Continue reading)

Kai Vehmanen | 6 Jan 2005 09:52

Re: segfault with 24bit recording on ice1712

On Thu, 6 Jan 2005, Tommi Sakari Uimonen wrote:

> Actually this example works fine, aplay and ecasound (-i temp.wav -o 
> alsa) play the file ok, but if I try to play it back in 24bit:
> 
> ecasound -i temp.wav -f 24,2,96000 -o alsa,plughw
> 
> is is buzzing (not noise or distorted sound, just buzzing)

What version of ecasound and alsa-lib? 

I tested various combinations of -f:24 and alsa,plughw but could not get
a segfault or a buzz in the sound with any combination on my machine. I'm 
running ecasound-2.3.5 and alsa-lib-1.0.4 from PlanetCCRMA. 

> These commands play back fine:
> ecasound -i temp.wav -f 16,2,96000 -o alsa,plughw
> ecasound -i temp.wav -f 32,2,96000 -o alsa,plughw

That would suggest a bug in the plughw conversion of alsa-lib or an old 
bug in ecasound.

I recommend always using -f:32,ch,srate when accessing +16bit soundcards. 
I don't know any soundcards that actually consume or produce actual 24bit 
samples. Instead they use 32bit samples with least-significant byte padded 
to nulls. So the correct Ecasound format is f:32,ch,srate. Otherwise 
alsa-lib will have to do conversions.

> I also found more about the segfault. It comes when I try to set the input 
> format to 24bit:
(Continue reading)

Kai Vehmanen | 6 Jan 2005 10:25

Re: Problem with encoding AAC

On Thu, 6 Jan 2005, Didier BELLAMY (DigitalDeejay) wrote:

> 	But faac stay in memory. If I kill faac, everything works, including
> the generated AAC file.
> 	I know that faac itself seems to have some problems with "piped
> stream", but I can't figure out that nobody can convert a file (even a WAV
> file) using ecasound. So is there any solution ? Any tips ?

Hmm, I was now able to reproduce this. Faac doesn't seem to react to plain 
SIGTERM signal. Oh well, will be fixed in upcoming releases.

--

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

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.


Gmane