New
#11
That setting is now enabled, does not seem to have an impact. The file is not set at read-only.
That setting is now enabled, does not seem to have an impact. The file is not set at read-only.
Just to be sure, you did try to change the WM/MediaClassPrimaryID tag again (using Tag Editor Plus) after enabling that setting, right?
I have uploaded the command-line tool (mp4xtratags) to directly edit an MPEG-4 file's Xtra tag here: http://bmproductions.fixnum.org/soft...p4xtratags.zip
To simply list all the Xtra tags (including WM/MediaClassPrimaryID) that a file contains:
Code:mp4xtratags <filename>
To write the new value for WM/MediaClassPrimaryID to the file:
Code:mp4xtratags -s "WM/MediaClassPrimaryID" -g "DB9830BD-3AB3-4FAB-8A37-1A995F7FF74B" <filename>
Okay, I read the tag in the file:
Attachment 242493
It has the right info, so previous attempts must have worked already, without impacting date modified of the file? Or it has always been like that. Either way, it remains listed under other media.
What's more, when checking the tag's value via your addon inside WMP, it's shows the same guid as before, {FCF24A76-9A57-4036-990D-E35DD8B244E1}.
So, I think WMP is puttting the files in other media based on something else? And that results in the different GUID for internal purposes?
Either way, I think it's time to retire WMP. The alternative I talked about is working really well.
Thanks for your help!