Home → Problems →

"Failed to decode"

• Edit

Richard

06 May, 2019 05:31 AM

Hello Hendrik,

I added some new files to my big library, did the analysis only to fill the BPM field. Out of 380 new files (roughly), it failed to decode 84 of them. The message on all but one of them is "Failed to decode track 'track name' (UnsupportedAudioFile: MP3, Failed to decode audio frame. (Invalid data found when processing input))."

Some of the problem files (maybe all of them) were downloaded, so there could well be a problem with them. They play OK, and they were downloaded from two different sources, both of which I have used before without issue.

I'm attaching two of the problem tracks, and I uploaded my log files. (I might have uploaded them twice. If so, sorry about that.)

If you could take a look at them, that would be much appreciated. If not, no problem, and no rush on my part. I have not had much time to spend with my music collection recently.

I'm on Win 8.1, and beaTunes 5.1.13.

As always, thank you.

Richard

PS- It would be a nice feature if we could copy/paste or export the error message list so we could keep a record of what tracks failed analysis. If that is an option, I can't find it.

• 21._You_Can't_Be_True__Version_Two_.mp3 5.52 MB
• 14._A_Precious_Little_Thing_Called_Love.mp3 4.27 MB

1. Support Staff 1 Posted by hendrik on 06 May, 2019 07:00 AM

   

   This is probably related to http://help.beatunes.com/discussions/problems/50479-beatunes-failin... (decoding mp3 issues on Windows, new in 5.1.13 due to preferring FFmpeg as mp3 decoder).

   The two samples that you sent contain APE tags at the end of the files. Is that true for all the failing files?

   Workaround: You can work around this issue either by downgrading back to 5.1.12 (https://www.beatunes.com/download/beaTunes-5-1-13-x64.exe) or by disabling the FFmpeg-based decoder. Disabling the decoder can be achieved by renaming or deleting the corresponding DLL in the beaTunes installation directory (a .dll file containing the string ffsampled in its name).

   • Edit

2. 2 Posted by Richard on 06 May, 2019 06:42 PM

   

   Yes, it appears that all the files have APE tags. I didn't realize there was already a thread on this.
   Update: I used mp3tag to remove the APE tags from 1 of the tracks, resynchronized in beaTunes (this might not have been necessary), and then reanalyzed the 1 track, and it processed just fine.
   Then I renamed the ffsampled dll to have a non-dll extension and tried to analyze a different, previously failed track. It didn't do anything, no error message, no nothing. Then I decided maybe I needed to close and reopen beaTunes since the dll "went away" while beaTunes was running. So I did that and tried again. This time, the analysis was successful.
   So, in conclusion, the workaround works. I wish there was a batch way to get rid of whatever APE tags are in my mp3 files. I'd never heard of APE tags until this exchange.
   Thanks for your help.

       On Monday, May 6, 2019, 2:00:58 AM CDT, hendrik <[email blocked]> wrote:

   |

   • Edit

3. Support Staff 3 Posted by hendrik on 08 May, 2019 12:57 PM

   

   Then I renamed the ffsampled dll to have a non-dll extension and tried to analyze a different, previously failed track. It didn't do anything, no error message, no nothing. Then I decided maybe I needed to close and reopen beaTunes since the dll "went away" while beaTunes was running.

   Correct, you need to restart for such a change to take effect.

   So, in conclusion, the workaround works. I wish there was a batch way to get rid of whatever APE tags are in my mp3 files. I'd never heard of APE tags until this exchange. Thanks for your help.

   The real solution is for FFmpeg to not stumble over APE tags. It might does that already in a newer release—I have to check.

   • Edit