-
-
Notifications
You must be signed in to change notification settings - Fork 581
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
Help with configuring asound.conf and shairport-sync.conf #1339
Comments
Thanks for the post. Actually Shairport Sync doesn't use the Ideally, if possible, you should use an They also have shorter names based on the card number. Thus, from By inspection, you can match up the long names with the short names. Thus, to output to the Sabaj A3, it looks like the
or
Now there may be a problem with this. Shairport Sync requires that the output device must be capable of accepting audio at 44,100 frames per second (CD quality) and this Sabaj A3 may not do so -- the specification is unclear on this. If it does not accept 44,100 FPS, Shairport Sync will terminate and leave a message in the logs. In that case, you can try using:
or
These are "virtual" I hope this helps. |
Thank you for the quick response. I had shairport-sync working with the Sabaj amp under Buster, on a PI3. I downloaded and installed Bullseye and did a clean install, and tried both output_device="hw:CARD=AMP,DEV=0" and output_device="hw:1"; in the shairport-sync.conf file, but did not get any output from the amp. However, as I stated, using hw:0 will play output through the onboard card through the 3.5mm jack.
I will try the output_device="hw:1"; option. If that fails, I will reinstall from scratch, and try again.
Thank you.
Robert
From: Mike Brady ***@***.***>
Sent: Thursday, November 18, 2021 6:43 AM
To: mikebrady/shairport-sync ***@***.***>
Cc: rtmurphy ***@***.***>; Author ***@***.***>
Subject: Re: [mikebrady/shairport-sync] Help with configuring asound.conf and shairport-sync.conf (Issue #1339)
Thanks for the post. Actually Shairport Sync doesn't use the asound.conf stuff -- that's an alsa configuration file.
Ideally, if possible, you should use an alsa hardware device directly. Those are indicated by having hw: at the start of their names. So, from aplay -L you can see:
hw:CARD=Headphones,DEV=0,
hw:CARD=AMP,DEV=0 and
hw:CARD=vc4hdmi,DEV=0.
They also have shorter names based on the card number. Thus, from aplay -l you have
hw:0, hw:1 and hw:2.
By inspection, you can match up the long names with the short names.
Thus, to output to the Sabaj A3, it looks like the output_device setting should be:
output_device="hw:CARD=AMP,DEV=0";
or
output_device="hw:1";
Now there may be a problem with this. Shairport Sync requires that the output device must be capable of accepting audio at 44,100 frames per second (CD quality) and this Sabaj A3 may not do so -- the specification is unclear on this. If it does not accept 44,100 FPS, Shairport Sync will terminate and leave a message in the logs. In that case, you can try using:
output_device="plughw:CARD=AMP,DEV=0";
or
output_device="plughw:1";
These are "virtual" alsa devices that pass audio through rate converters (and maybe other components) before sending the resulting data to the respective hardware devices. If they are your only option, so be it, but if they can be avoided, so much the better.
I hope this helps.
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmikebrady%2Fshairport-sync%2Fissues%2F1339%23issuecomment-972789736&data=04%7C01%7C%7C6e56421c0da348a47d9c08d9aa889f56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637728326036284086%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3iG%2Fejwlx7zRcVMRMK%2FWGr6Otpk13ZuIZw5R6F%2Ba3HM%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF7PB5UM7LUQKKNDI5N7LFDUMTRFRANCNFSM5IIEU6CQ&data=04%7C01%7C%7C6e56421c0da348a47d9c08d9aa889f56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637728326036284086%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4dnX0u%2F2hd5SrCCBSvSYyLFiGWTvMMHcPndCFXdj5lM%3D&reserved=0>.
Triage notifications on the go with GitHub Mobile for iOS<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7C6e56421c0da348a47d9c08d9aa889f56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637728326036294075%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=FFpWNvBqV9uWVT2GweoTwSP0LbAVtGU8k4%2FqxVBWGwM%3D&reserved=0> or Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7C6e56421c0da348a47d9c08d9aa889f56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637728326036304070%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5ApM2koFaWA7aoX2HSkAh5zgPebHgEJ3tIWAJSAo8o0%3D&reserved=0>.
|
Thanks for the update. With all these, it’s important to check the volume on the output device and to ensure that it is not muted. You can do both by checking the device with |
This issue has been inactive for 45 days so will be closed 7 days from now. To prevent this, please remove the "stale" label or post a comment. |
Hello: I have tried for a few hours to get shairport-sync to work with my external amp (sabaj). It works fine with the pi's headphone jack. Can you please tell me what should be in the asound.conf file and output_device = line should be in the shairport-sync.conf file. Thank you.
Here is the output from aplayer, etc:
The text was updated successfully, but these errors were encountered: