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.
Thank you so much for checking something off of my todo list!<p>Apple TV lets you share with two sets of apple headphones, which is awesome... but I wanted a way to:<p>* 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.<p>I was considering using an esp32, but so happy this exists now! Thanks!
Neat way to turn an iDevice in to a usable DAC.
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.<p>I've got a few questions maybe later with the protocols and stuff but so far from initial look, it seems super promising.<p>Nice job really!
A lot of apps allow you to AirPlay to multiple devices at once — would be neat to put this on a bunch of iphones to simultaneously play music
How old of a device can I install this on? (Eg to make an old phone an AirPlay receiver).<p>Edit: looks like ios17 is earliest
Nice work! Do you think that it is possible to port this to watchOS?
It's just a thin wrapper for <a href="https://github.com/qasim/Airstream">https://github.com/qasim/Airstream</a> (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.
I think I could take a look, but watchOS has different limitations for background apps
You mean u want to run the app on Apple Watch?
Works great from iPhone to iPhone.
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: <a href="https://github.com/qasim/Airstream">https://github.com/qasim/Airstream</a><p>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.
I’ve fixed the readme to add a link to airstream
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.
Absolutely. That’s why they’re open source.<p>But it’s a common courtesy to credit the foundations you build upon when they’re doing the heavy lifting for an app.<p>If you look at the Airstream repo, you’ll see that it prominently credits the underlying library that it uses for a lot of the AirPlay foundational work.
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<p>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.<p>I’m not trying to “police” arbitrary things, I’m trying to explain <i>what the project is</i>.<p>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.
I think that name policing and “the whole project is really just a wrapper for another thing” are dramatically different points of discussion.
There is room for both. Of needless naysaying we could do with less, though.
I'm impressed this is so instantly installable via test flight! I have a suspicion Apple my pull this soon.
[flagged]
[flagged]