Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
On 2010-05-25 01:26, Lennart Poettering wrote: On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. AFAIK this sound card is just using the standard USB Audio drivers. I don't have access to this particular hardware either, so I'm not in a position to debug the drivers ATM. So I can't answer your question and my guess is that it varies between hardware revisions. Perhaps David Kågedal, who wrote the initial profile, knows more about this? // David ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
David Henningsson launchpad@epost.diwic.se writes: On 2010-05-25 01:26, Lennart Poettering wrote: On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. AFAIK this sound card is just using the standard USB Audio drivers. I don't have access to this particular hardware either, so I'm not in a position to debug the drivers ATM. So I can't answer your question and my guess is that it varies between hardware revisions. Perhaps David Kågedal, who wrote the initial profile, knows more about this? I haven't seen it switch between device IDs, so I have no idea. But I didn't really use it a lot with my linux machine, so the testing has been light. But it worked without problem. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss