1 thing I could not solve by now. My twonky is showing all music album covers under Photos - this makes no sense for me. I want my personal pictures under Photos - nothing else.
Is there a way to exclude certain folders from the scan for Photos?
The same problem could come up when I copy Audiobooks on the WD MyCloud - they should not be displayed under Music.
When you use the Twonky UI to tell it where to look for media (in the ‘Sharing’ page), use the ‘media type’ selector to tell it what types of media to look for in each share.
See Q. Where should I put my media so Twonky finds it?
Then you will need to make the changes to stop MyCloud breaking your Twonky settings each time it reboots.
In addition to what cpt_paranoia posted one can specify certain folders for Twonky to ignore when it performs a content scan. See Advanced → Ignore Directories. One may have to use SSH to get the proper folder/substring name. See Q. Can I stop Twonky searching in certain folders in my media storage folders? for more information
I’d like to use the twonky dlna server to stream dsd (dsf) files to my oppo player. Unfortunately, it looks like WD’s implementation of twonky doesn’t suppor these files. I know there’s a way to add file type support in some versions of twonky. Is there any way to do it for the mycloud? I know I can just login to the mycloud via smb to play these files, but I like using the dlna server for everything.
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.
So I had a bit of a Google, and found some interesting stuff that I might investigate a bit further. There are three points of interest that I found reported:
i) Twonky supports transcoding (at least on QNAP devices)
ii) the ‘Media Receiver Type’ value has an associated setting file that may be modified.
iii) Twonky apparently added DSD support in v7.2.7. My devices run v7.2.9, so they may support DSD.
i) Twonky supports transcoding (at least on QNAP devices)
Yes apparently, with some tweaking, transcoding is possible. Whether the processor on the WD My Cloud is capable of doing so effectively at run time is another story. In the “/usr/local/twonkymedia-7/resources” folder is a file called “transcoding.html” which explains how to setup transcoding on Twonky. From that file:
The new transcoding architecture is able to use nearly any external program for transcoding, rescaling or resampling. Examples of such external programs are: vlc, ffmpeg, mplayer, mencoder, imagemagick and others. In principal each program which is able to transform file x to file y can be used.
It includes this graphic that explains how the transcoding is done:
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.
So I had a bit of a Google, and found some interesting stuff that I might investigate a bit further. There are three points of interest that I found reported:
i) Twonky supports transcoding (at least on QNAP devices)
ii) the ‘Media Receiver Type’ value has an associated setting file that may be modified.
iii) Twonky apparently added DSD support in v7.2.7. My devices run v7.2.9, so they may support DSD.
I had posted some comments on customising the Receiver Type, but never tried it myself:
Q. How can I get Twonky to provide full size artwork to media-playing clients?
I’m guessing the directory mentioned in a couple of the links:
/share/MD0_DATA/.qpkg/TwonkyMedia/resources
will be
/usr/local/twonkymedia-7/resources
on the MyCloud.
Feel free to report the results of any experiments you do.
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. I don’t need transcoding as my oppo player reads the dsd files just fine. 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.
So you’re saying that the version of twonky on the mycloud should be able to support dsd files?
I’m only repeating what can be read in the Twonky release notes; I don’t work for Packet Video or WD.
Did you look at the links I posted? They contain suggestions as to how you might proceed, by editing the receiver type definition files. I don’t have an Oppo player, or a blu-ray player or any DSD files, so I can’t do your experiments for you.
I’l check them out, but it looks like the version of twonky on my mycloud is only 7.2.3 (I’m on the old firmware). Does the latest mycloud firmware upgrade twonky to 7.2.9. Or did you custom install twonky on your drive?
For anyone interested it appears there is now an option (don’t recall it there previously) on the Twonky page with Twonky version: 7.2.9-6 in the WD My Cloud firmware v04.04.00-303 that was released yesterday (or today) that includes a new page called “Online Services”.
From that page: “These settings provide the ability to link your online services to this Twonky Server. Linking enables you to browse and beam your YouTube™, Facebook®, Flickr, or Picasa Web content via this Twonky Server on the local network. You can also login to Twonky to configure those services and select or change which feeds will be available through Twonky Server.”
DLNA is a protocol for distributing media within a local network. So unless you have a local copy of the photos, then, no, Twonky cannot find or serve them.
I had forgotten the ‘Online Services’ feature added with the latest firmware… I have no need to use it so I haven’t bothered to investigate. I can’t see any mention of OneDrive, but you could have a play and report how you get on.
I thought Bennor in his previous post was saying it can access the content on google picasa, facebook etc? Those are no more local than OneDrive.
Yeah I commented on that setting being added to a recent firmware update a while back. Haven’t used it though. Below is a screen capture of that Twonky setting page.
DLNA is a protocol for distributing media within a local network. So unless you have a local copy of the photos, then, no, Twonky cannot find or serve them.
So, does this mean a remote user cannot access nor even see what’s stored, locally? And, do local users see everything & everyone’s streamable content? Please elaborate.
So, does this mean a remote user cannot access nor even see what’s stored, locally?
In the context of this thread (DLNA media server):
A remote DLNA client cannot access the DLNA media server (since, as far as I am aware, DLNA does not support the concept of a remote client).
There are applications that create proxy servers for particular media players. For instance, BubbleUPnP has a BubbleUPnP Server which acts as a local DLNA client, but also acts as a server for a remote BubbleUPnP client, and allows remote media streaming from the DLNA media server.
Nazar78 has very kindly built BubbleUPnP Server than can be installed on the MyCloud:
In the wider context, you can use the WD apps to gain access remotely. These don’t use DLNA, though.
And, do local users see everything & everyone’s streamable content?
DLNA does not respect access controls (that’s a DLNA specification issue, not a Twonky or WD issue), so, yes, if you enable media serving on a share, any local DLNA client will be able to access it.
Thanks CPT for a great thread. One problem I run into is the playback order of songs. They’re presented in alphabetical order rather than track order on the CD. I know I can rip all the music, appending the track number to the front of the song title. Is there anyway to fix this without having to do that?
I have Media Monkey on my PC and songs play in the proper order with MM
i) muck about with the ‘views’ Twonky provides (see the fourth post in this thread)
ii) re-rip, forcing a track number
iii) get MediaMonkey to rename the files.
I’d take the last option; MediaMonkey has a very useful ‘Auto-Organise’ function, that will move files using the metadata. 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 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).
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.
