Maya Posch

Thank you, we'll take it under consideration.

> Adding to this, I would also like to see the use cases. Additionally, a step-by-step guide for setting things up from scratch. But this can also be done via...

Thank you for your interest in NymphCast. Subtitles are supported in NymphCast's core, but aren't shown by default yet, and no controls are exposed within the NymphCast client or library...

The current version of the player now features buttons to switch between subtitles as well as video & audio streams. At some future point this will be changed to open...

Hello, and thank you for your interest in the project! The current capabilities and features are listed in the Readme for the project. At this point RTMP streams can be...

NymphCast already uses ffmpeg internally, which means it's mostly a matter of implementing code that exposes this functionality. At this point such a feature has not been planned, however.

@Florent4223 Sorry for taking a while to answer. Could you summarize your requirements if you are still interested in such a solution? @gabrielstuff NymphCast uses its own (RPC-based) protocol. There...

@Ramblurr That is correct. ChromeCast protocol receivers ('servers') require authentication by clients (like the Spotify app) using secret keys that only Google knows. This means effectively that implementing one's own...

Thank you, @Ramblurr :) Back with the CastV1 protocol (based on DIAL) it was possible to write one's own client and server, but with the v2 protocol which Google introduced...

@mapl Streaming to a ChromeCast instance is a supported feature, it is the 'build your own receiver' part that's impossible, unless you want to build the equivalent of a first-gen...