You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than now putting in work to add Nymphcast support in a lot of applications it might be useful to add a PipeWire-based client so system audio (and thus any application running on it) could be cast to a Nymphcast receiver. Ideally any Nymphcast receiver or group would appear as an audio device so people could use their existing sound settings to change audio output to a receiver. It would also be a great alternative to both Bluetooth and PipeWire-zeroconf based speakers.
The text was updated successfully, but these errors were encountered:
That's indeed similar to an idea which I had before, though I was looking mostly at cross-platform solutions for a 'virtual audio device'. I think that now that PipeWire is becoming pretty much the standard for Linux, it would be a very useful feature to have.
I have looked at the PipeWire documentation some for how to use the API, but any specific resources you may have found are always welcome before I dive into this :)
I have been looking so far at the Airplay module and trying to make that work for NymphCast. It looks similar to the Snapcast module from what I can tell.
So far I have implemented part of a NymphCast module for PipeWire, but have been rather short on time so it's been languishing. I hope to find time to resume work on it the coming weeks.
Rather than now putting in work to add Nymphcast support in a lot of applications it might be useful to add a PipeWire-based client so system audio (and thus any application running on it) could be cast to a Nymphcast receiver. Ideally any Nymphcast receiver or group would appear as an audio device so people could use their existing sound settings to change audio output to a receiver. It would also be a great alternative to both Bluetooth and PipeWire-zeroconf based speakers.
The text was updated successfully, but these errors were encountered: