Hi,
I'm trying to record something for about 24 hours but oggenc tells me that I
have 203m remaining.
Quote:
durand at Deuterium ~> arecord -f cd -t wav | oggenc -b 192 -o file.ogg -
Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz,
Stereo
Opening with wav module: WAV file reader
Encoding standard input to
"file.ogg"
at approximate bitrate 192 kbps (VBR encoding enabled)
[ 0.1%] [203m23s remaining]
Is there a reason for this? It's not a storage limitation because I have
plenty of space. Finally, is there a way that I can bypass this limit?
Thanks!
Have you just tried to encode it? The 203m remaining message may be misleading - after all it gets it through a pipe, so doesn't really know how long the file is that it encodes. It might just work. Cheers, Silvia. On Mon, Jul 6, 2009 at 11:54 AM, Durand<durand1 at gmail.com> wrote:> Hi, > > I'm trying to record something for about 24 hours but oggenc tells me that I have 203m remaining. > > Quote: > > durand at Deuterium ~> arecord -f cd -t wav | oggenc -b 192 -o file.ogg - > Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo > Opening with wav module: WAV file reader > Encoding standard input to > ? ? ? ? ?"file.ogg" > at approximate bitrate 192 kbps (VBR encoding enabled) > ? ? ? ?[ ?0.1%] [203m23s remaining] > > > Is there a reason for this? It's not a storage limitation because I have plenty of space. Finally, is there a way that I can bypass this limit? > > Thanks! > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev >
Durand a ?crit :> Hi, > > I'm trying to record something for about 24 hours but oggenc tells me that I have 203m remaining. > > Quote: > > durand at Deuterium ~> arecord -f cd -t wav | oggenc -b 192 -o file.ogg -My guess is that it has to do with the wav file header. arecord doesn't know the duration of the wav file (since it's live), so it has to put "something" in the wav header for duration. I would assume it puts 0xffffffff or something, meaning that oggenc interprets this as the file length. I would suggest making arecord output raw pcm instead to make sure there's no confusion. Cheers, Jean-Marc> Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo > Opening with wav module: WAV file reader > Encoding standard input to > "file.ogg" > at approximate bitrate 192 kbps (VBR encoding enabled) > [ 0.1%] [203m23s remaining] > > > Is there a reason for this? It's not a storage limitation because I have plenty of space. Finally, is there a way that I can bypass this limit? > > Thanks! > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev > >
On Mon, 06 Jul 2009 03:07:43 +0100, Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote:> Have you just tried to encode it? The 203m remaining message may be > misleading - after all it gets it through a pipe, so doesn't really > know how long the file is that it encodes. It might just work. > > Cheers, > Silvia. >Yes I have, it doesn't work unfortunately :( On Mon, 06 Jul 2009 03:09:07 +0100, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote:> My guess is that it has to do with the wav file header. arecord doesn't > know the duration of the wav file (since it's live), so it has to put > "something" in the wav header for duration. I would assume it puts > 0xffffffff or something, meaning that oggenc interprets this as the file > length. I would suggest making arecord output raw pcm instead to make > sure there's no confusion. > > Cheers, > > Jean-MarcThat did the trick! I'm now using "arecord -f cd -t raw | oggenc -b 192 -o file.ogg --raw -" and its now counting up rather than down. Thanks!