That's interesting! Does it work for streaming video or just audio? Sometimes I'd love to AirPlay from my video editing software to my iPhone to check how it looks on the smaller screen, checking colors and overall appearance.
We’ve been looking for something like this for our conference room. A PC presenting on a large TV, but mirrored/AirPlayed on iPads for anyone that wanted a version closer to their face.
If it works for you, happy the help you setup a private instance or something. And for in-office use, maybe optimize for quality rather than minimal updates it is now.
Thank you so much for checking something off of my todo list!
Apple TV lets you share with two sets of apple headphones, which is awesome... but I wanted a way to:
* Share to more than two sets
* Extend coverage past the (very generous) bluetooth range of AirPods.
* Have lossless (albeit 44khz/16bit) wireless audio with audiophile headphones.
I was considering using an esp32, but so happy this exists now! Thanks!
This is actually something I've been looking for for a while, through some workarounds with jelkyfin and others I've been able to navigate something but this seems promising.
I've got a few questions maybe later with the protocols and stuff but so far from initial look, it seems super promising.
It's just a thin wrapper for https://github.com/qasim/Airstream (I think it's very lame that the README doesn't mention this), which I think would work in a watchOS app although I'm not 100% sure it would get approved.
This is cool, but like the other comment said I think it would be prudent to mention in the README that this uses the Airstream project for the AirPlay implementation: https://github.com/qasim/Airstream
I thought this was a new Airplay implementation from the way it was described, but then I looked at the source code and realized there wasn’t much there. Nothing wrong with wrapping a library, but it’s nice to mention the technologies used and set expectations.
Libraries are made to be used as the base for the actual application. I checked your GitHub link - no clue how I’d use it without coding an entire solution.
These threads are really about discussing the work and less about policing projects' formatting, names, credits, etc. It's just way, way, way less interesting.
> These threads are really about discussing the work
That’s what I was trying to do. I opened up the code, started reading, and realized it wasn’t really what I thought it was.
I’m not trying to “police” arbitrary things, I’m trying to explain what the project is.
There’s been a recent trend of “Show HN” projects taking credit for other people’s work, like the “KVSplit” Show HN from several weeks ago that claimed credit for some upstream features in another project by wrapping it up in a separate repo and writing some LLM-generated claims.
A link to the utilized library is not simply drive-by grump. I agree with a lot of complaints about non-substantive grouchiness on HN but I can’t be sold on this one.
If it works for you, happy the help you setup a private instance or something. And for in-office use, maybe optimize for quality rather than minimal updates it is now.
Apple TV lets you share with two sets of apple headphones, which is awesome... but I wanted a way to:
* Share to more than two sets * Extend coverage past the (very generous) bluetooth range of AirPods. * Have lossless (albeit 44khz/16bit) wireless audio with audiophile headphones.
I was considering using an esp32, but so happy this exists now! Thanks!
I've got a few questions maybe later with the protocols and stuff but so far from initial look, it seems super promising.
Nice job really!
Edit: looks like ios17 is earliest
I thought this was a new Airplay implementation from the way it was described, but then I looked at the source code and realized there wasn’t much there. Nothing wrong with wrapping a library, but it’s nice to mention the technologies used and set expectations.
That’s what I was trying to do. I opened up the code, started reading, and realized it wasn’t really what I thought it was.
I’m not trying to “police” arbitrary things, I’m trying to explain what the project is.
There’s been a recent trend of “Show HN” projects taking credit for other people’s work, like the “KVSplit” Show HN from several weeks ago that claimed credit for some upstream features in another project by wrapping it up in a separate repo and writing some LLM-generated claims.
Without massive moderator intervention that whole submission would have been buried in cruft. Better to not start cruftalanches to begin with.