But this week I discovered that you can browse these addons from your phone and then click to play them on your tv. I was aware that there were remote apps, like the official and the unofficial Yatse. Also, them working well was very depended on the Kodi theme used, and my preferred theme did not support it well. However, for me these addons never quite formed a good alternative, since I just really liked browsing in the app on my phone and then ‘casting’ it to the tv while being able to start and stop on my phone. I already had a unofficial Netflix addon and an addon called Retrospect which features all kinds of regional and national broadcasting, amongst others the Dutch NPO. It has all my media in libraries, but can also run so-called addons, apps for Kodi. For years, even before I had the Chromecast, I’ve had a little media machine running LibreElec, a mini os based on Linux with just Kodi. This week I’ve discovered that I’ve got quite a good alternative setup for the Chromecast for those that have a Kodi machine. Because that might be a good alternative, to still also get rid of Google and not need Chromecast support. Does anyone know how important this issue does Roku support the NPO app? (From your name I got you might be Dutch, your profile confirmed this, so thought you might use NPO haha). For developpers it may really be worth looking into why this particular app works and whether workarounds may be possible based on this. Therefore I find it very interesting to see that the Bubble upnp app which speaks of, does indeed support Chromecast. But would rather not “solve” it this way. I’ve not switched back to Lineage because I’ve also got a phone from work which I’m not allowed to root and flash anyway, so I’ve essentially still got Chromecast support. Don’t get me wrong, I think it’s terrible that this vendor lock in happens with the Chromecast and I’m really much more in favour of open source and open standards, but since some apps only support Chromecast, this is an important issue for the usability of /e/, nonetheless. For me, it would be the reason not to recommend /e/. And lack of Chromecast support is the major drawback for me. This important part is that I get jittering on my TV, with current setup.I’ve used /e/ since about… well, my original post here. I know your logic makes a lot of sense but I prefer not to go this route, spend an hour configure everything just to uninstall it after, regardless the result. While playing from my Mac has no jitters at I understand what you are proposing but even if I choose to install the Mac Plex release and test it, I will never use it, that is why I built my NAS. Now that I payed close attention, the important part is the jittering does not occur always, some videos have it, some don't? Streaming from Google Chrome browser on my TV with Cast functionality has one small jitter. I encode all my videos with Handbrake, so all settings are identical for all movies. The funny part is that occurs only in the beginning of stream, on TV or maybe my eyes are getting used to? But is always at the exact same sequence, as you can see. I no jittering also when I play the movie directly on site, in my Safari browser. I attached the video filmed from my Mac (played with IINA from SMB share) and my TV (Plex) as comparison. Some update, for a moment I thought this is related to automatic quality adjustment, but is not.
0 Comments
Leave a Reply. |