Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-306

Picard should consistently use the same method for duration calculation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Normal Normal
    • None
    • None
    • Data Submission
    • None

      Currently Picard uses the fpcalc-calculated duration for AcoustID submission. It should either use its own for submission, or use the fpcalc-calculated one for lookup as well.

      A few files at http://keiichianimeforever.com/music/Onegai-Twins/Complete-OST-_-Photograph are calculated differently by Picard vs. fpcalc: #218, 221, 228.

      Presumably this is due to a corrupted file; fpcalc says:
      [mp3 @ 0x24f6800] incomplete frame

      However, this means that Picard cannot look up those files even though if you use the values from fpcalc in the acoustID API they lookup fine: http://goo.gl/MhFZU

            Unassigned Unassigned
            hawke Alex Mauer
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package