August 28th, 2024

FCast: Casting Made Open Source

FCast is an open-source protocol for wireless audio and video streaming, supporting multiple platforms and stream types, enabling custom receiver development, and promoting community contributions for enhanced innovation.

Read original articleLink Icon
ExcitementCuriositySkepticism
FCast: Casting Made Open Source

FCast is an open-source protocol designed to facilitate wireless audio and video streaming across various platforms, including Linux, MacOS, Windows, and Android. It supports multiple stream types such as DASH, HLS, and mp4, allowing developers to create custom streaming experiences. Unlike traditional closed protocols like Chromecast or AirPlay, FCast promotes open innovation, enabling developers to build their own receivers and integrate the protocol into existing applications. Users can set up compatible receivers on their devices to begin streaming, while developers have access to extensive resources, including example implementations and protocol documentation. Key features of FCast include cross-platform compatibility, full playback control, mDNS for device discovery, real-time updates, and a strong emphasis on community contributions. The project aims to democratize media streaming by encouraging innovation and providing a flexible platform for developers.

- FCast is an open-source protocol for wireless audio and video streaming.

- It supports various stream types and is compatible with multiple operating systems.

- Developers can create custom receivers and integrate FCast into their applications.

- The protocol emphasizes community contributions and continuous improvement.

- FCast simplifies device discovery using mDNS technology.

AI: What people are saying
The comments on the FCast article reflect a mix of excitement and skepticism about the protocol's potential impact on wireless streaming.
  • Users express enthusiasm for FCast as a promising alternative to existing casting solutions like Chromecast and Airplay.
  • There are inquiries about the integration of FCast into popular platforms and devices, such as browsers and smart TVs.
  • Some commenters compare FCast to other existing technologies, questioning its unique advantages.
  • Concerns are raised about the terminology used in the protocol, suggesting it may be confusing for users.
  • Community interest in contributing to and developing the protocol is evident, highlighting a collaborative spirit.
Link Icon 10 comments
By @r-w - 5 months
This project comes from FUTO, which is now making a name for itself by releasing and maintaining OSS alternatives like this, as well as sponsoring development of other OSS options. I personally first came across them when Louis Rossmann announced his affiliation. Very excited to see where this goes!

As an aside, I wonder what it will take to get the protocol integrated into browsers? I presume Chrome is a foregone conclusion, but maybe Firefox and/or Brave would be interested in an integration?

By @ravenstine - 5 months
Now we're talking! The experience of casting has recently become a bigger headache for me than ever. Last month, I made a comment on HN about how the original Chromecast was great and that I'm disappointed in the state of the current Chromecast devices; a lot of people seem to agree with this. I've also had trouble with Airplay since streaming from Quicktime seems to only support h264, and even that hasn't really worked for me even though my 1st gen Chromecast worked great before my TCL television fried it.

Casting video should be simple, straight forward, and open. Glad to see there's projects like this trying to solve this problem rather than leaving it up to advertising firms.

By @koen31 - 5 months
FCast engineer here. Look forward to FCast receivers on platforms like AppleTV, Roku, Tizen (Samsung), WebOS (LG).
By @westurner - 5 months
How does FCast differ from Matter Casting?

https://news.ycombinator.com/item?id=41171060&p=2#41172407

"What Is Matter Casting and How Is It Different From AirPlay or Chromecast?" (2024) https://www.howtogeek.com/what-is-matter-casting-and-how-is-... :

> You can also potentially use the new casting standard to control some of your TV’s functions while casting media on it, a task at which both AirPlay and Chromecast are somewhat limited.

Feature ideas: PIP Picture-in-Picture, The ability to find additional videos and add to a [queue] playlist without stopping the playing video

By @nsteel - 5 months
NymphCast has been around for years but it's still basically unheard of. This has more polished marketing (and a less weird name) but other than that I don't see what makes it any more likely to succeed.

* https://news.ycombinator.com/item?id=22457351

* https://news.ycombinator.com/item?id=27482699

By @dblitt - 5 months
Could this end up on an embedded smart tv device, like a Roku?
By @_volatile - 5 months
Is it currently usable in anything other than GrayJay?

I wish I could use this with local videos.

By @zigzag312 - 5 months
I'm not a native English speaker, but FreeCast would be better, more meaningful name in my opinion.
By @throwaway81523 - 5 months
I've used Icecast before. It worked great. Is Fcast better somehow?
By @justinclift - 5 months
Seems to use confusing terminology?

  In FCast, a "client" is a device or software application that discovers and
  communicates with a "receiver".

  The client, which can be a terminal client or an Android application, uses
  the FCast protocol to send media content to the receiver, such as a TV or
  media top box. The client initiates the media streaming by connecting to the
  receiver, launching the media, and then the receiver begins playing the media.

  Once the media is launched, the client can control the playback, allowing
  operations like pause, resume, seek, and volume adjustment.
Seems like basically a client-server relationship, but with the "client" acting as a server and a "receiver" acting as a er... client?

But with the "client" being the thing to control the start/stop/etc of the media, which is a weird thing for a server to do.