On Sun, May 08, 2011 at 08:18:39PM +0200, Jan Stary wrote: > On May 07 12:21:30, Alexandre Ratchov wrote: > > On Sat, May 07, 2011 at 10:52:09AM +0200, Jan Stary wrote: > > > > > > I just bought me the "new" M-Audio USB MobilePre (MK-II): > > > > > > uaudio0 at uhub2 port 2 configuration 1 interface 0 "M-Audio MobilePre" > > > rev 1.10/10.00 addr 2 > > > uaudio0: audio rev 1.00, 0 mixer controls > > > audio0 at uaudio0 > > > > > > Indeed, 'mixerctl -a' shows nothing; but > > > aucat -u -C 0:1 -e s24le -r 48000 -o in.wav > > > seems to be recording anyway (and the sound > > > is very good). > > > > Cool. > > Is it OK for an uaudio(4) device to have 0 mixer controls?
absolutely. > I can control the respective inputs/outputs with the device's (hardware) > knobs, but having 0 (software) mixerctl variables still seems a bit strange. > Is it possible that the device really has 0 controls to expose via USB > audio (and uaudio just correctly reports that), or is this a sign that > the dovice is not fully supported (or possibly not class-compliant)? if there are hardware controls, then there probably aren't software controls. they would sorta conflict otherwise, no? > What would be the correct way to find out what the device can physically do? > All I know about is .../cap.c somewhere in the audio source tree. Is there > a 'real' tool, exposed and documented? faq 13.1. hmm, maybe that should also have an explicit example of '$ audioctl encodings'. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
