some flac files "unable to determine BPM"

Richard's Avatar

Richard

28 Dec, 2018 08:07 AM

Hello Hendrik,

I have 7 new tracks where beaTunes said "Unable to determine BPM for track 'x'. You might want to change your settings or try another BPM algorithm.

These are 7 tracks from 2 CDs I just ripped myself in flac format. The other 13 tracks got a BPM. There is nothing obviously different about the 13 tracks that did compared to the 7 that didn't.

These are privately issued CDs (a distant relative's band, recorded in a small professional studio, and pressed by an unnamed company that does that sort of thing), but I don't think that should make a difference, since beaTunes is getting my flac rip of the audio CDs. I will attach one of the problem files.

I got the error messages, so I'm reporting them. I tried selecting them manually to analyze, same result. I don't think this is a case like the other one I had earlier where one channel was the negative waveform of the other channel.

Low priority.

  1. Support Staff 1 Posted by hendrik on 29 Dec, 2018 12:41 PM

    hendrik's Avatar

    Hey Richard,

    I have tied, but cannot reproduce the issue with the file you sent. Should this happen again, please repeat analysis for the files in question, and if reproducible, send log files. Perhaps something else was wrong and the error message misleading.

    Cheers,

    -hendrik

  2. 2 Posted by Richard on 29 Dec, 2018 02:20 PM

    Richard's Avatar

    Once again, it appears that an issue I thought was BPM, isn't. I checked the file I sent you and it didn't receive a fingerprint, either. So it appears to be another Analysis issue, not a BPM calculation issue. I apologize for that. If I could change the title of this thread to "Some tracks fail to analyze", I would.

    Following your message from earlier this morning...
    I closed and reopened beaTunes.
    I "Got Info" on the track I sent you, and that's how I realized it never got a fingerprint.
    I selected the 7 "problem" tracks.
    I Analyzed as before (get fingerprint, and derive BPM).
    I got the same 7 error messages on BPM.
    The 1 track still doesn't have BPM or a fingerprint, according to Get Info.
    I uploaded my logs to you.

    I screen capped along the way and have attached these screen caps to this message. The file names of the screen caps indicate (by date/time) the sequence.

  3. Support Staff 3 Posted by hendrik on 02 Jan, 2019 07:15 PM

    hendrik's Avatar

    Hey Richard,

    Thanks for the logs. In there it says that the file is identified as

    FLAC (.flac) file, byte length: 0, data format: PCM_SIGNED 48000.0 Hz, 16 bit, stereo, 4 bytes/frame, little-endian, frame length: 45753647 (MFAudioFileFormat)
    

    This is wrong, as the file is 44100 Hz and 32 bit.

    The MFAudioFileFormat means, that beaTunes identified the file using Window Media Foundation. What puzzles me is the fact that out of the box Windows Media Foundation does not support FLAC. See https://docs.microsoft.com/en-us/windows/desktop/medfound/supported...

    There is way for third parties to write plugins to extend the list of supported formats—and there is at least one plugin available to help Windows Media Player support FLAC (https://sourceforge.net/projects/mfflac/). Any such plugin would also affect Windows Media Foundation and in turn beaTunes.

    Any chance your Windows Media Player plays FLAC and you have such a plugin installed?

    Cheers,

    -hendrik

  4. 4 Posted by Richard on 02 Jan, 2019 07:37 PM

    Richard's Avatar

    Well, on these particular CDs, I used EAC to rip them to .wav files, then used MediaMonkey to convert them to FLAC, and then deleted the wav's. Usually, I use EAC to just rip and convert to mp3 in one go, but this time I wanted flac so I did the other process. (And it is the flac files that I then added to beaTunes' library.) What is notable is that I ripped the entire CD in one go, and then converted the group of wav files in one go (repeating for the 2nd CD), meaning that all the files were handled the same - the ones that ultimately "worked" in Analysis and the ones that didn't. Maybe MediaMonkey is somehow bunging things up.

    I don't intentionally have a plug-in installed. If MediaMonkey incorporates one on their own, I don't know about that.

    Maybe I should re-analyze the group of files that "worked" and send you the logs again? That way it can be established if the identification of the files is different for the "good" vs the "bad" group. In fact, I'll just re-analyze them all again. There's only 20 in total. I'll add the "analyze key" item, too, so that I can see for sure which tracks got analyzed anew.

    I'll do that now.

    Update- The tunes that "worked" before also now have a Key added, as expected. The "bad" 7 tracks remain un-analyzed or un-updated.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Wednesday, January 2, 2019 1:16 PM
     Subject: Re: some flac files "unable to determine BPM" [Problems #49132]
       
     #yiv1472899459 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv1472899459 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  5. Support Staff 5 Posted by hendrik on 02 Jan, 2019 07:38 PM

    hendrik's Avatar

    The issue has nothing to do with ripping.
    It's purely a playback issue (or read issue).

    In Windows Media Player, can you play FLAC files?

  6. 6 Posted by Richard on 02 Jan, 2019 09:23 PM

    Richard's Avatar

    I mentioned the ripping process because that's how the files got created and "identified". I thought it might be relevant.
    I chose one of the "bad" files ("01. Your Love Is Like a Flower.flac") and played it in WMP, no problem. I virtually never use WMP and so have never modified it, added a plug-in, or anything like that. Looking at WMP "Options", Plug-ins tab, I see that the only plug-ins are 3 that have to do with Visualization, which I imagine came with WMP.

    My version of WMP should be up-to-date for Windows 8.1. It says File Version 12.0.9600.19145. I had to go to wmplayer.exe "properties" to find that out.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Wednesday, January 2, 2019 1:38 PM
     Subject: Re: some flac files "unable to determine BPM" [Problems #49132]
       
     #yiv2658592519 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv2658592519 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  7. Support Staff 7 Posted by hendrik on 03 Jan, 2019 07:15 AM

    hendrik's Avatar

    I mentioned the ripping process because that's how the files got created and "identified". I thought it might be relevant.

    That came across the wrong way. It's definitely good that you mentioned it!

    I chose one of the "bad" files ("01. Your Love Is Like a Flower.flac") and played it in WMP, no problem.

    WMP cannot play FLAC files, unless you have some plugin installed. Th plugin in question would not be a WMP plugin, but a so-called "Media Foundation Transform". There is no super easy way to see them, but an engineer from Microsoft wrote a little tool that does it. At the bottom of https://blogs.msdn.microsoft.com/matthew_van_eerde/2010/05/03/how-t... there is a link to mftenum.zip. Please download that file, extract it. There is a x86 version and a amd64 version, since you are on 64bit (right?) you want the amd64 version. Simply run the appropriate mftenum.exe file in a command shell and paste the output into a message. I'm curious whether something unusual shows up!

    Thanks,

    -hendrik

  8. 8 Posted by Richard on 03 Jan, 2019 07:27 AM

    Richard's Avatar

    Here is the output:
    -- Audio decoders ({9EA73FB4-EF7A-4559-8D5D-719D8F0426C7}) --
    Microsoft Dolby Digital Plus Decoder MFT ({177C0AFE-900B-48D4-9E4C-57ADD250B3D4})
    WMAudio Decoder MFT ({2EEB4ADF-4578-4D10-BCA7-BB955F56320A})
    Microsoft AAC Audio Decoder MFT ({32D186A7-218F-4C75-8876-DD77273A8999})
    A-law Wrapper MFT ({36CB6E0C-78C1-42B2-9943-846262F31786})
    GSM ACM Wrapper MFT ({4A76B469-7B66-4DD4-BA2D-DDF244C766DC})
    WMAPro over S/PDIF MFT ({5210F8E4-B0BB-47C3-A8D9-7B2282CC79ED})
    Microsoft MPEG Audio Decoder MFT ({70707B39-B2CA-4015-ABEA-F8447D22D88B})
    WMSpeech Decoder DMO ({874131CB-4ECC-443B-8948-746B89595D20})
    G711 Wrapper MFT ({92B66080-5E2D-449E-90C4-C41F268E5514})
    IMA ADPCM ACM Wrapper MFT ({A16E1BFF-A80D-48AD-AECD-A35C005685FE})
    MP3 Decoder MFT ({BBEEA841-0A63-4F52-A7AB-A9B3A84ED38A})
    ADPCM ACM Wrapper MFT ({CA34FE0A-5722-43AD-AF23-05F7650257DD})

    -- Audio effects ({11064C48-3648-4ED0-932E-05CE8AC811B7}) --
    AEC ({745057C7-F353-4F2D-A7EE-58434477730E})
    Resampler MFT ({F447B69E-1884-4A7E-8055-346F74D6EDB3})

    -- Audio encoders ({91C64BD0-F91E-4D8C-9276-DB248279D975}) --
    MP3 Encoder ACM Wrapper MFT ({11103421-354C-4CCA-A7A3-1AFF9A5B6701})
    WM Speech Encoder DMO ({1F1F4E1A-2252-4063-84BB-EEE75F8856D5})
    Microsoft MPEG-2 Audio Encoder MFT ({46A4DD5C-73F8-4304-94DF-308F760974F4})
    WMAudio Encoder MFT ({70F598E9-F4AB-495A-99E2-A7C4D3D89ABF})
    Microsoft AAC Audio Encoder MFT ({93AF0C51-2275-45D2-A35B-F2BA21CAED00})
    Microsoft Dolby Digital Encoder MFT ({AC3315C9-F481-45D7-826C-0B406C1F64B8})

    -- Demultiplexers ({A8700A7A-939B-44C5-99D7-76226B23B3F1}) --
    No IMFTransforms found.

    -- Multiplexers ({059C561E-05AE-4B61-B69D-55B61EE54A7B}) --
    Microsoft MPEG2 Multiplexer MFT ({AB300F71-01AB-46D2-AB6C-64906CB03258})

    -- Miscellaneous ({90175D57-B7EA-4901-AEB3-933A8747756F}) --
    Microsoft H264 Video Remux (MPEG2TSToMP4) MFT ({05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5})

    -- Video decoders ({D6C02D4B-6833-45B4-971A-05A4B04BAB91}) --
    Intel® Hardware M-JPEG Decoder MFT ({00C69F81-0524-48C0-A353-4DD9D54F9A6E})
    Intel® Hardware VP9 Sync Decoder MFT ({07AB4BD2-1979-4FCD-A697-DF9AD15B34FE})
    Intel® Hardware VP9 Decoder MFT ({0C69E30B-A112-4A86-B496-35120CD745D5})
    Microsoft MPEG Video Decoder MFT ({2D709E52-123F-49B5-9CBC-9AF5CDE28FB9})
    DV Decoder MFT ({404A6DE5-D4D6-4260-9BC7-5A6CBD882432})
    Intel® Hardware VP8 Sync Decoder MFT ({451E3CB7-2622-4BA5-8E1D-44B3C41D0924})
    Mpeg4s Decoder MFT ({5686A0D9-FE39-409F-9DFF-3FDBC849F9F5})
    Microsoft H264 Video Decoder MFT ({62CE7E72-4C71-4D20-B15D-452831A87D9D})
    Intel® Hardware VP8 Decoder MFT ({6D856398-834E-4A89-8EE5-071BB3F58BE4})
    WMV Screen decoder MFT ({7BAFB3B1-D8F4-4279-9253-27DA423108DE})
    WMVideo Decoder MFT ({82D353DF-90BD-4382-8BC2-3F6192B76E34})
    MJPEG Decoder MFT ({CB17E772-E1CC-4633-8450-5617AF577905})
    Mpeg43 Decoder MFT ({CBA9E78B-49A3-49EA-93D4-6BCBA8C4DE07})
    Mpeg4 Decoder MFT ({F371728A-6052-4D47-827C-D039335DFE0A})

    -- Video effects ({12E17C21-532C-4A6E-8A1C-40825A736397}) --
    Frame Rate Converter ({01F36CE2-0907-4D8B-979D-F151BE91C883})
    Resizer MFT ({1EA1EA14-48F4-4054-AD1A-E8AEE10AC805})
    VideoStabilization MFT ({51571744-7FE4-4FF2-A498-2DC34FF74F1B})
    Color Control ({798059F0-89CA-4160-B325-AEB48EFE4F9A})
    Color Converter MFT ({98230571-0087-4204-B020-3282538E57D3})

    -- Video encoders ({F79EAC7D-E545-4387-BDEE-D647D7BDE42A}) --
    Intel® Quick Sync Video H.264 Encoder MFT ({4BE8D3C0-0515-4A37-AD55-E4BAE19AF471})
    H264 Encoder MFT ({6CA50344-051A-4DED-9779-A43305165E35})
    WMVideo8 Encoder MFT ({7E320092-596A-41B2-BBEB-175D10504EB6})
    WMVideo9 Encoder MFT ({D23B90D0-144F-46BD-841D-59E4EB19DC59})
    Microsoft MPEG-2 Video Encoder MFT ({E6335F02-80B7-4DC4-ADFA-DFE7210D20D5})

    -- Video processors ({302EA3FC-AA5F-47F9-9F7A-C2188BB16302}) --
    Microsoft Video Processor MFT ({88753B26-5B24-49BD-B2E7-0C445C78C982})

    -- KS data compressors ({1E84C900-7E70-11D0-A5D6-28DB04C10000}) --
    No IMFTransforms found.

    -- KS data decompressors ({2721AE20-7E70-11D0-A5D6-28DB04C10000}) --
    No IMFTransforms found.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Thursday, January 3, 2019 1:15 AM
     Subject: Re: some flac files "unable to determine BPM" [Problems #49132]
       
     #yiv1835221067 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv1835221067 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  9. Support Staff 9 Posted by hendrik on 03 Jan, 2019 08:17 AM

    hendrik's Avatar

    Hm. Thanks for trying this. Nothing sticks out to me. :-/

    Anyhow.

    To get to a solution, please

    • shut down beaTunes
    • go to its installation directory (probably C:\Program Files\beaTunes5)
    • open folder lib
    • rename mfsampledsp-0.9.10-x86_64.dll to mfsampledsp-0.9.10-x86_64.dll__defunc
    • start beaTunes again
    • analyze those files again

    Better?

    All the above does is disabling the Media Foundation based code. Instead beaTunes will use FFMPEG. This may lead to issues with mp3. To re-enable the Media Foundation based code, just rename the file back to its original name.

  10. 10 Posted by Richard on 03 Jan, 2019 03:06 PM

    Richard's Avatar

    That worked.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Thursday, January 3, 2019 2:17 AM
     Subject: Re: some flac files "unable to determine BPM" [Problems #49132]
       
     #yiv5241453742 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv5241453742 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  11. Support Staff 11 Posted by hendrik on 04 Jan, 2019 06:52 AM

    hendrik's Avatar

    That worked.

    Good.
    Not ideal, but good.

  12. 12 Posted by Richard on 09 Jan, 2019 11:01 PM

    Richard's Avatar

    I thought this would be a closed thread, but the very next CD I've ripped had a similar (but not identical) problem. This one is a regular commercial CD ("Gutterflower" by the Goo Goo Dolls). I ripped it to FLAC using MediaMonkey. I Synchronized and then Analyzed in beaTunes. All but 2 of the tunes Analyzed properly (i.e., did the Analysis modules I requested: Fingerprint, BPM, and Lyrics [although it didn't find lyrics for 6 of the 12 tracks... but that's not relevant to this post).

    On the 2 tracks it didn't do, I got the same "Unable to determine BPM for track 'x' ..." message as before. I then turned around and manually re-selected the 2 tracks that didn't analyze, this time adding "key" just so I could more easily see if anything was happening. This time, one of the two tracks was partially successful (which I wasn't expecting), adding the fingerprint and key, but not the BPM. The other one still didn't analyze at all. I'm going to attach the one that's still a baddie if I can (it's 24 MB), and I'll send the logs.

    I'm using an app called MediaInfo that tells me the track is 1078 kb/s, 44.1 kHz, 16 bit, 2 channel FLAC. You said the problem with the prior files is that they were identified as 48 kHz, which is not supported. So, this one appears not to be that.

    Update: The attachment appears to be successful.

    Now I am doing the dll rename you had me do earlier & trying both "bad" tracks again.

    Next update: That worked for both tracks.

    So, I'm not sure what is going on. A single commercial CD that was ripped all at once generated 12 FLAC tracks that beaTunes could analyze 10 of on the first try, another 1 of [partially] on the 2nd try, and the remainder of after I disabled the one DLL. I'm sure this is the sort of thing that could lead you to pull out your hair.

  13. Support Staff 13 Posted by hendrik on 10 Jan, 2019 01:10 PM

    hendrik's Avatar

    You said the problem with the prior files is that they were identified as 48 kHz, which is not supported.

    That was actually not the problem. They were misidentified as 48kHz and then treated as 48 kHz. Treating a 44.1 kHz file as if it were a 48 kHz file leads to data garbage and that's what happened.

    So, I'm not sure what is going on.

    As stated before, for some reason the Media Foundation based component identifies FLAC files (it should not do that) and does it wrong (it definitely should not do that).

    I'd keep the mf... file disabled for now, unless you notice that other things don't work.

  14. 14 Posted by Richard on 10 Jan, 2019 03:36 PM

    Richard's Avatar

    "That was actually not the problem. They were misidentified as 48kHz and then treated as 48 kHz." - I stand corrected.
    So, to restate to make sure I understand, the MF component, which is part of the library beaTunes relies on, for reasons unknown involves itself in files it shouldn't (FLACs) and misidentifies some on an unpredictable basis, leading to the functional failure I experienced. And the workaround, as you stated, is to disable the buggy mf...dll.
    Hendrik, I appreciate all the time you spent diagnosing this problem.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Thursday, January 10, 2019 7:10 AM
     Subject: Re: some flac files "unable to determine BPM" [Problems #49132]
       
     #yiv9071736518 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv9071736518 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  15. Support Staff 15 Posted by hendrik on 10 Jan, 2019 03:51 PM

    hendrik's Avatar

    Hendrik, I appreciate all the time you spent diagnosing this problem.

    No worries.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • 03._Smokey_Mountain_Smoke.flac 10.9 MB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac