Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
If your device has HDMI ports, the Shairport Sync help command previously listed them with a
hw:
prefix, e.g.hw:vc4hdmi0
. Unfortunately, if you use ahw:
prefix on a HDMI device, the device may not be usable by Shairport Sync. But if you use ahdmi:
prefix, e.g.hdmi:vc4hdmi0
, it may work: something capable of receiving audio must be connected to the HDMI port and it must be powered on when your device boots up.The enhancement is to update the help text for the ALSA backend to denote HDMI devices using the
hdmi:
prefix rather thanhw:
. Now, for example, on a Raspberry Pi 4, the output is:Previously it was:
...which is technically correct but unfortunately not very useful.
Get more information about the hardware output devices using sps-alsa-explore, which has also been updated.
Docker Enhancements
-O3
) while building the Shairport Sync application itself.Bug Fixes
pthreadtestcancel()
call to the innermost loop. Thanks to Tobias Huttinger for the bug report -- Issue #1870.shairport.c
.TCP_KEEPINTVL
andTCP_KEEPCNT
if they are not defined (they are not defined in older versions of Mac OS X). Thanks to Sergey Federov for raising these issues and pointing at a potential solution.