Description of problem: ======================= Audacity 2.0.2 is unable to record from an Ion MixMeister external soundcard though earlier releases had no problem. It appears that 2.0.x versions need a USB audio codec which is either missing or non-functional. On this machine (a Lenovo Thinkpad R61i) a number of sound sources are offered. With software playthrough ON I get the following results from the possible 'Input Device' choices: - HDA Intel Conexant Analog (hw:0,0): produces clean silence - USB Audio codec: Audoo codec (hw:1,0): an initial full volume POP followed by both meters dropping to zero. If Audacity is started with the USB soundcard is disconnected, this entry does not appear in the 'Input Device' list, so evidently Audacity knows the device exists but can't accept input from it. - sysdefault produces clean silence - pulse, default both produce very low volume crackling (L channel at -20dB, R channel at -26dB estimated) There are no other choices, which is odd because on the 'Audacity Device ToolBar' the 'Audio host: selection is locked on 'ALSA' Version-Release number of selected component (if applicable): 2.0.2 ============================================================= How reproducible: Impossible to avoid. ================= Steps to Reproduce: =================== 1. Plug in the Ion Mixmeister 2. Start Audacity 3. ALSA is the only 'Audio host' available and the choices of 'Input device' give the results shown above. Previous versions of Audacity and/or Fedora used to work with the Conexant Analogue device selected. Actual results: As described above. =============== Expected results: A recording made from the analogue source. ================= Additional information: ======================= The audio outout and meter display are the same regardless of any analogue input to the external sound card and is unaffected by disconnecting the sound card: this is what makes me think that the USB codec is either missing or is failing to pass the audio stream to Audacity.
Is the card a surround or multichannel card ? Does lsusb see it (post the relevant part)? Does lsmod before and after plug show driver loaded (which) ? Is lsusb/lsmod the same running the earlier release ? Which kernel is running ? Is there any earlier F17 kernel where this worked ? Is there an earlier Audacity version that worked on F17 ? As you might guess, I suspect kernel / usb / module load issue, and the above might help narrow it down...
The card is an input-only stereo device capable of accepting line level or moving coil phono cartridge input. It uses a Burr-Brown ADC and, apart from the line/phono switch only has a recording level control: it is superficially a very simple device. $ lsusb Bus 004 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 005 Device 011: ID 08bb:2900 Texas Instruments Japan PCM2900 Audio Codec Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub the output from "lsusb -s 005:011 -v" (1270 lines) is attached. lsmod output: see attached files lsmod_attached.txt and lsmod_not_attached.txt Is lsusb/lsmod the same running the earlier release? Pass the previous usage was probably with Fedora 15 which is not currently installed. The current kernel as running when I first reported the bug: $ cat /proc/version Linux version 3.7.3-101.fc17.i686.PAE (mockbuild.fedoraproject.org) (gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC) ) #1 SMP Fri Jan 18 17:47:17 UTC 2013 I don't think I was on F17 when I last successfully used this device. I only ever use Audacity with this device, the Ion Mixmeister. I'm fairly certain that the previous version of Audacity was 1.38.
Created attachment 696596 [details] lsusb output for the ion MixMeister
Created attachment 696597 [details] lsmod output with the Ion MixMeister attached to the PC
Created attachment 696598 [details] lsmod output with the Ion Mixmeister disconnected from the PC This attachment was produced by the command sequence: $ sudo modprobe -r snd_usb_audio $ lsmod >lsmod_not_attached.txt which was run after the 'lsmod_attached.txt' attachment had been produced.
Forgot to include 'lsusb' o/p with the Ion Mixmeister disconnected. Here you go: $ lsusb Bus 004 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Could you check out the ~recording test~ info on the alsa web site [1], and see if the driver/alsa can actually record with your hardware ? 1. http://www.alsa-project.org/main/index.php/SoundcardTesting
I looked at the 'recording test' info and ran the tests. I learnt a bit, but didn't find anything out that pointed at any particular problem. In particular I didn't (and still don't) understand why Audacity would sit there with constant (but different) sound levels shown on the 'VU meters' in the tool bar which I'd expect to be audible but still show flatlines in the recorded level. After visiting my local electronics store I've just I built an adapter box that lets me connect headphones to line level phono plugs. I was able to trace the analog signals from my preamp's 'tape out' socket, sort out some problems with a rather elaborate switching box, and prove that analog signals now arrive at the Mixmeister's inputs. Audacity and the Mixmeister now appear to be working with the USB driver. The 'VU meters' are doing the right thing too. Over the next day I'll digitise an album as a full system check and will report the result. Apologies in advance if this bug report appears to have been deeply flawed.
Digitising the album worked OK. Audacity split it into tracks and the result sounded as I expected it to. I think this bug can be safely closed as Solved/Operator Error and removed from Bugzilla. Apologies to anybody whose time was wasted by this.
(In reply to comment #8) > In > particular I didn't (and still don't) understand why Audacity would sit > there with constant (but different) sound levels shown on the 'VU meters' in > the tool bar which I'd expect to be audible but still show flatlines in the > recorded level. I have sometimes seen Audacity showing the record VU fixed (fairly high vibrating) level with nothing plugged in, or the wrong e.g. digital input selected. It might also occur when two audio sub systems are trying to access the device. In any case, thanks for tracking down your issue. Closing as requested.