FLAC Song Length Rounding Up One Second

[Saltshaker]

Here there folks,
Is there a way to prevent MP3Tag from rounding up the song length to the next second? Not sure if this is some kind of padding issue or not. But I just noticed this while generating total play times on my files and it is throwing off my totals completely.
However this does not happen with all of my FLAC files, just some of them and the original wav files have the correct times.
When loading/playing the "incorrect" FLACs they do have the correct time displayed. Its just in MP3tag that is doing it. Windows shows the files with the correct times so I assume this is the app doing it based on the bit length. Im running the latest versions of everything and I know this may have been possibly discussed before but hopefully someone can either shed some light to this and how to correct it? Thanks in advance

[ohrenkino]

See this thread on rounding length:

SUGGESTION: Count the lengths of files with accordance to reality

I made a simple experiment concerning the way Mp3tag adds lengths of files I created a WAV file that was 44 Hz stereo 16-bit. And I made difference version of it on account of its lenght. And then multiplied it and loaded to Mp3tag. The results were A] 1.000 seconds long file x 60 = 60 seconds in Mp3tag B] 1.001 seconds long file x 60 = 60 seconds in Mp3tag C] 1.499 seconds long file x 60 = 120 seconds in Mp3tag D] 1.501 seconds long file x 60 = 120 seconds in Mp3tag This might seem un…

It looks as though different programs handle different formats differently.
Es.p this finding:

@vilsen

For the nearly 3-second files, FLAC and mp3 (cbr & vbr) formats were rounded off upwards but the wav files were rounded off downwards in Mp3tag. In Foobar though, all file formats were rounded off upwards.

[Saltshaker]

Thanks for the reply. Based on your prior post, it appears that the problem is recognized but there is no solution to it in the app?
Is there a way for a new column to be created with the millisecond of the track length rounded down through a formula or calculation?

Either way, it wouldnt be the end of the world for me since what I only really care about is how it is exported. I export all the track names and times into a text so that it can be pasted into an info file. I use this custom export...is there a way to adjust this so it calculates correctly? Thanks.

$filename(Tracklist.txt,utf-8)
'Total Time - '%_total_time2%

$loop(%track%)$num(%track%,2)) %title% - $div(%_length_seconds%,60):$num($mod(%_length_seconds%,60),2)
$loopend()

[ohrenkino]

@Saltshaker

$div(%_length_seconds%,60):$num($mod(%_length_seconds%,60),2)

This could be shortened to %_length%.

As there is no way in MP3tag to get the split seconds in a track, you would have to take what the built-in functions offer you.

[Saltshaker]

Thanks for the reply but I need seconds in my info files so Im hoping I can figure something out.

[ohrenkino]

@Saltshaker

but I need seconds in my info files

I am not sure about the "but" as this is the output with both methods for a file that has the length of 11 minutes and 18 seconds:

So I would still say that the longer expression could shortened ...

[ohrenkino]

@Saltshaker

so I assume this is the app doing it based on the bit length

I think that usually programs display the data from the header.
And as the WAV files had to be converted somehow, it could well be that the converter wrote something correspondingly into the header.
You could install Foobar and check how many samples you find in each file - and to how many seconds and milliseconds that sums up.
If both file types show the same information in the header, then perhaps something should be done ...

[Saltshaker]

So yeah I actually do have Foobar installed and did a quick comparison. I take two files and they match just as others do. Same samples and time with milliseconds. The WAV and FLAC file have 21.973 but is seen as 22 seconds only in FLAC files.
Foobar rounds up and sees both files as 22 seconds,
But MP3tag sees WAVs correctly at 21 seconds and rounds up after 500 milliseconds for FLAC files only.
Windows and Winamp see the FLAC files at 21 seconds but there is a difference with the two in MP3tag which throws my numbers off when calculating totals for info files. I need it to be true and not round up to the nearest second after 500+ milliseconds for any file.

[ohrenkino]

AFAI can see the length is 21.973 secods.
So MP3tag tells you the are 0.027 seconds more to listen to than there actually are.
And WIndows and Winamp tell you that the track will end 0.973 seconds earlier that it actually does.
Comparing 0.027 and 0.973, I would say that Winamp and Windows are more than 36 times more inaccurate than MP3tag is.
And unarguably, none of these programs shows the exact length.

Anyway: it stays as it is: you will get only the seconds but not the splitseonds with the export function.

It would be interesting to see whether the totals are really off so much. I would assume that there are just as many files where the length got rounded up as there are with rounded down lengths. So on average the display would be right.
Good luck with the search for a program that meets your requirements.

[Saltshaker]

Thanks for your reply and feedback, I really do appreciate it. At the end of the day, this probably is not a big deal to many folks here and to be honest it is not a deal breaker for me from using the program. I have tried a few others but so far this is the best one out of the bunch. Its probably the easiest to use.
My totals for various exported setlists may be off by 10 seconds on average so it is what it is. I just found it confusing that MP3tag treats FLAC files differently than WAV files and hoped that maybe there would be a solution or setting that could help with this variance.
Either way, I will work with it as is. Thanks for your time!