MusicIP Analysis in Windows 7 failing

[kllngtme]

Anyone have any other ideas? I agree on it seeming like a permissions issue but I can't figure it out for the life of me. If I transfer the same flac file to the computer with MusicIP on it, it will fingerprint it fine. Once it's back on my NAS though - nope...

I dunno...

[Wirrunna]

Have you got FLAC installed in C:\Program Files (x86)\FLAC\flac.exe ?
I read through the thread and this is the only thing I can think of that we didn't explore.

As I understand the MIP process, MIP converts tracks to .wav format in ram for analysis, though a browse at C:\Program Files (x86)\MusicIP\MusicIP Mixer shows "bassflac.dll" which presumably reads the flac files.

[kllngtme]

I didn't have it there originally. I added it there but it's still giving me the same thing. I have since deleted it.

I've gone over all my permissions many times. The only way I can fingerprint a FLAC it seems is if it resides locally on the same machine as MusicIP. Right now, I'm at a loss to fingerprint all this music. I can't move this much music to my computer just to fingerprint and move back, it's over a TB of data.

[kllngtme]

I've gotten no where with this. I can't figure it out. I've tried everything just about other than formatting my computer. haha I don't think I'll get musicIP going this way. There's no way I'm transferring over a TB of flac just to transfer back to my NAS after it does fingerprinting..

If anyone found a work around, let me know.

[bakker_be]

I've gotten no where with this. I can't figure it out. I've tried everything just about other than formatting my computer. haha I don't think I'll get musicIP going this way. There's no way I'm transferring over a TB of flac just to transfer back to my NAS after it does fingerprinting..

If anyone found a work around, let me know.

Do you have write access on the flac location from your Win7 PC?

[bleepblorp]

I've gotten no where with this. I can't figure it out. I've tried everything just about other than formatting my computer. haha I don't think I'll get musicIP going this way. There's no way I'm transferring over a TB of flac just to transfer back to my NAS after it does fingerprinting..

If anyone found a work around, let me know.

I have the same problem. .mp3 converts fine when stored on NAS, but .flac does not. I'm strangely glad I am not alone, but not sure how to fix this.

[kllngtme]

I have the same problem. .mp3 converts fine when stored on NAS, but .flac does not. I'm strangely glad I am not alone, but not sure how to fix this.

It's driving me nuts! I don't get it at all and have no solution either to get it to work.

[IsaSim]

I've gotten no where with this. I can't figure it out. I've tried everything just about other than formatting my computer. haha I don't think I'll get musicIP going this way. There's no way I'm transferring over a TB of flac just to transfer back to my NAS after it does fingerprinting..

If anyone found a work around, let me know.

I have a similar issue. Coming from a Windows 7 Home edition desktop, updated to Windows 10 three days before the free upgrade deadline (no problem with MusicIP analysis then), and updated to Anniversary Windows 10 (1607) at the end of September. Now, MusicIp won’t analyze WMA Lossless 9.2, the format I always used from several years back, using dBpoweramp Music Converter. It will analyze FLAC, though, and I verified that wav was also analyzed. This really doesn’t make me happy, since I postponed Windows 10 precisely with the fear some legacy programs I love would stop working…

From MusicIP log, I get “Fingerprint failed (mis-execution)”. I checked what would happen to WMA songs already analyzed in my collection, and got “Analysis failed (error analyzing)” from the log, and “Unanalyzable” status from MusicIP.

After googling the issue, I tried installing GenPUID, which gave back “genpuid.exe is not recognized as an internal or external command”. Further googling led me to explore PATH, where I got past the first roadblock, and now what appears is “missing required component mipcore” (which is there).

I tried analyzing folders on the same drive where MusicIP is installed: nothing works either. I also ran MusicIP in compatibility mode without success.

I’m not fluent with the inner works of computing, so I don’t know really where to go from here. I hope this will help someone more qualified to solve this mystery!

[conquerist]

I'm just chiming in here in case anyone else is still having this problem (googling for "MusicIP Mixer", "unanalyzable", and "flac" quickly leads here).
The problem I was having is very similar to what's described earlier in the thread (some flac files fail to analyze, mp3 files and wav files work fine).

Doing either of the following fixed it for me.

1. Renaming the files from .flac to .fla or
2. Setting the registry setting HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\W in95TruncatedExtensions to the value 1 and updating the extension portion of the 8.3 filenames of the affected .flac files to .FLA (see below for a batch script)

What's happening is that when analysis is started on a file, the MusicIP Mixer GUI launches a process called mipcore.exe and refers to the file to be analyzed by its 8.3 filename. The 8.3 filename is a second filename that files (can) possess in addition to their normal (long) filename (more info on wikipedia). This 8.3 filename is created whenever a file is created, renamed or copied, and for a .flac file, the extension portion of its 8.3 filename can bei either .FLA or .FL~, depending on Windows version and registry setting at the time that the 8.3 filename is created. Now, for whatever reason, on files with .FL~ in their 8.3 filename, MusicIP analysis fails. And Windows 7 just so happens to, by default, have the registry setting above set to 0, which leads to 8.3 filenames with .FL~ being created, which in turn causes the problem that's the topic of this thread.

Luckily, the extension part of the 8.3 filename can be changed to .FLA to fix the problem.

One way of doing this is to change the normal/long filename to the .fla extension, because this automatically also leads to the creation of a new 8.3 filename with the extension .FLA. However, this is a bit of a work-around, because .flac is still the generally used extension and using .fla (with the lower case extension referring to the normal/long filename) comes with its own set of restrictions, e.g. most programs/ripping tools create .flac files that need to be renamed manually, downloaded files likewise, and some programs don't even recognize .fla as FLAC files.

The second way preserves the .flac extension in the long filename, it only involves modification of the 8.3 filename. Changing the registry setting above (see here) leads Windows to use .FLA instead of .FL~ when creating a new 8.3 filename for a .flac file. However, this alone doesn't change anything on existing files.

To "fix" the existing .flac files, the extension portion of their 8.3 filenames needs to be set to .FLA, and an easy way to do that is to place the following batch script into the music root directory as fix_8dot3.bat and executing it with the necessary privileges (e.g. right click -> run as administrator). The script iterates over all .flac files in the directory in which the script is located (including subdirectories) and changes the extension portion of their 8.3 filename to .FLA. This strictly speaking works independently of the registry setting above, however without having Win95TruncatedExtensions set to "1", new files will continue to be created with .FL~ and on these analysis will fail until their 8.3 file extension is changed to .FLA, e.g. by running the batch script again.

for /r %%A in (*.flac) do (
	fsutil file setshortname "%%~A" %%~snA.FLA
)

Personally, I used the second method (registry and batch script), because it fixes the problem for files for files that already exist as well as those that are created after performing the fix, all while retaining a .flac extension. However, the first method doesn't require modifying the registry or executing a batch file from the internet.

I hope this helps anyone who's still having this problem. Why "still"? As a follow-up, Windows 10 seems to default back to the pre-Windows 7 behavior concerning .FLA and .FL~, so this thread is especially relevant for Windows 7, or more precisely, for .flac files that were either created on a Windows 7 machine and not touched afterwards by a non-affected OS as well as for files that have been renamed or copied in Windows 7.

[Wirrunna]

conquerist
Thank you for your post. Excellent explanation.
Oh, and welcome to the forum.