Vorbis - Aug 2004 - arecord/oggenc stops after 3 hours 45 minutes 47 seconds

On Aug 23, 2004, at 9:35 PM, Ralph Giles wrote:
> On Mon, Aug 23, 2004 at 11:49:27AM -0700, Eric Smith wrote:
>
>> I've tracked the problem down to abuse of the C type size_t in
>> aplay.c.  So I'm pretty sure it's not a problem in oggenc.
>
> Hmm. Wouldn't have expected that from alsa, though if it's saving
> as 'wav' you have to sort of hack the pipe output support. Anyway,
> no, there's not reason oggenc should have trouble with large files.
Well, either oggenc or the players have problems with extremely large 
oggfiles (three days or more), we are using oggenc and icecast to 
stream several radio channels in Ogg/Vorbis and after some days, all 
players refuse to play the streams.

May you live long and spamless,

Andreas Bergstr?m

I wrote about the 6 hr. 45 minute problem with arecord from
alsa-utils:
> It looks like they've already fixed this in alsa-utils 1.0.6.
Got home last night and found that even with 1.0.6 it still stopped
recording after 6h 45m 47s.  I switched to ecasound, and after dealing
with some configuration issues, got it to record successfully
overnight (more than 8 hours).

Ralph Giles wrote:
> Wouldn't have expected that from alsa, though if it's saving
> as 'wav' you have to sort of hack the pipe output support.
I knew about that problem, which was why I was using "raw" rather
than "wav".

ecasound works pretty well, but now I'm getting some warnings about
dropped samples.  I don't recall the exact message, and I'm at work
now so I can't look at it.  The message had "alsa" in it
somewhere,
but I'm not sure whether it's from ecasound or the ALSA library.
The machine is a dual Athlon 1900+ running a 2.6.8 kernel, with
nothing else going on, so I'm surprised that there would be any
dropped samples.  But this isn't an Ogg Vorbis problem, so I'll
take it up elsewhere.

Thanks for all the advice!
Eric