| Issue Number | 4231 |
|---|---|
| Summary | MP3Info package gives incorrect runtimes |
| Created | 2017-02-13 10:42:18 |
| Issue Type | Bug |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-08-08 12:06:23 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.202846 |
I have discovered that the Python package we have been using to determine MP3 run lengths does not always return the correct number of seconds. Usually the error is only a second or two, but occasionally it is double the actual length. I have found and tested a replacement (mutagen) which can be installed using the standard pip tool.
Added some watchers. None of the errors currently stored in the repository (at least on DEV) are egregious (that is, more than a second or two).
I have created a CGI page which lets you upload an MP3 file and have the run times reported by the two packages displayed. The larger file (brahms.mp3) has about a 2.5 seconds difference; the shorter example is reported by the older package to be 2 1/2 times longer than by the newer package. In both cases (and in all cases which I have tested) the time reported by the newer (mutagen) package matches what I see in any MP3 player I load the file in. I haven't dug deep enough to find out why the MP3Info package's times don't match the actual times for the MP3s, but I don't see any payoff for doing that digging. I am inclined to swap in the newer package.
~oseipokuw: I have temporarily plugged the newer package into the Audio Import tool. Would you be able to test that tool (on DEV)?
I created a tool to make testing that tool a little less awkward. Instead of you having to create new zipfiles/spreadsheets as if you were Vanessa, this tool lets me do that for you. I've created a test zipfile on DEV.
Sure. Will do.
I didn't see the new file. This is the error message I get. when I attempt to download the file. The file referenced below appears to and older file which has been reviewed already.
An error has occurred
Error: Local File Week_094_Rev2.zip already exists!
Is it possible we're looking at different tools? When I say "Audio import tool" I'm referring to:
CDR Admin > CIAT/OCCM Staff > Audio Import
Which page are you looking at?
I was looking at the Audio Download which is the first step we perform before going to the the Audio import tool. I didn't realize that the file was already downloaded. I was able to import the files:
CDR779687 Added link from this document to Media document
CDR779701
CDR779687 Added link from this document to Media document
CDR779702
CDR779689 Added link from this document to Media document
CDR779695
CDR779689 Added link from this document to Media document
CDR779696
CDR779691 Added link from this document to Media document
CDR779697
CDR779691 Added link from this document to Media document
CDR779698
CDR779693 Added link from this document to Media document
CDR779699
CDR779693 Added link from this document to Media document CDR779700
I checked all the media docs and none of them recorded the run seconds of the files.
Yes, I just noticed that, too. I fixed the problem and generated another test set. Please give it another shot.
Seems to have worked. 2secs was recorded for all of them and when I played the audio it does seem like 2 secs.
Not sure why this didn't get closed, as the replacement library which fixes this problem is in production.
| File Name | Posted | User |
|---|---|---|
| brahms.mp3 | 2017-02-13 13:57:29 | Kline, Bob (NIH/NCI) [C] |
| horn.mp3 | 2017-02-13 13:57:24 | Kline, Bob (NIH/NCI) [C] |
Elapsed: 0:00:00.001321