12 ms·
NymphCast: Casual attempt at open alternative to Chromecast
- vzaliva 7y agoGood project, but unfortunate bad choice of technologies (C++, AngelScript).
- robert_foss 7y agoThis is super neat, having an alternative to Chromecast is really welcome.
- pjc50 7y agoAs the article points out, ChromeCast is an extremely locked down protocol. It's designed to bind your device and all its clients permanently into the Google ecosystem. The real shame is that it had to exist in the first place and that DLNA was never adequate for this.
- makapuf 7y agoIm baffles that afaict we have no standard wireless protocol to send a still image from a pc (Open architecture) or a mobile phone to a big screen such as slides - never mind a video or reusing wifi
- felixfbecker 7y agoWhat about Miracast?
- hocuspocus 7y agoSadly while my Nexus 4 could cast to almost any TV 7 years ago, Google had to decide to remove support from stock Android in 2015 and try to shove Chromecast down our throats instead. It seems to work well from Windows 10 though.
- jsight 7y agoIts irritating how far we've gone away from standards. At least in the past there were efforts to push open solutions, but those seem to be steadily fading away.
- nitrogen 7y agoSamsung still has Smart View; not sure what protocol(s) it uses, but it seems fairly general. One of the things that kills these common standards is that every company has to tack on its own obscuring trade name. DLNA, HDMI-CEC, probably others I can't remember have all had this. It's kind of a wonder that SMTP managed to be known as just "email", but even that is largely eroded into branded experiences.
- BiteCode_dev 7y agoThey noticed apple mostly got praises and money for it, while going standards means competition and losing control. Both bring angry geeks for different reasons, but as long as most people reward them for being locked up in a closed ecosystem, I don't see why they would change.
- whoopdedo 7y agoThe wooden spike through the heart of screen mirroring is DRM. Publishers were aghast that devices were "sharing" video feeds without having to pay per-viewer licensing fees back to them. Even when using supposedly compatible devices, like a Samsung flagship phone casting to a Samsung smart TV, you have no guarantee that the app won't block the streaming to protect their subscription model.
- riedel 7y agoUpnp and chromecast have quite some stuff in common. I think its all politics and messed up standardization. Add some recoding services like bubbleupnp server, browser support and dlna can still serve as a nice alternative with tons of hw. But people like their locked ecosystems and are not willing to invest in interop. Upnp was build for home automation so i guess it was too ambitious considering the company political minefield. Its successor dpws lives in an equally strange niche now: printer autoconfiguration. The open source community never cared much to provide robust free implementations. (I wrote upnp and dpws gateways for smartdevices more than 10 years ago and the situation hasnt changed since)
- reificator 7y ago> But people like their locked ecosystems and are not willing to invest in interop. I think that's a mischaracterization. Given two identical experiences, one that locked you in and one that didn't, I'd imagine most people (though sadly not all) would choose the more open one. The locked in experience here is simply substantially more seamless and out-of-the-box ready than the open alternative. Given that the point of a handover system is to make using multiple devices seamless, it's obvious that being "more seamless" is an advantage. I setup a Chromecast for my mother who doesn't have cable or anything at home, and it took several explanations spread out over a year before she finally started using it on her own, but now she's using it daily. Any harder to use and it wouldn't have been helpful at all. She's not exactly a luddite either, this is actually the first thing I've tried to teach her that she's struggled so hard with. Hopefully it's not a sign of aging...
- mixmastamyk 7y agoWhat does she watch with it? YouTube?
- reificator 7y agoThat, Prime Video, some knitting thing, probably more than that tbh. We don't share a TV so I don't have a clue what she watches.
- kodablah 7y agoI had success a couple of years ago patching the Chrome binary to put my own CA Chromecast roots in there and then broadcasting my software device over mdns [0]. At that time the newer protocol wasn't implemented in Chrome yet so the furthest I got was appearing in the device list. But now it is implemented [1], so maybe I should revisit. Of course this isn't a general solution since it requires patching the binary instead of having some other way to use custom keys (they compile them into Chrome today, and of course other devices are even more closed). 0 - https://github.com/thibauts/node-castv2/issues/2#issuecomment-403872299 https://github.com/thibauts/node-castv2/issues/2#issuecommen... 1 - https://bugs.chromium.org/p/chromium/issues/detail?id=809249 https://bugs.chromium.org/p/chromium/issues/detail?id=809249
- ColanR 7y agoPlan 9 could pull this off seamlessly. Each program window is a folder tree, so moving the window to the external screen would be as simple as remounting it on the remote server. Plan 9 is designed for that and does it trivially. The file tree paradigm also means that standard UNIX permissions apply.
- pedrocx486 7y ago>as simple as remounting it on the remote server Don't think the common enduser would agree with that.
- ColanR 7y agoObviously that would get wrapped up in a user-friendly UI. My point is that the backend would be straightforward.
- notyourday 7y agoExcept Plan9 is a design pipedream that got shredded on the first encounter with reality which is why it has less of a penetration even in a geek community than BeOS. The largest use case for something from Plan9 is 9P transport used by QEMU to share host folders with guests.
- laumars 7y agoThe two platforms are targeting different audiences and solving different problems so I don't think it really pays to compare them. For example Plan 9 was released in a market where UNIX was already successful and "good enough". So it was always going to be a tough sell. Whereas BeOS was released in an era when desktop OSs totally sucked (NT wasn't yet ready for home users, Windows 9x was an unstable mess, Mac OS 8 and 9 were even worse than Win 9x, Linux wasn't even remotely ready for the casual user and Atari / Amiga dead and becoming increasingly irrelevant in all but a few niche scenes). Even at that time it felt like desktop operating systems sucked and then along came BeOS and proved just how much better things could be. It felt light years ahead of the competition and yet still failed (I'm not bitter at all!) It's also worth noting that Plan 9 did go on to influence UNIX and Linux quite a lot since. So while 9P transport might superficially feel like the only Plan 9 tool to survive (it's not because people do use other stuff like ACME), there's a lot of Plan 9's influence in modern *nix too (eg FUSE).
- notyourday 7y ago> As the article points out, ChromeCast is an extremely locked down protocol. It's designed to bind your device and all its clients permanently into the Google ecosystem. This does not pass the smell test. I can cast onto any of my Chromecasts using VLC and Catt[0] and while the former is limited to media, Catt lets me render websites just fine. I believe Catt's author is on HN. [0] https://github.com/skorokithakis/catt https://github.com/skorokithakis/catt
- efreak 7y agoNow try building your own Chromecast receiver. Transmitting is easy, receiving is impossible afaik.
- notyourday 7y agoThat's only the case if one wants to integrate with Google ecosystem. Every single mobile app with a more than rudimentary casting capabilities has a custom receiver built by the developer of the application. When we built ours the only real issue were Google's funky interpretation of CORS rules and sucky documentation. However I'm still unclear... if the goal is to render output on Chromecast, a combination of ability to render web pages, video and audio streams and images seem to cover pretty much everything needed to interact with the device.
- pjc50 7y agoYes, that's what I meant: you can cast to the chromecast, but you can't substitute for it nearly so easily. The client is open but the server is closed. I believe the applications have to be registered with Google? (Who presumably can ban them?)
- notyourday 7y agoI am pretty sure you're correct and we had to register our app. My point is why not push media/web pages using something like catt bypassing all the mess? I certainly see the appeal of using anything with HDMI port to push the media out but RPI and likes aren't anywhere close to Chromecast dongles in polish and what one needs for adoption is ease of use.
- amoshi 7y agoSo many letter combinations in the world and they went for "Nymph"Cast? Like Nympho (Nymphomaniac)?
- detaro 7y agoLike "Nymphs", the nature spirits?
- ipnon 7y agoA nymph is a supernatural female diety in Greek mythology associated with air, water and wood.
- jessaustin 7y agoHehehe, you said "wood".
- thwave 7y agoIt also just means "a young wife", or "a marriageable maiden" in ancient Greek.
- hjek 7y agoI think it's sweet naming a project after a supernatural being rather than a toxic heavy metal. Perhaps the sound of that name has less of a macho crunch and feels a bit unusual but couldn't that be a good thing?
- DoreenMichele 7y agoThe author blurb: A girl who is trying to find her way through the confusion of giftedness, human societies and her intersexuality. Her life is somewhat of a dramatic survival show. She is currently working on her autobiography. To me, it mostly signals "A girl is working on this project and wants the name of it to signal that." If it were written by a guy and used a word that could be interpreted to mean "Studly," we probably wouldn't bat an eyelash. Many people likely wouldn't notice at all. Edit: https://www.girlswithslingshots.com/comic/gws-chaser-810 https://www.girlswithslingshots.com/comic/gws-chaser-810
- thom 7y agoWhile I am not proud of this, Chromecast is a fairly core part of mine and my family's routine each week. It's one of probably only two consumer technologies that I've found transformative in the last ten years, the other being Apple Pay. It'd certainly be interesting if there were an viable open alternative, but it seems unlikely that NymphCast is going to make a debut in the Netflix app anytime soon. I'd probably settle for a good Firefox implementation of the Chromecast protocol, but that's obviously missing the point here. Also as an aside, AngelScript's is another of these programming language sites where sample code seems to be more than three clicks away from the homepage. I will admit I gave up before finding any.
- Waterluvian 7y agoChromecast is the killer product that drives our home's media use. It just works. It's accessible to anyone with their phone. The UI are the phone apps. It plus a few subscription services makes every other media box obsolete for us. I got a Roku tv last month. For jokes I turned on WiFi and tried out the built in streaming. Just terrible. Great for people without phones, but who else would want that kind of experience?
- diamondo25 7y agoI was happy with my chromecasts, until one of them stopped working on one screen. It boots up, google logo does its thing and then its black. Device can be communicated to, and resets do not work. I have read that this is HDCP related and that using a chinese hdmi splitter works... The device works fine on my Dell monitor, and I am not using any extension cable...
- thebean11 7y agoMaybe I need to give it another shot, I switched to the built in Roku functionality because I couldn't stand the phone player disconnecting from the chromecast. It would always take me at least 30 seconds to pause anything; with the Roku I have a dedicated remote that works every time instantly, and it handles both the on/off and the media.
- kachurovskiy 7y agoBuilt something similar but with less features and moving parts, abandoned due to the lack of interest: https://github.com/kachurovskiy/ArinaCast https://github.com/kachurovskiy/ArinaCast
- k__ 7y agoI tried to get some streaming going on a spare monitor a few years ago. Miracast and Chromecast were a garbage fire. In the end I only got AirPlay to work and even that wasn't without problems.
- BlueTemplar 7y agoHow does one deal with mp4 being proprietary?
- deno 7y agoMiracast is much more straightforward and predictable and with 801.11ad you can even go lossless. Also you can get an HDMI receiver for like $15, because it’s just streaming instead of a full stack. Chromecast will go of the way Google’s many Dodos. And good riddance!
- remir 7y agoIt depends on the use case, I guess. Miracast is good for quick sharing of content stored locally on your phone/laptop, whereas Chromecast is better suited to stream content that is hosted elsewhere, so it doesn't drain your battery.
- deno 7y agoThat’s a single use case and you can just reverse it and have a ‘remote control’ mode on the portable device. In practice people are now buying Telescreens (not like there’s option tbh) and they have Android or at least Netflix already built in.
- Xorlev 7y agoLooking through the code you can tell the author is putting a lot of work into this project. It's not the cleanest code, but it's the kind of "home cooked" project I really enjoy seeing. Built from the ground up using a self-rolled RPC library and everything. It's really neat. Give it some more "bake time" and this could be a really great way to use a Pi.
- crudbug 7y agoW3C has SecondScreen WG looking at similar open solution [1] [1] https://www.w3.org/2014/secondscreen/ https://www.w3.org/2014/secondscreen/
- isuckatcoding 7y agoThis is fantastic
- guyzero 7y agoChromecast and AirPlay are both locked down because they're fundamentally tied to DRM and no content provider is going to spend any time on a platform that doesn't have strong L1 DRM.
- alkonaut 7y agoAnd it works the other way too: as a consumer I don't care about whether something is open or not, if it doesn't stream the things I want to stream.
- _eht 7y agoConsider caring.
- alkonaut 7y agoI do care. I just care less about openness than convenience notice the "IF it doesn't stream...". Given two systems that work equally well, I'd pick the open one. That's rarely the case though. So I pick the polished one. I think this goes for most consumers.
- the_gipsy 7y agoIt affects consumers, though. Closed platforms work against consumers' interest way too often.
- _jal 7y agoYou start caring when 'your' devices are suborned into a proxy fight against their actual owner's competitors.
- alkonaut 7y agoNo. I care about both convenience and openness. At some point perhaps the proxy fight makes the producs inconvenient? Perhaps even less convenient than the open alternative? At that point consumers might reconsider. Not until then.
- aogl 7y agoThis seems like a very unfortunate name..
- stevehawk 7y agoIf you're an Android user there are alternatives to Chromecast. I use Roku devices + Samsung's 'SmartView' which I'm pretty sure is just rebranded MiraCast and it works like a champ.
- bgorman 7y agoThe biggest joke is Google removed Miracast support from Pixel phones
- hocuspocus 7y agoIt happened way earlier than Pixels. The Nexus 5 is the last device that supports Miracast.
- solarkraft 7y agoLooks cool! I have myself been super frustrated by the lack of free streaming protocols or implementations. DLNA (UPnP) is in theory perfect for this use case and it wouldn't be that hard to use it together with VLC and a Python script and I have indeed attempted this, but at the end just gave up due to the complexity of the protocol (and my laziness). I am currently still in the market for a good casting solution like this. I'll probably try this, but at a first glance it seems like it may do a little more than I need. Does anyone know any other similar projects?
- Krasnol 7y agoI have two of them and I hate it. I hate having to use a chrome browser to stream online streams. Vivaldis last version just crashes on fullscreen tab cast. Installed Chromium, it wouldn't find any of the Chromecasts. VLC finally supports it but sometimes it's not working or you can't hit pause and resume. It'll just stop and you have to start from zero. Also it's doing things online I have no control over. I'd be so happy to have an easy open source solution. I'm ready to spend some money on it too.
- golemiprague 7y agoIt's interesting the difference between the US to the rest of the world. It seems like in the US people are really attached to big conglomerates products, whether it is Apple TV or Google chromecast while in many other countries the main thing I see people use are cheap Chinese Android boxes which seems to work really well with a simple remote without all the fanfare and connectivity to everything and what not.
- warren6551 7y agoWelcome to The illuminati World. Bringing the poor, the needy and the talented to limelight of fame and riches. Get money, fame, powers, security, get recognised in your business, political race, rise to the top in whatever you do, be protected spiritually and physically! All these you will achieve in a twinkle of an eye when you get initiated into the GREAT ILLUMINATI TEMPLE. Once you are initiated to the ILLUMINATI EMPIRE, you will have numerous benefits . do you wanna join?
- warren6551 7y agoThis is an open invitation for you to become part of the world's biggest conglomerate and reach the peak of your career. As we begin this year's recruitment programme and our annual feast of harvest is almost at hand. Do you agree to be a member of this illuminati new world order?message the supreme Master(+16028992039) on WhatsApp only or email: grandmasterilluminatti9@gmail.com
- sneak 7y agoI think the real issue here is that streaming to these things requires buy-in to support the client inside of eg the video player app or the audio player app. I have an iPhone, and it can only send system-level audio to AirPlay. The Spotify app itself also supports streaming to Amazon devices. The YouTube app will also stream to a Chromecast. It’s all so balkanized. I’m not sure making a new format/protocol will solve that problem, although if it is solvable that’s certainly the first step.
- fyfy18 7y agoMy wife uses Bluetooth to avoid that issue. For some reason the receiver we got (new last year) only supports one device paired at a time though >_<
- hackkitten 7y agoOne idea I have to perhaps get around this issue is to fudge in an external/new audio/video output that can be targeted instead of the standard outputs. This of course gets into some heavily platform-specific nonsense, which is why I haven't pursued it further yet. Maybe after the first release of NymphCast it's something to look at in more depth :) (I'm the NymphCast author)
- justlexi93 7y agoThis is great! I would love to remove a dependency on proprietary hardware. Do Netflix, YouTube, and other streaming services have open APIs that would allow for 3rd party apps supporting NymphCast, or would we have to depend on the companies supporting NymphCast directly? There seems to be a chicken and egg problem where apps won't support NymphCast until there's enough mainstream buy-in, but there won't be enough mainstream buy-in until enough apps support it.
- worldsayshi 7y agoInstead of talking vendors into supporting your particular protocol, wouldn't it be possible to use a protocol like picture-in-picture to extract the video stream? https://github.com/w3c/picture-in-picture https://github.com/w3c/picture-in-picture I guess it doesn't handle the audio though.
- kingosticks 7y agoPlayback of whatever media on a SBC (rpi etc) is not the problem. Of course, it's great to have more software doing this and I applaud the effort (personally I'd have leveraged gstreamer and saved a load of time since I've used it before). The real problem, quickly dismissed in this article, is support integrated into 1st party apps. Chromecast lets you use a streaming platform app 100% normally and then 2 clicks later it's playing on your big screen/speakers. You could implement some sort of bridge app (that you'd "share" the content to) but then you are switching between the streaming app for content discovery, and the bridge app for control. That's not the chromecast experience. The only way we can get that experience is with 1st class support built into the streaming app. Spotify/Google/soundcloud/Amazon have no reason at all to work on adding support for something new until it becomes popular, but that's obviously a chicken and egg situation. Chromecast support is already built in everywhere, but of course that's a non-starter since Google have locked everything down sufficiently to prevent implementation of a receiver. I don't know the answer to this.
- hackkitten 7y agoI do not feel that I dismissed support for 1st party apps in the article. In fact, I have considered doing so for Netflix and Spotify, among others. Some have a control API for the 1st party app, such as what is used on Android, for example. It's however a lot of work, with spotty documentation and questionable support. That's why for the first release I haven't really bothered with it too much and instead focused on the core functionality of streaming audio and video, and controlling the NymphCast server from the client. (I'm the NymphCast author)
- kingosticks 7y ago> In fact, I have considered doing so for Netflix and Spotify, among others I must not understand because my argument is that the support absolutely must be built into the netflix and Spotify apps themselves, that seemless integration is what makes chromecast so usable. The media discovery and control needs to be in their app, not split between two different apps. So what can you do, other than provide a library for Spotify and Netflix to then ignore?
- JeremyNT 7y agoI love to see some progress in this space! I was curious about using e.g. Raspberry Pis or old Android devices as replacements for the now defunct Google Chromecast Audio, that is a set of linked devices connected to speakers throughout the house and all streaming from a single source that I can control from my phone or PC. Doing this seemed to be unreasonably difficult. The closest thing to a solution I identified was using Mopidy along with Icecast, where Mopidy is the control plane and Icecast is the audio sink, and all client devices simply permanently connected to the shoutcast stream. This "worked" but it is very frustrating for a simple use case. Mopidy used to be a MPD server implementation, but it has deprecated that in favor of its own API, and the client options were very limited. And nevermind video, this was just audio... Anyway, I feel like NymphCast is a very welcome development, and I really hope that Maya will continue to work on it.
- hackkitten 7y agoThank you for the feedback :) I have no plans to stop working on this project any time soon. Having it work as a ChromeCast Audio replacement was one of my initial thoughts back in 2019, and while the scope has slightly increased, that initial goal hasn't been altered. After some feedback, I am prioritising the implementing of multi-target streaming (multiple speakers/TVs) so that this will exist (in some form) in the first release. Another of the goals is for the whole system to be dead-simple to setup and use. Heavens know I have wasted enough of my life trying to make half-broken projects somewhat do what they were supposed to do. I'd rather my own projects are not among those :) (I'm the NymphCast author)
- kingosticks 7y agoFYI Mopidy-MPD is not actually deprecated. It just doesn't have a maintainer that's interested in it. Some parts of the MPD protocol are a bad fit for streaming services where the 'media library' is essentially infinite so it's much harder to use performantly. That makes it really frustrating to develop with considering the Mopidy core API is available and far better suited.
- JeremyNT 7y ago
- mfoltzgoogle 7y agoHi there, I'm from Chrome, someone on my team pointed me at this thread. My team supports casting features in Chrome. This is a fantastic project and it's great to see energy around this. I get the frustration around the inability to make devices work together for casting. In the standards community, we have been working with other companies and researchers on a protocol [1] that provides the groundwork for interoperability in media streaming and media control on the Web between browsers/apps and devices. We are developing an open source implementation and plan to see it in future products. There's a lot of other work going on in the Web standards community as well, that in the near future will allow Web apps to create their own media codec pipelines and streaming protocols customized to their needs [2] [3]. [1] https://w3c.github.io/openscreenprotocol/ https://w3c.github.io/openscreenprotocol/ [2] https://github.com/WICG/web-codecs https://github.com/WICG/web-codecs [3] https://github.com/WICG/web-transport https://github.com/WICG/web-transport (client/server), https://w3c.github.io/webrtc-quic/ https://w3c.github.io/webrtc-quic/ (P2P) If you have suggested use cases or questions engaging on GitHub through the standards repos is a great way to get involved or you can email public-secondscreen@w3.org. Cheers, Mark Foltz GitHub: https://github.com/mfoltzgoogle https://github.com/mfoltzgoogle