11/19/2023 0 Comments Remove twonky server qnap![]() 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 |