Wealso verified the WD My Cloud specifications and unfortunately it may not work with Twonky 8. We are currently working on it to find a solution. It is usually provided in a form of a firmware update.
Hi there,
An official Firmware upgrade mostly improve or fix only Basic functionality of the Operating System Kernel. Twonky is a 3rd Party Software. 3rd Party Software only will be upgraded, if this is absolutely necessary for the kernel function - so nearly never!
Changeing / adding autostart sequences or CRON Jobs inside of the Firmware kernel is not really recommended for People without really good Linux experience and knowledge of Linux os start behavior. Only a Little mistake can make your NAS useless!
Yesterday I wanted to create a new user. This has still worked. But all functions for sharing and assigning rights no longer worked.
Also different admin functions no longer run. Cloud settings and device names can not be changed anymore.
After the installation of the original firmware everything works again normal.
The exact cause I can not determine.
Whether the other v2.xx.xx devices is synonymous so, I do not know.
So, after a whole day of testing and analyzing, I can report the following:
It looks like the base GPL package already has a bug. If the package is composed (strictly according to instructions from WD) and nothing of the 3rd party modules are modified, exactly the same happens.
After uploading the firmware to the device works a lot no more. It runs the twonky as desired, but many other functions are dead.
Not really a plugin but close enough Had to try it out. Install is really for Fedora and most of the guides I found for installing on Debian were for version 6. Here is what I did to get it working (haven't tried transcoding yet and still playing).
I agree with your likes and dislikes. I would add to the likes the fact you can view by date. This shows me items recently added and most likely to wathc. I would add to the dislikes that transcoding is not easy to configure (haven't done it yet). I don't understand why they don't have an Ubuntu/Debian installer.
I agree. My past experience with transcoding has been bad. I tried twonky in the past running under WinXP Quad core and the clients struggled to stream the movies because the server could not keep up...and these were only DVD VOB files..i.e. Standard Definition. So for me Trancoding is a non-flyer on my HP-N40L microserver which has low-spec AMD dual-cores. There's no way they can transcode HD on the fly AND stream simultaneously. May be the new s/w is a bit more efficient...may try it.
Please also keep in mind that above manual prepared for x86 architecture as my system runs on OMV 2.2.5 i386 due to lack of powerful hardware. So if need x64 architecture, please download media server and library file in first step accordingly.
Sorry, I can't offer anything. I do use a DLNA server (Serviio), but don't run it on a NAS. Odds are if the Twonky channel was removed from the Channel Store, then Twonky has decided to stop supporting it.
I have no idea if there's any other DLNA server product that can be run from a WDMyCloud NAS device. Serviio has versions for QNAP and Synology, but I have no idea if either might work on your device.
I finally spoke with a senior tech at WD today. He intimated the problem could be on their end. He has initiated a review. I still have not heard anything from Twonky. I sent screen snaps in the am to Twonky in response to a suggestion they made last night. I was mistaken that Twonky is not on the WD App Store. If does not appear as a choice in the WD dashboard if you have it installed. If deleted it will once again appear as a choice. The WD tech walked me through that as well to check if deleting and reinstalling had any merit.
I am also having trouble with the Twonky app on a WD Ex2 with OS5. After installing the app from the WD app store and selecting my Roku device the app prompted me to install the Twonky channel on the Roku, the Roku responded and installed the channel, all my content in the shared folders I set up is available on the Twonky app via my computer but when I click on the Twonky Channel on my Roku I get the message: Channel not available: twonky is no longer available, you may want to remove the channel from the home screen.
The Twonky app itself is in fact no longer supported on the roku. You have to configure the app on the WdMycloud ex2. I can walk you through what I did. It is stable for now. Let me know. In the end you will be using the roku media server app to access your content from the ex2.
Thank you, I will have to play with that tomorrow. I'm currently wired to my desktop using an HDMI cord and steam through my computer. I really want to eliminate that "middle man" and I'm not crazy about Plex. Is there something special I need to input into the Twonky app to have it direct to the Roku Media Server app?
Do you have the Twonky app installed on your ex2 ? To do that go to your dashboard. Then to Apps. you see the Apps choice across the top. There are many apps to can install. Choose Twonky and install it. The next step is to configure Twonky. Once you have installed it it will appear on the left as installed. Click on the twonky server button then choose to configure. The configure choice is right above the run button. The choice will open the configure widow. Then go to shared folders on the left. Navigate over to create this .....Your home drive needs to be where you navigate.
Thanks, great info and it should help others coming behind me. I had it all set up, the app actually prompted me to install the Twonky Channel as I set it up initially only to have Roku tell me it's a dead channel afterwards. I did delete the app but will reinstall it now that you have said the Roku Media Server works with Twonky.
It sounds like Twonky will work as a DLNA server, in addition to their dedicated app. Plex will do this as well, and I believe Emby also does. DLNA servers are visible automatically using Roku Media Player. It won't have as nice a user interface as the Plex or Emby dedicated channels, but should work just as well for media playback.
I have never figured out how to use Plex as a DNLA server. I do know it is possible. There have been problems between Twonky and WD that seem to have come wtih firmware updates. The techs at WD are quickly learning. WD has an ios app which makes it very easy to reach my drive on all my mac devices. I believe the Roku has enough of a user base the make that a possibility for the Roku as well. I do know that twonky was used as WD's built in DNLA software prior to going to WD os5.
I was trying to set up a Twonky Server on Ubuntu. The server works fine, but I could not get systemd to autostart the server (using a service file I created at /etc/systemd/system/twonkyserver.service). Sometimes I got the cryptic error message that some PID-file (/var/run/mediaserver.pid) is not accessible, the exit code of the service is 13, which apparently is a EACCES Permission denied error . The service runs as root.
As described above, the below service file auto-starts the Twonky Server on boot. Simply create it using vim /etc/systemd/system/twonkyserver.service. This assumses that you have installed the Twonky Server to usr/local/twonky. The shell-file twonky.sh already provides a nice interface to the service file (twonky.sh startstopreloadrestart, also see twonky.sh -h).
You need to be sure the paths in the ExecStart command match where you unpacked twonky, and also where you want the .pid file, configuration, logfile and runtime appdataunless you are happy with their default locations.
I pulled down the file and put it on the flash, but where is the "go script"? I see one in /var/tmp and another in /var/log, I don't see one specifically on the flash drive when I look at it through windows.
Start at the beginning. I tried telnet and moving the flash back to my PC. No such path. Via telnet, those obviously don't make sense because the slashes are the wrong way, so I don't think you mean that to be a Unix path. From windows, I get "directory not found" when going through a webbrowser and my flash's directly has a config file, but there do not seem to be any hidden files in there.
Hmmm. Interesting, I go back to my zipped file of the unraid software and I find files in the config file there that are not on my flash (go, disk.cfg, ident.cfg, license, network.cfg, and share.cfg) . Strange, since my Unraid is working just fine.
Is there a trial license period on the Linux version of Twonkyvision? I tried to play around with the windows version but due to other commitments I ended up running out of time before I ever got it working.
Pondering this since the 360 now plays DIVX and XVID, anyone using it and any issue with memory etc? 360 still will not play MKV or DVD but it might be interesting to play with. Is swap needed? Running a gig of memory but my music collection is over 100Gigs and my DVD collection is quite large too, concerned what will occur if it tries to index...
I use it with pics, music and movies and the 360 connects flawlessly. The music and pics index very quickly, better than it did when connected to my media pc. I have only vob's for music and use a dlink dms 520 to stream, not the 360 for movies. Hope that helps some.
Heh, well in the meantime my XBOX 360 went toes up and I've built XBMC on Linux well enough to use instead. Still mght liek a UPNP server for other devices in the house but it's back burner now for sure :-(
Any updates on whether this fixed the problems you were seeing? I'm thinking of trying Twonky 4.4.5 on my unRAID 4.3.1 Pro box to serve files to my PS3 and just wanted to see how straight forward this would be.
I finally go this somewhat up and running. My pPS3 sees the server and I can see my movie folders. But I can't seem to see any of the files in the folders. How does one configure Twonky to see the video_ts files to start a movie. I can't find any documentation that explains any of this and I checked the twonky site.
 3a8082e126