FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

[timw0932]

Using foobar2000's "File Integrity Verifier" on two ALAC files converted from FLAC, one by dbpa and the other by Easy CD-DA Extractor, the results are:

*****
Item: "01 A Farewell To Kings.m4a"
MD5: 3FC2888E190FCF7015E72222DA739256
CRC32: 09828224
Warning: Reported length is inaccurate : 5:53.221950 vs 5:53.160000 decoded

Item: "01 A Farewell To Kings.m4a"
MD5: 3FC2888E190FCF7015E72222DA739256
CRC32: 09828224
No problems found.

All items decoded successfully.
1 item decoded with minor problems.

List of decodable but suspicious items:
"01 A Farewell To Kings.m4a"
*****

The warning is for the dbpa file, and all files I converted with dbpa generate similar warnings, with varying discrepancies in lengths. Fortunately, the encoded data is fine, and I know from prior validation of several thousand converted files that dbpa gets the data right. Still, I'm concerned about this length discrepancy as I'm having trouble using some of these files with my Touch and Apple TV, and I have no way of knowing that iTunes isn't creating a glitchy file due to this dbpa problem when it converts my ALAC files to 128 Kbps AAC when I sync. Comments?

[timw0932]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

I looked into this a little more, and dbpa converts its ALAC files with the wrong lengths and number of samples to WAV and FLAC with the right lengths and number of samples. Again, the decoded data is the same for all the files per foobar2000's bit comparison tool, and for the albums that can be verified with CueTools without the .cue files, they check out exactly the same in Accurate Rip.

Here are the results for Yes's "Fragile", with the first number being the difference in length and the second in samples per foobar2000, between a dbpa-converted ALAC file and an iTunes-converted ALAC file; in each case, the dbpa file is the longer:

Yes - [Fragile *blooper*01] Roundabout 0.080 / 3540
Yes - [Fragile *blooper*02] Cans And Brahms 0.071 / 3124
Yes - [Fragile *blooper*03] We Have Heaven 0.020 / 864
Yes - [Fragile *blooper*04] South Side Of The Sky 0.078 / 3468
Yes - [Fragile *blooper*05] Five Per Cent For Nothing 0.016 / 700
Yes - [Fragile *blooper*06] Long Distance Runaround 0.013 / 584
Yes - [Fragile *blooper*07] The Fish (Schindleria Praematurus) 0.061 / 2712
Yes - [Fragile *blooper*08] Mood For A Day 0.080 / 3544
Yes - [Fragile *blooper*09] Heart Of The Sunrise 0.005 / 192

Again, I don't know how these numbers were derived, or if they could affect anything. Any ideas?

[Spoon]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

Will mark as a bug to look at.

[Spoon]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

Bug confirmed, then next update to R14.2 (beta) fixes this.

[imeric]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

Bug confirmed, then next update to R14.2 (beta) fixes this.

So what do I do to fix this on the thousands of ALAC files which have this issue and can't convert to my iPhone in itunes??

[Spoon]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

This bug was 10 years ago, you created ALAC files with dBpoweramp over 10 years ago?

[imeric]

Re: FLAC->ALAC; foobar says "Warning: Reported length is inaccurate"

This bug was 10 years ago, you created ALAC files with dBpoweramp over 10 years ago?

I think it's more like 15 years ago...I converted my library with dBpoweramp back then from FLAC to ALAC for Itunes\Iphone compatibility. Anyhow it looks like reconverting ALAC->ALAC with JRiver fixes my "Warning: Reported length is inaccurate" issue.

Using JRiver as it allows me to do it from a playlist on just these problematic files.