<PRAISE> First, thanks to everyone for their contributions to flac. It is obviously a significant piece of work with very good performance. For me, the open-source and anti-copy-protection principals of the project make it the best choice among lossless compressors even if there are closed-source projects with marginally better compression. I firmly believe that the open-source process will further improve those comparisons as development continues. </PRAISE> <REAL-CONTENT> Unfortunately, my first contribution will be to ask about an error. :-) I am encoding files with "-8 -r 99" (e.g. flac -8 -r 99 1.wav 1.3.flac) using version 0.6 under Linux. On one of my flac files, however, I was not able to seek exactly 2 minutes into the file due to the following error: $ flac --skip 5280000 -d 1.3.flac 1.1.wav ... 1.3.flac: ERROR seeking while skipping bytes With a little experimentation, I was able to determine that I cannot seek to samples 5278573 - 5280363. Seeking to samples before and after that yield proper results and if I seek to before that range, the output contains correct decompressed audio for the range to which I cannot seek. Obviously, the error only presents a problem when seeking to this .04 second and I could write my script to recognize this error and advance by a few samples if it gets this error, but I thought it was worth a query. I tried recompressing the file and got the same resulting flac file and the same seeking error for this range. Am I missing something about my arguments to flac? Is there something curious about this flac file? Is there a way to get some information about this tiny part of this 30mb flac file? Thanks sincerely, -Michael
thanks for the good words... it looks like you have found a real bug. is there a way for you to make the input wav and flac file available for download somehow? otherwise I will try and reproduce it with another file. Josh --- Michael Moore <michael_moore@csnw.com> wrote:> I am encoding files with "-8 -r 99" (e.g. flac -8 -r > 99 1.wav 1.3.flac) > using version 0.6 > under Linux. > > On one of my flac files, however, I was not able to > seek exactly 2 minutes > into the file due > to the following error: > > $ flac --skip 5280000 -d 1.3.flac 1.1.wav > ... > 1.3.flac: ERROR seeking while skipping bytes > > With a little experimentation, I was able to > determine that I cannot seek > to samples > 5278573 - 5280363. Seeking to samples before and > after that yield proper > results > and if I seek to before that range, the output > contains correct > decompressed audio for the > range to which I cannot seek. > > Obviously, the error only presents a problem when > seeking to this .04 > second and I could > write my script to recognize this error and advance > by a few samples if it > gets this error, > but I thought it was worth a query. > > I tried recompressing the file and got the same > resulting flac file and > the same seeking > error for this range. > > Am I missing something about my arguments to flac? > Is there something > curious about > this flac file? Is there a way to get some > information about this tiny > part of this 30mb > flac file?__________________________________________________ Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
xflac@yahoo.com writes:>thanks for the good words... it looks like you >have found a real bug. is there a way for you >to make the input wav and flac file available >for download somehow? otherwise I will try and >reproduce it with another file.I just wanted to make sure it wasn't something I was missing. It seems to me that the error is likely to be so rare (in that it affects such a small range of samples in this case) that it may be hard to reproduce without doing exhaustive tests seeking to every sample in a lot of flac files. I figured if it was a real bug, this would be a good thing to get to you for debugging. I have made both the wav and flac files available at: ftp://ftp.gerbilsong.com/pub/ I'll have to take them off the server in 3 or 4 days due to their size. Good luck in tracking down the issue. Take Care, -Michael