Please see the attached for illustration: [image]

Very strange. If you copy the file to your Desktop folder, does the problem still happen there? (I'm wondering if the full path, path length, or drive type has any connection to the # character being treated specially, which could explain why I'm not seeing the same.)

Strange, indeed, as when I copy a file beginning with a # to the desktop folder, it does exactly the same: no metadata populated for those blank columns shown in the previous screenshot, yet it displays absolutely correctly upon deleting # from the start of the file name.

Would it be possible to make a ProcessMonitor log of what happens when you navigate into the folder? That should show us if it's trying to open the file with a # in the name, and maybe getting blocked by something, or opening the wrong path for some reason. Might also be worth testing what happens…

I've figured it out, thanks. Files needed remuxing because they were missing their headers to allow for the aforementioned columns' metadata to display. As always, thanks for your input and patience :slight_smile:

Glad it's working now! I wonder why the filename mattered there as I'd expect the data to still be missing if the hash was removed.

[image] DMRoss: MediaInfo displays it fine, though. [image] DMRoss: Files needed remuxing Very odd! :hushed:

Indeed—especially as all metadata displayed when removing the # from the beginning of the file name without remuxing. Something within the files must have been off slightly to make it behave so strangely until I decided to try remuxing one file, then all of them after seeing metadata then displayed. …

This gets stranger. Upon updating to the latest beta today (13.0.35), all MKVs beginning with a # do not display the metadata shown by the blank columns in the original screenshot when scanning my video folder on my external drive, despite MediaInfo showing it. Remuxing obviously did not change anyt…

Have you tried disabling the script that's adding the extra columns, in case it's involved? Failing that, a Process Monitor log is probably the best thing to try next.

Metadata still fails to populate in columns with all MKV files beginning with hashes (#) in their titles. Such titles also need to be manually copied in sync mode on a QNAP NAS, as they're ignored for some reason. Not a huge issue if remembering to add them manually, but still some kind of bug becau…

MKVs Beginning with Hash Tags Missing Metadata

Help & Support

lxp February 4, 2025, 2:23pm 21

You can create a list of currently shown columns that can easily be shared with

ClipCopy COLUMNS