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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |