Year/date value for media file showing as xx-xx-2036 or xx-xx-1902.
Issue: MP4 files incorrectly categorized and wrong year/date value displayed when viewed in DLNA client (in my case Windows Media Player and Roku Media Player). And I find that quality varies widely… But then, as stated, I’m mildly obsessive, and insist on my own track naming format, developed over the last twenty years… Orcrone is already using MediaMonkey, which provides similar metadata manipulation tools to those of mp3tag.Īny tagging tool that uses metadata databases is reliant on the accuracy of the metadata databases.
I am using the free software mp3tag if the ripper itself is not doing this. So the obsessive need is met, but in a different way… Now all my 62k+ track filenames are post-processed or newly ripped to prefix filename with leading-zero track number, and the metadata is cleaned to remove track number from track title, and remove the leading zeroes as presented in the metadata. But, having realised that media tools such as MediaMonkey allow you to parse filenames to split them into different metadata fields (track #, artist, track title, etc), I realised that it was the most effective way of ensuring cross-platform track ordering. My initial reaction on having to a) prefix a track number to the filename and b) prefix with a leading zero track number was negative I’m mildly obsessive about these things, and didn’t want to ‘corrupt’ my carefully entered filenames (I even got upset when MM modified the file dates when changing metadata tags, because some media players sort by file date I now realise that was silly…). In order for the alphanumeric sort to work correctly for track numbers higher than 9, you need to force leading zeroes (most alphanumeric sorts will give an order 1, 10, 11 … 19, 2, 20, 21, etc). My experience of a number of different media players over the years is that, provided you have a filename that can be sorted correctly alphanumerically, most media players can be made to present tracks by filename in the correct track order. Different DLNA clients present the data provided by these views in different ways.
Twonky provides a number of different views, based on different metadata tags, and the physical filenames (‘By Folder’). Will add a leading-zero, two-digit track number prefix to all filenames, and will create appropriate folders if necessary. You give the auto-organise tool a string to define the structure you want, and it will go off an process all the tracks you have selected, e.g. I’d recommend you to prefix tracks with a leading-zero track number you can always remove this from the track name metadata (again, using the powerful input filename parsing of MediaMonkey). Provided your metadata is correct, you can get it to re-organise your music into sensible folder structure, and prefix each track with a track number. I’d take the last option MediaMonkey has a very useful ‘Auto-Organise’ function, that will move files using the metadata. Iii) get MediaMonkey to rename the files. I) muck about with the ‘views’ Twonky provides (see the fourth post in this thread) I just want mycloud’s default dlna twonky server to at least recognize the dsd files so that my blu-ray player might pay them via dlna instead of direct smb. I don’t need transcoding as my oppo player reads the dsd files just fine. So you’re saying that the version of twonky on the mycloud should be able to support dsd files? But for some reason it does not. share/MD0_DATA/.qpkg/TwonkyMedia/resourcesįeel free to report the results of any experiments you do. I’m guessing the directory mentioned in a couple of the links:
How can I get Twonky to provide full size artwork to media-playing clients? I had posted some comments on customising the Receiver Type, but never tried it myself: I’d never found the Twonky release notes before… My devices run v7.2.9, so they may support DSD. Iii) Twonky apparently added DSD support in v7.2.7. Ii) the ‘Media Receiver Type’ value has an associated setting file that may be modified. I) Twonky supports transcoding (at least on QNAP devices) There are three points of interest that I found reported: So I had a bit of a Google, and found some interesting stuff that I might investigate a bit further. I’ve never really played with the media types, because I’ve never had an issue with any of my DLNA clients all the media formats I use seem to be supported.