-
-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Problem]: Using Docker inside a Proxmox VM -- bad sound quality when using non-default output device. #1833
Comments
Thanks for the post. I'm just wondering if there's a possibility that the hardware output device is not capable of working at 44,100 frames per second. There is a tool called sps-alsa-explore (also available a a Docker image) that will give you some more information about what output devices are available that are compatible with Shairport Sync. It could be worth trying out. |
I'll try the tool, but I'm wondering if my USB sound card is not capable of working at 44,100 fps then it should behave same way when I refer to it as "default" output device? |
Ah, sorry, should have explained a bit more. The "default" device probably includes a transcoder that could transcode from Shairport Sync's 44,100 to the output device's 48,000 fps, whereas going directly to the output device bypasses the transcoding. But we're getting ahead of ourselves. |
Here is the output from sps-alsa-explore:
|
thank you for explanation, it makes sense now :)
|
Super (just edited it for formatting). That looks good, so no transcoding problems there. Ensuring that Shairport Sync isn't running in the background, could you run, from the command line, something like:
and let it run through the unpleasantness for a short while, and the post the log, please? Note that after |
Also, is anything else using the output device? Any other audio program or utility? |
No, I don't think it is being used by anything else. It is mounted only to one VM and I have only one container running there. Below is the output from
|
Thanks. The log seems to show that it's listening on port 6001 instead of the default port 7000. Could you try a different port, or leave it at default for the present? (Try to avoid ports in the range 6001 -- 6010.) |
(I shoulda seen that 6001 thing earlier, sorry.) |
tried with port 7000, still hearing crackling
|
Thanks. The thing is, it looks as if there's another instance of Shairport Sync running somewhere in the background, possibly started automatically after startup, or possibly running in another window, so the log you are posting is not the log of the functioning Shairport Sync, and so is no use for debugging. To stop an automatically-started version of Shairport Sync, do a |
I'm running Shairport Sync in docker container, I run |
Just looking back over this -- are you running Shairport Sync inside Docker on a Linux system that's in a VMWare/VirtualBox/Parallels Virtual Machine? |
Yes, I'm using ProxMox |
Okay, so a copy of Shairport Sync is automatically launched when the Docker container comes up, so when you execute the command line inside the Docker image, that copy of Shairport Sync is already running. The problem now is that, if you kill it, the container will close. So, if you could stop that Docker container completely and instead do this on the command line:
It should log the single copy of Shairport Sync that should be running. (Haven't tested it here though.) |
here is new output:
|
Great stuff -- well done. Sadly (for the big picture) it indicates that Shairport Sync is working more-or-less normally. The interpolation needed to compensate for sync errors should be almost completely imperceptible. However, the output FPS figures indicate that the accuracy of the clocking of the output device isn't great -- I'd expect the If you could run the experiment without specifying the output device, i.e:
It would be interesting to see the statistics. Presuming they are mostly the same, I'm wondering if the |
What happened?
Hi, I installed Shairport-sync in docker container and configured it to use alsa "default" output device.
I have one physical USB-sound card which is listed under different names when I run
aplay -L
When I specify any other name for same physical output device, sound quality gets really bad and I hear lots of crackling.
Relevant log output
System Information.
Intel i5 with ProxMox
Running Shairport-Sync as docker container in Debian Bookworm VM.
Configuration Information.
PulseAudio or PipeWire installed?
How did you install Shairport Sync?
Docker
Check previous issues
The text was updated successfully, but these errors were encountered: