Some reason, the media server is showing most of my video files named as “data”. Even though that isn’t what they are named. They all have the proper name in the title metadata. Some of the files show their proper names. Any ideas on how to fix them to show the proper names.
Hello,
You can try a rebuild or rescan.
Check page 103 for more information.
http://www.wdc.com/wdproducts/library/UM/ENG/4779-705103.pdf
I have tried that, didn’t change anything.
I was playing around with one of my videos, and i use Media Monkey to edit the metadata, and it seems the title entered using it doesn’t register. But if i use the windows properties to edit the title metadata it registers. So i think i may have figured it out.
Hello,
Happy to know you have found the solution. Thank you for sharing.
I was playing around with one of my videos, and i use Media Monkey to edit the metadata, and it seems the title entered using it doesn’t register.
That’s odd, becuase in my experience, MediaMonkey is very good at editing metadata. Admittedly, my experience is limited to audio.
When you used Windows properties, did the MM-entered title appear, or was it incorrect? Just trying to determine if it’s Twonky being fussy about the metadata format that MM creates, or whether all apps have difficulty reading it.
Yes, the metadata set using Media Monkey shows when viewing with Windows properties. Music and Tv Shows are fine with the metadata filled with Media Monkey, for some odd reason it is only movie files. Which was what was throwing me off.
That’s weird, as I don’t see any distinction in media type between TV shows and Films; they’re both video. What file format are they in? If they’re different, it may be the file or container format that is the differentiator in behaviour.
The fact that Windows is able to see the metadata written by MM suggests that the fault lies with Twonky not being able to read what is correctly-formatted metadata. It may just be some feature of the order or manner in which MM writes metadata to the file, and Windows attribute editor writes it differently.
One for VentisMedia, perhaps? They’re pretty good at responding to bug reports/queries, IME.
There is something wrong with either how Twonky parses the “title” metadata or with how Media Monkey writes the “title” metadata. Just tried changing the metadata with Media Monkey on a single movie file (MP4) and it caused Twonky to incorrectly display the movie title (it displayed it as “data”). Not sure where Twonkey is pulling the word “data” from as it doesn’t show up when viewing the file properties with either Media Monkey or with Windows.
I’ve had problems in the past where certain metadata is not visible and causes Twonky to incorrectly parse the media file. It was parsing a video file and displaying it as an audio file. No metadata was visible with Windows.
My files are also MP4
Bumping this thread a bit to add a bit more information for those using MediaMonkey to tag video files, in particular MP4 video files.
Played around with the free version MediaMonkey a bit more and there is something, intermittently at times, wrong with how that program codes the “title” and “comment” metadata tags when it comes to video files, specificly MP4 video files. I spent some time tagging roughly 20 video files with MediaMonkey. At first every single one of them while actually displaying a title in; MediaMonkey, MP3Tag, and when viewing the file properties with Windows Explorer. When the MP4 file is stored on the WD My Cloud and accessed via the Twonky DLNA media server, both Windows Media Player on a Windows 7 x64 PC, and the Roku Media Player on a Roku 2XS would show the word “data” rather than the video title.
If I tried renaming the file with MediaMonkey sometimes the change would take and the “title” would be shown correctly by the DNLA clients, other times not. One work around for this MediaMonkey “title” tagging error if the title is present but not showing properly was; using MP3Tag, to simply select each file and save it without changing any tags. Once that was done all files displayed the “title” tag correctly in both Windows Media Player and Roku Media Player. There are probably other ways to fix this error but using MP3Tag it made the process somewhat quick to fix multiple video MP4 files, one after another or all at once.
While fiddling around with this MediaMonkey “title” tag issue with MP4 video files, I came across another tagging problem with MediaMonky and MP4 video files. After figuring out how to get MediaMonkey to properly add movie data to the “comment” tag when using the “get album art and properties from Amazon for the selected file” option. I noticed that sometimes the “comment” data wouldn’t show up on screen with the DLNA client (in my case the Roku Media Player). It happened both when manually entering in “comment” data and when using the auto tag from Amazon option. It turns out MediaMonkey was, sometimes, saving the “comment” tag data as the “podcastdesc” tag. The work around, there may be others, when this happened was to go video file by video file with MP3Tag and change the “podcastdesc” tag to the “comment” tag using the MP3Tag Extended Tag “Edit Field” option by selecting “comment” from the “Field” drop down/selection box to correct the incorrect tag field name. Examples shown below.
From:
To:
1 Like
