9/21/2023 0 Comments Kid3 vs mp3tag![]() I guess the cutting point is 0.445 seconds since the last 5 would round up to 0.45, then 0.5 and then 1 second. I guess Mp3tag will always either show the same length, or 1 second longer because it would round up the milliseconds if it is about 0.5 seconds. I am yet to find a sample that Mp3tag shows a 1kbps larger bitrate than Kid3. mp3tag is the one showing 1kbps more on the bitrate over Kid3 and mp3tag will show 1 second longer on the duration. Quote from: DasFox on 05:47:04 I'll get a difference sometimes of 1kbps on the bitrate between the two. Would using foobar and mp3tag be a better choice for looking at the info, compare to Kid3? I'll get a difference sometimes of 1kbps on the bitrate between the two. Bitrate is consistent between the 2 applications. I double-checked it in foobar2000 because foobar2000 shows the milliseconds. There is a time difference of about 1 second on my MP3s because Kid3 always round down the milliseconds while Mp3tag would round up at about 0.5 sec. ![]() Why not use one more tool, e.g., foobar2000, for confirmation?Īfter changing to TagLib, Kid3 would show correct result. ![]() ![]() So at this point in time I'm not sure if Kd3 is all that accurate or not. Also Kid3 uses libraries id3lib and Taglib to read, and using id3lib isn't giving correct results so I used Taglib instead and it's better, but then Kid3 and mp3tag do show slight differences, like Kid3 might say the bitrate is 210 and mp3taq will say 211 and song durations between the two applications will show differences of a few seconds. Quote from: DasFox on 23:31:46 My bad I didn't have id3v2 checked in the settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |