Skip to content
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

avoid hard-coding audio devices? #24

Closed
wkearney99 opened this issue Apr 11, 2014 · 3 comments
Closed

avoid hard-coding audio devices? #24

wkearney99 opened this issue Apr 11, 2014 · 3 comments

Comments

@wkearney99
Copy link

There's a couple of places where aplay is used and it's hard-coded to use hw:1,0.

Could you change that to just use aplay without specifying the device? That'd make it a bit more flexible with what hardware it could use. As in, I've got mine setup with a monitor attached via HDMI (which shows up as hw:0,0). That and in a setup that might use different speaker setups the output might be on any number of other device numbers.

It's possible in ~/.asoundrc to configure the default channels for alsa.

This also applies to the recording device.

Otherwise we have to wander down the rat hole of trying to cajole linux into supplying fixed device numbers. No good ever comes from that effort, especially not if ANYTHING is on a USB connection.

Abstract the code away from hard-coded devices, please?

@gries
Copy link

gries commented Apr 12, 2014

Hi, I'm currently setting up jasper, have you managed to set it up using HDMI + Monitor? And if yes can you give me a hint on how you achieved it?
also 👍 for diffrent audio-setups

@ozett
Copy link

ozett commented Apr 17, 2014

yes, please elaborate more on choosing different audio-konfigurations for input/output.
a have the default image, and getting output from hdmi-monitor-speakers while taking input from mic of my plantronics-usb-headset. i would like to configure different audio-outputs and getting jasper to work with same audio-out which uses mpd on my raspberry. more info to audio-configurations would be a great help. What about a wiki?

@charliermarsh
Copy link

Consolidating this with #16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants