Menu

#31 Track duration incorrect

open
None
5
2002-09-24
2002-09-19
Anonymous
No

Refresh CD shows proper track duration in application
window, but file ouput shows a much shorter track
duration (about 33% of the actual track duration).

Discussion

  • Anonymous

    Anonymous - 2002-09-24

    Logged In: YES
    user_id=624

    That means that either the entire file was not successfully
    ripped, or that the track length is being incorrectly reported in
    the viewer. What output format (MP3, OGG, WAV) was
    being used? In the case of a WAV file, the file length is
    written to the WAV header, and should be correct.

     
  • Anonymous

    Anonymous - 2002-09-24
    • assigned_to: nobody --> akey
     
  • Veronica

    Veronica - 2004-05-01

    Logged In: YES
    user_id=156789

    I've had problems with truncated files when encoding to MP3,
    but running the same encoded as OGG the files come out full
    length. I havn't done any extensive testing on this but it
    is present in v0.24 running under w2k.

     
  • mrpotes

    mrpotes - 2004-12-13

    Logged In: YES
    user_id=1177231

    I'm also getting a similar problem encoding to MP3. The
    track viewer is reporting the length of the tracks
    correctly, but when the mp3s are opened in winamp, the
    number of seconds listed in the mpeg properties is rarely
    the length of the mp3.

     
  • Veronica

    Veronica - 2004-12-22

    Logged In: YES
    user_id=156789

    This problem occurs when output is mp3, with output as ogg
    there is no problem. I'm not sure if it's incorrect track
    info or problem with ripping the entire track, all I know is
    that when the track is played back it only plays the actual
    time that is presented in the file. So for a person like me
    that really don't know anything about mp3-format it looks
    like the entire track is not getting ripped properly.

     
  • Nobody/Anonymous

    Logged In: NO

    The track length is reported incorrectly however tracks
    play back correctly.
    This only happens when encoding in VBR mode. I have
    tried the same track at 192kbs and the time is reported
    correctly without VBR

     

Log in to post a comment.

MongoDB Logo MongoDB