-
Notifications
You must be signed in to change notification settings - Fork 373
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
Qualified ALSA device names break opening of ALSA control device #60
Comments
Since Ardour3 preferentially uses ALSA card names instead of numbers, and also qualifies the device with the device number, this means that Ardour3 cannot start Jack2 under its own control with the ALSA backend. |
What about git version? Nedko any idea? Thanks. Stéphane Le 18 févr. 2014 à 18:33, pauldavisthefirst notifications@github.com a écrit :
|
I think this is fixed more than a year ago, with b3394f4 |
the jack1 version is actually a port from jack2, see e02d7358da82a84647cb5cd71de23a75640ef506 |
1.9.8 does not appropriately handle ALSA device names when attempting to open the control device.
If the device name is given as "hw:PCH,0", the same name is used to try to open the control device. this will fail, because the name should be "hw:PCH".
The following code from jack1 takes a PCM device name and returns the appropriate control device name:
static char*
get_control_device_name(const char * device_name)
{
char * ctl_name;
const char * comma;
}
The text was updated successfully, but these errors were encountered: