ini files both contain an “ignoredir” environment variable setting. I have an extra directory in /Public that I want kept out of the DLNA scan. ini precursor files: twonkyserver-default.ini and. In /usr/local/twonkymedia-7 the twonky executable files live. This probably will not survive an upgrade, but there are many other frustrating ways for the. I have a suggestion for twonkyserver.ini. Obviously with the media server firmware being two years old it doesn’t have the latest capabilities and fixes of the latest Twonky firmware. There is also the issue of what appears to be poor integration between the My Cloud OS and Twonky that appears to cause certain issues. Where people typically run into problems is with the Media Receivers not listing their device properly or their device not properly displaying media content served up by Twonky. The Twonky media server on the My Cloud (using Twonky media server firmware that is two years old now) generally works for most as a very basic media server provided one doesn’t look for advanced features. Often the phone support people don’t know what the developers are doing to the firmware or know the details of the firmware or the many complains about a product in the user to user product support forums such as this one. Often they are reading from a prepared script of answers to common questions and issues. The problem with calling WD Support, really almost any large tech company’s phone support, is the phone support people often don’t know the full details about the product they are supporting. One can peruse the Twonky support forum to see specific posts about Twonky: One can see more information in the Twonky Release Notes: It appears the version in the latest v4.x firmware is 7.2.9 which was released late 2014. What I assume is happening is WD paid for a certain license (several year old) and hasn’t paid for the newest/latest licensed version of Twonky. And is up to 8.2.1 which was released on February 8, 2016. In any event Twonky server is up to version 8.2 released last November. Update: believe it or not after hours with Support I figured out that Twonky has discontinued myTwonky some time ago (more than three years now). Support promised to call me back, but didn’t support promised to escalate to next service level but didn’t and keep on going to say: “You will see that on the link you provided are the steps to access the Twonky user interface, but the option to enable 3rd party services is not available.” Good by WD My Cloud? Plus the “Online Services” function is activated by default. You can by default configuration aggregate all media files in your network to WD My Cloud, index and stream them or decide to duplicate them into WD My Cloud. The next level of support declined that this function is available because WD My Cloud is running as a DLNA server only. You’ll be able to do this by accessing the unit’s dashboard, clicking on Media and turning the DLNA server on.” Well, thanks! That is what is done by default and is not the question. The first answer from WD support was: “We would recommend that you Turn On the Twonky Media feature. Unfortunately I have to say that it looks like they have no idea about their own product. After hours with WD Support (not really a support).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |