Solved Windows can't read FLAC tags

[dvnamis]

Bump

Another thank you for the download link, exactly what I needed.
Installed on Win 7 Pro x64

 

[emueyes]

Indeed, this needs to be stickied.

Out of curiosity, anyone know if the file explorer in Windows 8 handles flac tags ?

 

[Tim De Baets]

Out of curiosity, anyone know if the file explorer in Windows 8 handles flac tags ?

Do you mean native support? No, just like in Windows 7, a third-party property handler is still required.

 

[KarlBlomquist]

Yeah! Thank you Tim and Seth! Thanks for the link! I will upload that thing to mediafire, cause it has to last looong.
FLACPH15.rar

Anyone know where this can be found now? A search results in just dead links. Thanks.

 

[Tim De Baets]

Reuploaded the file here.

 

[ydrol]

Another reup on Google Drive

 

[jons]

Is this FLACPH15.rar safe? Will it cause any modification to the flac files or just mods explorer?

 

[mmmelaney]

Yes it's fine. It will not change the files. It just allows you to see the properties (Title, Artist, etc.) in Windows Explorer.

 

[kagemand]

Thank you all so much!
I've been looking for a program like this EVERYWHERE, but this is the only place where this glorios little program had a working download link. I know this post is old, but i needed to display my gratitude

 

[LuzTeTT]

Works for Windows 8 x64, no hassles.

 

[mtcsltd]

Just what I was looking for too. Works a treat.
Thanks.

 

[deepdish7]

the FLAC Property handler actually worked in Windows 8, but not it doesn't work in Windows 10 again.

neither i was able to find a similar fix for ALAC/M4A files for Win8 or Win10.

we only have to pray until someone updates FLAC property handler to work in Win10, and produces similar ALAC/M4A property handler to work in Win8/Win10

 

[Tim De Baets]

Microsoft has added native FLAC support in Windows 10 so you don't need a third-party property handler anymore there.

For M4A tags (including ALAC) there has already been native support since Windows 7. To play ALAC you still need the DC-Bass Source Filter though.

 

[deepdish7]

both are not true.

win10 does not support FLAC tags, neither did Win7 (or Win8, or Win10) support ALAC/M4A tags (to be precise, only certain tags were supported, but not all for ALAC/MP4 and absolutely no tags were supported for FLAC). please see attached screenshot. sorry it's in Russian language, but the language doesn't matter, for English version of OS it's absolutely same. The column names are "year" and "publisher". Both publisher and year tag are filled in for FLAC/M4A files in the folder in question, but neither is displayed for FLAC and only year is displayed for M4A, but publisher tag is not displayed. while they are both shown (as always) for MP3 files.

btw if you google a bit, you'll find out that now everyone has same problem - ppl who used FLAG tag property handler for Win7/Win8 confirm that it doesn't work anymore in Win10/the system doesn't support FLAG tags either

 

[Tim De Baets]

So you're basing the presence of FLAC support on just the Year and Publisher tag? I suggest that you check other tags like Length, Artist and Title. Native FLAC support has been added in Windows 10; that's a fact. If *you* would Google around a bit, you'd quickly find that out yourself.

And yes, certain FLAC tags aren't recognized, but that's because Microsoft's support isn't complete yet. I suggest that you use the feedback tool in Windows 10 to report that.

I'm not going to further comment on M4A as that's off-topic here.

 

[deepdish7]

So you're basing the presence of FLAC support on just the Year and Publisher tag? I suggest that you check other tags like Length, Artist and Title. Native FLAC support has been added in Windows 10; that's a fact. If *you* would Google around a bit, you'd quickly find that out yourself.

And yes, certain FLAC tags aren't recognized, but that's because Microsoft's support isn't complete yet. I suggest that you use the feedback tool in Windows 10 to report that.

I'm not going to further comment on M4A as that's off-topic here.

well what's the use to me that microsoft declares win10 now supports FLAC, where it actually does not? little help. and again, it's not me, but other people complaining too. and, for MP3 these tags work. so if FLAC support is declared, then same fields should work for FLAC too, otherwise there's no logic. And what's the point to display artist and title in the columns on the right, if they are usually a part of filename anyway? there's much more sense to display publisher (label) and release year on the right. if you had a large music library, you'd understand me.

i actually did mention this in the feedback tool. hope Microsoft responds. though not soon probably, as these guys are usually a bit slow, unfortunately :-(

 

[deepdish7]

luckily I just found a solution how to fix this.

first you need to disable the native FLAC support in Windows 10:

FAQ (WMP Tag Plus) - BM-productions

and then you can install the above mentioned FLAC property handler tool, and now it will work!!! VOILA!!!

 

[wahnsinn]

This is great. Flac property handler works on my W7 x64.

One question though:
How would one go about getting custom tags support?

Specifically, I mean tags like "ACCURATERIPCOUNTALLOFFSETS" and "ACCURATERIPTOTAL" (can be added by CUETools to store whether the file is ripped accurately).

I would *think* that once you have the means to display the tag content for regular tags like "album" or whatever, it should be a relatively small step to get the same for <insert your tag name here>, no?

 

[Tim De Baets]

Apologies for the late reply, I was meaning to reply sooner but lost sight of your post.

There's actually a predefined list of properties that Windows supports, it's documented here. While it's possible to define custom properties (explained here), doing so requires work from the developer of the particular Property Handler providing the custom properties. It's unfortunately not possible for individual users to define their own custom properties.

 

[wahnsinn]

Apologies for the late reply, I was meaning to reply sooner but lost sight of your post.

There's actually a predefined list of properties that Windows supports, it's documented here. While it's possible to define custom properties (explained here), doing so requires work from the developer of the particular Property Handler providing the custom properties. It's unfortunately not possible for individual users to define their own custom properties.

Oh, that's going to be beyond me then, too bad. Thank you for the informative response!