![]() ![]() The one that I have to access the server on is the first one. Although when I go into the Twonky settings I see two network interfaces. then edit the file transcoding.db ( vi transcoding. This is what it appears to be because my XBoxes can see the QNAP but cannot see any of the movies etc. run this command: cd /share/MD0DATA/.qpkg/TwonkyMedia/resources/. So apparently it can only handle 1 port and not two. So the issue here is that Twonky, unlike every other application, has decided to utilize the 2nd network port for its settings and therefore I could not get to it by going to the IP for the first network port. Then I remember that I have ordered a managed switch so that I can take advantage of port trunking and currently have both of the network adapters plugged into an unmanaged switch with port trunking turned off until such time that the switch comes in and I could just simply plug them in and go. The IP address for this is different than what the IP is for my QNAP. I opened the two config files within /MNT/HDA_ROOT/twonkymedia and wow check this out. hmmmm opened up the twonky directory and looked at the ini file. Did that, no avail however this time instead of waiting 20 seconds to time out, the page immediately came up cannot be found. I read another issue with another guy where the QNAP admins had him update the firmware again. When I went into the administrators control panel, the link was which is perfect because I access everything via the hostname not the IP. Is there a way to see what port it is running on? The log file recreated itself. I am going to try to delete the file within putty and then see if that works.Īny other ideas with Twonky if the above fails? (Deleting it failed too) Did the port somehow magically change? Maybe it is running but the port has changed. I refreshed the directory after renaming the file and it game me the same error above with the new name. Is there a way to page the results so that they don't give me 5000 of them at once such as the windows command dir /p to get the same results? When I do a ipkg list command it shows all the packages that are available however I can only scroll up to the T section and it doesn't hold any more than that. I did a ipkg update twonky command and it ran and then terminated but still no avail. I re-enabled the services and to no avail. Twonky Server v8.2.1 and higher no longer contain the Twonky Thumbnail Utility (TTU) tool and does not support extracting thumbnails from video content. It successfully renamed but alas did not fix the issue. IMPORTANT: The Twonky Server Interface and Settings are not supported by WD Technical Support. I opened putty and navigated to the same directory and copied and pasted the command you provided. Unexpected directory listing line '-rw-r-r- 1 admin administ485419471 May 29 07:30 twonkymediaserver-log.txt'. I navigated to the directory and an error came up about the log file stating that it was basically corrupted and had problems and it would not display in WinSCP. I've got it running and can connect to the Twonky server from client computers. I figured I would just rename it in WinSCP since I was there anywhere. mlevin77 wrote:I want to share content via DLNA from the Twonky server on my QNAP box. My directory was empty so I went to WinSCP into the root and did a find files search for *twonky* with the wild cards and found the correct directory the file was located in. I then utilized putty to go to the directory that you stated yours was in. I disabled the Upnp Service in the administration control panel. There definitely was something wrong with my log file. Re-encode to a TS container, do NOT change the encoding of the video, COPY the video stream. The #video: DLNA Mandatory section should look something like this (Twonky Media Server also allows you to add new formats): you will see there a line for the MP4 format, duplicate it on a new line and change the MP4 to MKV (except for “video/mp4”, leave that as it is). ![]() then edit the file transcoding.db ( vi transcoding.db).run this command: cd /share/MD0_DATA/.qpkg/TwonkyMedia/resources/.ssh ( putty) to your media server machine (QNAP NAS in this case).However, if you happened to have install Twonky Media Server 7 (7.09 at the time I’m writing this), then you need to do things just a bit differently. By default, it uses Twonky Media Server 6 and for this version you should look at this tutorial. Or almost.įor this tutorial I am using a QNAP NAS TS-412. Well, that’s simply because Twonky Media Server isn’t transcoding MKV by default and if the player also doesn’t know the format then you’re stuck. So, you are using Twonky Media Server to stream content to devices on your network? Then you might have noticed that devices that don’t natively play MKV format can’t access those files. ![]()
0 Comments
Leave a Reply. |