wojteva fyllbirt michellah
Margorie Gomoran
Could you try the clean install troubleshooting on one to two of the affected channels? To do this, you remove the channel and then reinstall it. To ensure the process is successful, restart your device before adding the channel back in. We would recommend doing this from the Settings menu by navigating to Settings > System > Power (If you do not see a Power submenu, skip to the next step.) > System restart.
I noticed a remarkable decrease over time in the stability and usability of my 55S535 that I purchased in February of 2021 having v9.4.0. (BTW, I never expected its VA panel to be as awesome as it is! 48 zone local dimming does a really good job, too.)
It began with v10.0 in May 2021 and got worse with v10.5 in November 2021.
But with the arrival of v11.0 in May of this year, I have had to restart my TV more times to date than I've had to do for the entire period of use with v9 & v10. From rock solid to reset-city in about 15 months.
Since I bought the TV, the apps have, or course, received updates though I have not kept track of the versions. But that an update has arrived is evident by subtle or obvious changes in the "look and feel." For example, the latest HBO Max now has posters that expand to about three times their size when selected and then shrinks when you move to the next poster which expands and so on, the "improvement" being the same exact graphic and text, only larger. Over time, for all the apps, the improvements are more visuals and animations that download and render in real time. The Roku app Search, once a nice simple text listing that populated as one "typed" in a search, now populates with graphics and ellipsis truncated text instead. In navigating the Roku home or in an app, I often find myself hitting a cursor key more than once then realizing I was waiting on some visual to render or update.
There is a term for this: bloat. Bloat eats up resources and wrecks havoc on temporary caching where "leaks" occur which fragment memory spaces in RAM as the CPU tries to keep up with the GPU and vice versa. The kind of failures described in this topic ARE leaks, confirmed by the users here of the universal "fix" of a restart which clears/resets the cache with things being OK for a while, then they're not. A hardware problem would persist immediately after a restart.
In my case, the most egregious of the failures occur in Hulu, HBO Max and Disney+. Hulu gets me a full screen of green trash. The other two get me a black screen with forever animated dots and spinning pinwheel immediately after the HDR or Dolby notify. I can back out to the home screen and watch Netflix or YouTube TV and go back to either of the others for a repeat failure to play; network is OK, which is wired Ethernet. All "fixed" only by a restart, every time, all the time. Until they're unfixed again. Netflix and Prime are problematic, but not a bad as the others.
FYI: the Settings > System > Power > System Restart is all that's needed. The "secret hidden menu" or a complete power unplug works, but requires more work to do. With the latter, holding down the power button for 20 seconds will "drain" the RAM without having to wait 10-15 minutes before plugging it back in.
So, as our sets age, accept the restart as a routine. I wonder how much my TCL will suffer when the awaited v11.5 shows up. Or when HBO graphics will spin and pulsate.
As well, I foresee a time when my Roku TV will hardly keep up at all and by that time there should be a far more powerful Roku Ultra-whatever device to stuff into an HDMI port.
Cheers.
I have a Amazon Prime account and loaded both of these apps onto my Roku. Recently when I try to watch content on either of them whatever I choose to watch starts up and then it kicks me out to the home screen EVERY TIME. I have unplugged my system and removed and reloaded by apps onto my home screen without success.
To ensure the process of removing and re-adding the Amazon Prime and Netflix channels is successful, make sure to restart your device before adding the channel back in. from the Settings menu by navigating to Settings > System > System restart > Restart. However, if it still has no dice and the issue is only with the channel alone, this is a good indication that there is likely an issue within that specific channel that will need to be addressed with an update from the channel publisher. Channels on Roku are created and maintained by each channel publisher. In this case, you'll want to reach out to Amazon Prime and Netflix support directly to share your feedback.
Warm Regards,
Lianna
Out of frustration, I unplugged the TV to remove it but thought I would try one more time before discarding the TV. I plugged in the TV again (probably several minutes elapsed) and launched the Netflix app, and this time it successfully played every movie that I launched.
These are all relevant reasons for subtitles, but Netflix has not (yet) implemented a fully working solution for subtitles in its streaming engine. Only a limited selection of movies in the streaming library have closed captioning available within Netflix. And there is no multi-language availability. So if you want to display subtitles in Spanish for one of the Hollywood movies on Netflix, you are out of luck. Or at least so it seems on the surface.
Step 1: Search for an SRT file with subtitles for the movie of your choice from any of the many web sites specializing in subtitles. I personally like to use a web site called PodNapisi. Please note that downloading a file with subtitles is perfectly legal, because the subtitles have been generated by a user (i.e., they are not copyrigthted content). If the web site offers you several choices, download the one that is formatted for a single file and for 25 frames per second (fps).
Step 2: Play the movie in the Netflix player for a little bit and mark the timing (minutes and seconds) for the first few lines of dialogue. This is very important! You will find that many subtitles files that you download from the web are a little off in timing compared to the Netflix movies. This is because the subtitles were meant for a movie that comes from another source (e.g., DVD) and Netflix may have added or deleted a few seconds of video from the beginning of the movie. You will need the information about timing in the next few steps, so make a note of it somewhere.
Step 4: Run Jubler and open the SRT file with the subtitles that you have downloaded. For illustrative purposes in this post, I will be using The Perfect Host movie and Spanish subtitles for that movie, which I found on the PodNapisi web site.
Step 5: A quick look at the first few lines of the subtitles reveals that they are lagging about 1.5 seconds behind the movie as it has been formatted for Netflix. (Remember the timings that I asked you to mark for the first few lines of dialogue in the movie, in Step 2?) You will need to shift the timing a bit. To do that, first select all the lines of the subtitles in Jubler.
Step 9: Jubler does not have DFXP as an option. However, it allows you to export into XML, which is essentially the same as DFXP. From the Format dropdown list, select W3C Timed Text (XML) as your desired output format.
Step 10: Select UTF-8 as the target encoding. This is very important! If you fail to export your subtitles under the UTF-8 encoding, it is highly likely your output file will not be properly read by Netflix.
Note for Mac OS X users: You will have to select Get Info for that file and rename the file from the Get Info window. Simply right-clicking on the file and choosing Rename may not work properly, because that affects only the name of the file, but not the real extension of the file.
Step 13: Now go back to the browser tab where you are running Netflix. Start the movie and pause it when it loads and begins playing. As you are in the Netflix player and the movie is paused, press simultaneously the following combination of keys:
Step 14: Select the second option (Load Custom DFXP File) from the Diagnostics menu. A window will pop up, which will ask you to locate the DFXP file with the subtitles. Go to the location on your hard disk where you saved the DFXP file converted by Jubler (as discussed in Step 11). Select to open that file.
I have been developing custom subtitles for Netflix content for two years. As far as I can tell, support for DFXP custom subs has been disabled by Netflix with the most recent iteration of Silverlight. A lot of work has gone down the drain.
I have enjoyed several movies finally with subtitles thanks to your very detailed instructions. I have not been able to convert subtitles to Friday Night Lights (television series) using the same steps. Though everything looks the same, it does not work. Are television series different?
This may sound like an obvious question, but did you try to fix this problem by logging out of Netflix and restarting the browser? I am asking because I had a similar issue with titles for one movie once. I was tinkering with the titles, trying to sync the copy of the titles I had found on the Web with the actual times on the Netflix version of the movie. Since I had tried loading the dfxp file too many times, at one point I started experiencing exactly the same problems you are describing. I logged out of Netflix, closed the browser (Chrome), then restarted it, logged back into Netflix and the problems had miraculously disappeared.
90f70e40cf