gottogo99 Posted February 19, 2011 Share Posted February 19, 2011 Hello, I was recently testing ImgBurn with different audio file types. I noticed that the FILE-DECODED-SIZE is incorrect for m4a and mp3 files, and it differs depending on the DirectShow filter used. First, using DSP Worx for FLAC, m4a, and ogg, only FLAC and ogg have the correct length of 04:02:47. M4a is 04:02:51 and mp3 is 04:02:53: TITLE "Get Yer Ya-Ya's Out!" PERFORMER "The Rolling Stones" FILE "01. Jumpin' Jack Flash.flac" FLAC REM FILE-DECODED-SIZE 04:02:47 TRACK 01 AUDIO TITLE "Jumpin' Jack Flash" PERFORMER "The Rolling Stones" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.m4a" M4A REM FILE-DECODED-SIZE 04:02:51 TRACK 02 AUDIO TITLE "01. Jumpin' Jack Flash" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.mp3" MP3 REM FILE-DECODED-SIZE 04:02:53 TRACK 03 AUDIO TITLE "Jumpin' Jack Flash" PERFORMER "The Rolling Stones" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.ogg" OGG REM FILE-DECODED-SIZE 04:02:47 TRACK 04 AUDIO TITLE "Jumpin' Jack Flash" PERFORMER "The Rolling Stones" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.wav" WAVE REM FILE-DECODED-SIZE 04:02:47 TRACK 05 AUDIO TITLE "01. Jumpin' Jack Flash" INDEX 01 00:00:00 Next, using madFLAC for FLAC, Orban for m4a, and no ogg. Now m4a and mp3 are both incorrect at 04:02:53 instead of the correct 04:02:47 for the other file types. TITLE "Get Yer Ya-Ya's Out!" PERFORMER "The Rolling Stones" FILE "01. Jumpin' Jack Flash.flac" FLAC REM FILE-DECODED-SIZE 04:02:47 TRACK 01 AUDIO TITLE "Jumpin' Jack Flash" PERFORMER "The Rolling Stones" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.m4a" M4A REM FILE-DECODED-SIZE 04:02:53 TRACK 02 AUDIO TITLE "01. Jumpin' Jack Flash" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.mp3" MP3 REM FILE-DECODED-SIZE 04:02:53 TRACK 03 AUDIO TITLE "Jumpin' Jack Flash" PERFORMER "The Rolling Stones" INDEX 01 00:00:00 FILE "01. Jumpin' Jack Flash.wav" WAVE REM FILE-DECODED-SIZE 04:02:47 TRACK 04 AUDIO TITLE "01. Jumpin' Jack Flash" INDEX 01 00:00:00 Not sure if the incorrect sizes are an ImgBurn bug, or a limitation of the DirectShow filters or the audio format itself. Whatever the case, the FILE-DECODED-SIZEs are wrong. PC is Windows 7, 32 bit, fully updated, ImgBurn 2.5.5.0. Thanks for your time. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 19, 2011 Share Posted February 19, 2011 It represents the exact amount of data that comes out of the directshow filter - and therefore nothing to do with ImgBurn. Lossless formats should decode to the same length as the original (fingers crossed anyway!), other formats could vary depending on the implementation within the DS filter. Link to comment Share on other sites More sharing options...
gottogo99 Posted February 19, 2011 Author Share Posted February 19, 2011 It represents the exact amount of data that comes out of the directshow filter - and therefore nothing to do with ImgBurn. Lossless formats should decode to the same length as the original (fingers crossed anyway!), other formats could vary depending on the implementation within the DS filter. Fair enough. Any suggestions as to DS filters which give correct lengths for mp3 or m4a? So far, Orban and DSP Worx have failed for m4a and whatever Windows 7 uses has failed for mp3. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 19, 2011 Share Posted February 19, 2011 Nope, sorry. Don't use a lossy format if you can't handle an extra frame or two on the output. Remember there are 75 in a second so there's no way you'd actually notice during playback. Link to comment Share on other sites More sharing options...
Recommended Posts