![]() I did try Plex, but on my kit it was horrendously slow and did not do a good job reading the metadata tags, which therefore rendered it useless for me as I am not about to re-tag about 9000 files, that work perfectly in Twonky! I have left one of my QNAP NAS devices with Twonky 8.2, as it works fine for mp3 files, and I like to split the libraries between the two.Īssuming that this is for your Intel based 453 Pro the link is: Media Device Type makes no difference, files still appear on Samsung TV as unsupported format under Twonky 8.2. to "Generic Media Receiver" or "-/-", which both means there's no MimeTypeMapping done there. Try to find your Samsung TV listed there and make sure it's the correct IP that is shown for the device. You'll find a device list of detected devices when you scroll down. Now navigate to the third position on the left below "Settings" (I only have the German language menu, it is below "Status" and "Setup"). Open the Twonky Server starting page and go to the settings. Make sure you know the IP adress of your Samsung TV. You can try to change the detected renderer and investigate if that helps. ![]() So probably, some of the actions defined change the way the stream is sent to your TV, and so iaffects if it is playable or not. The result is that if you have a lot of mp4 video files and a Samsung TV, I would recommend sticking with Twonkymedia 8.1.1 and ignoring the update notification message you will continually receive in the App Centre on the QNAP. I know that Twonky has a history of problems with mp4 files, though I have personally never had a problem in the past. The conclusion is that something is broken in Twonkymedia 8.2, but what it is I do not know. All files then stream correctly with no errors on the Samsung TV. I then removed Twonkymedia 8.2 and installed 8.1.1. All files then streamed without error on the Samsung TV using the QNAP DLNA server. This took forever, but eventually completed. I turned on the native DLNA app on the QNAP and told it where to scan the files to build the library. I could still stream everything using Twonkymedia 8.2 on other devices, the problem was solely on the Samsung TV. There had been a firmware update on the Samsung TV and I at first thought that this was the problem. I discovered the problem (eventually!) by isolating which end the problem was occurring. The saving in file sizes by using H.264 is marginal. ![]() I use "old fashioned" MPEG4 as it is supported by some of the older devices we have that do not support H.264. Files encoded with H.264 are not affected.Īs I have hundreds of files in my library, built up over many years, I did not want to recode the files or use transcoding. The crazy thing is that not all files are affected, it seems to be to do with the exact encoder used for the video stream, (e.g Level 1,2 etc.). The files involved are all mp4 files encoded with MPEG4 for video and AAC for sound. The symptom is that files that use to play no longer play and you get a message on the TV "cannot play file type" or similar. Twonkymedia v8.2 causes a problem streaming to a Samsung TV (in my case a UEH6400). In case someone else suffers the same frustration I am posting this info:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |