If content providers ( remote sites ) don't support the device for a push via whatever streaming protocol the device uses then the device...
If content providers ( remote sites ) don't support the device for a push via whatever streaming protocol the device uses then the device has to have a pull proxy to interpret the content in addition to rendering it over HDMI. The point is we already have a cheap HDMI renderer that can be connected to a network, has a fantastic form factor, most of the needed features, is so incredibly brain-dead simple to use that my wife's mother who can't make a programmable coffee machine work took less than 10 minutes to connect it to watch Netflix and is available in Walmart/Target/BestBuy/OfficeDepot/Staples etc. The biggest enabler of non-restricted casting would not be a renderer interface. It would be an easy to integrate library in non-geek languages (i.e. not C/C++/Rust/Go but Python, JavaScript, PHP, Ruby, Perl, etc ) with interfaces like PlayMediaFile(chromecastid, url) and RenderWebPage(chromecastid, state, url) to drive a Chromecast from a local box/smartphone without having any support from a content provider. I have been playing with Jellyfin/Plex/etc recently and they are atrocious in the UX for anyone who is not invested in making them work well because they all try to solve all of the annoying problem of handling and organizing media libraries, pulling media sources together and interfacing with casting devices. They do everything OK, but do nothing well. Give their authors a solid way to cast to Chromecast that just works and we will have an explosion of content to TV solutions.
Posted by notyourday on Mar 2, 2020, 12:58 PM
Tags
Related issues
- I've been thinking about this question a lot recently and have asked my friends for their opinions.
- > There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
- Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
- Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
- Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
- The page keeps crashing for me.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
ux (Network)
I've been thinking about this question a lot recently and have asked my friends for their opinions.
> There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
The page keeps crashing for me.
Server-side pagination to make ArgoCD UI a rocket
[RFC] Zero-runtime CSS-in-JS implementation
If content providers ( remote sites ) don't support the device for a push via whatever streaming protocol the device uses then the device...
If content providers ( remote sites ) don't support the device for a push via whatever streaming protocol the device uses then the device has to have a pull proxy to interpret the content in addition to rendering it over HDMI. The point is we already have a cheap HDMI renderer that can be connected to a network, has a fantastic form factor, most of the needed features, is so incredibly brain-dead simple to use that my wife's mother who can't make a programmable coffee machine work took less than 10 minutes to connect it to watch Netflix and is available in Walmart/Target/BestBuy/OfficeDepot/Staples etc. The biggest enabler of non-restricted casting would not be a renderer interface. It would be an easy to integrate library in non-geek languages (i.e. not C/C++/Rust/Go but Python, JavaScript, PHP, Ruby, Perl, etc ) with interfaces like PlayMediaFile(chromecastid, url) and RenderWebPage(chromecastid, state, url) to drive a Chromecast from a local box/smartphone without having any support from a content provider. I have been playing with Jellyfin/Plex/etc recently and they are atrocious in the UX for anyone who is not invested in making them work well because they all try to solve all of the annoying problem of handling and organizing media libraries, pulling media sources together and interfacing with casting devices. They do everything OK, but do nothing well. Give their authors a solid way to cast to Chromecast that just works and we will have an explosion of content to TV solutions.
Comments (0)
No comments yet. Start the discussion.