Windows can't read FLAC tags

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

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

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.

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.

Tim De Baets said:

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 :-(

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?

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.

Tim De Baets said:

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!