Incorrect "Length" value for audio files causes cumulative timing errors

Found a bug in "Everything"? report it here
Debugger
Posts: 726
Joined: Thu Jan 26, 2017 11:56 am

Incorrect "Length" value for audio files causes cumulative timing errors

Post by Debugger »

Incorrect "Length" value for audio files causes cumulative timing errors

Hello,

I believe I found an issue with the Length column in Everything.

For many audio files, the displayed Length is slightly different from the actual playback duration reported by Foobar2000. The difference is usually very small (milliseconds), but when these values are summed to generate timestamps for large playlists (100+ tracks), the error accumulates and can become several seconds.

For example:

Everything: Length = ...
Foobar2000: Length = ...

The Foobar2000 value matches the actual decoded audio duration, while the value shown by Everything appears to be rounded or calculated differently.

This makes the Length column unsuitable for applications that require precise cumulative timing, such as generating chapter markers or SRT subtitle timestamps.
void
Developer
Posts: 20041
Joined: Fri Oct 16, 2009 11:31 pm

Re: Incorrect "Length" value for audio files causes cumulative timing errors

Post by void »

Everything shows the floor of the length. It doesn't round up the length.
I believe Foobar rounds the length up.

To change Everything to round up lengths (round half up):
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    duration
  • Select: duration_round_half_up
  • Set the value to: true
  • Click OK.
To set Everything to show full resolution lengths:
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    duration
  • Select: duration_format
  • Set the value to:
    d:hh:mm:ss.SSSSSSS
  • Click OK.
duration_format
Debugger
Posts: 726
Joined: Thu Jan 26, 2017 11:56 am

Re: Incorrect "Length" value for audio files causes cumulative timing errors

Post by Debugger »

void wrote: Fri Jul 03, 2026 2:10 am Everything shows the floor of the length. It doesn't round up the length.
I believe Foobar rounds the length up.

To change Everything to round up lengths (round half up):
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    duration
  • Select: duration_round_half_up
  • Set the value to: true
  • Click OK.
To set Everything to show full resolution lengths:
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    duration
  • Select: duration_format
  • Set the value to:
    d:hh:mm:ss.SSSSSSS
  • Click OK.
duration_format

No, that didn't change anything; it still shows an error. After accumulating the times of all WAV files, more than 1 minute is missing (for a total of 145 tracks).
The error for some files is +1/0 second (normally, without error, 0).
The more files, the greater the accumulated time error (e.g., 1 minute missing).


Eberything doesn't show milliseconds, only "000"

I wrote a generator that creates times with milliseconds.

1
00:00:00,000 --> 00:04:12,747
Track 1

2
00:04:12,747 --> 00:04:27,134
Track 2

3
00:04:27,134 --> 00:07:16,014
Track 3
void
Developer
Posts: 20041
Joined: Fri Oct 16, 2009 11:31 pm

Re: Incorrect "Length" value for audio files causes cumulative timing errors

Post by void »

Everything doesn't show milliseconds, only "000"
Everything uses the system property handler to gather lengths from WAV files.
Please check if you have a third party property handler installed that only returns seconds.



Try using the Everything property handler:
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    property
  • Select: property_builtin_handler_priority
  • Set the value to: 1
  • Click OK.
In Everything, press F5.
Do the WAV files show milliseconds now?
Debugger
Posts: 726
Joined: Thu Jan 26, 2017 11:56 am

Re: Incorrect "Length" value for audio files causes cumulative timing errors

Post by Debugger »

void wrote: Fri Jul 03, 2026 11:05 pm
Everything doesn't show milliseconds, only "000"
Everything uses the system property handler to gather lengths from WAV files.
Please check if you have a third party property handler installed that only returns seconds.



Try using the Everything property handler:
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    property
  • Select: property_builtin_handler_priority
  • Set the value to: 1
  • Click OK.
In Everything, press F5.
Do the WAV files show milliseconds now?
Yes. Now the milliseconds are showing. Thanks for your help. God bless you.