You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our MPEG frame detection algorithm is picking up some false positives which will cause inaccuracies in the calculation of song duration, etc. The false positives are easily identified in the raw output, but the algorithm needs a way to identify them. Researching source code across the web has revealed a method I've been contemplating which involves reading a few MPEG frames from several points in the file (at 25%, 50%, 75%, etc) for quickly calculating average bitrate and song duration without having to read every MPEG frame (slow).
The text was updated successfully, but these errors were encountered:
Currently our MPEG frame detection algorithm is picking up some false positives which will cause inaccuracies in the calculation of song duration, etc. The false positives are easily identified in the raw output, but the algorithm needs a way to identify them. Researching source code across the web has revealed a method I've been contemplating which involves reading a few MPEG frames from several points in the file (at 25%, 50%, 75%, etc) for quickly calculating average bitrate and song duration without having to read every MPEG frame (slow).
The text was updated successfully, but these errors were encountered: