Lewis Pike <phaselocker@xxxxxxxxx> writes: > I am using an "m-audio fast track pro" usb sound card in conjunction > with ALSA version 1.0.23. I'm currently experiencing some problems > using this card's analog capture device. > > I am using the following command to test the capture device: > > arecord -c 1 -f cd -D plughw:1,1 test.wav > > This command usually works, and I am able to capture a clear audio > signal. However, on some invocations of arecord the captured signal > is heavily amplified with lots of digital clipping. Furthermore, once > this problem appears, subsequent invocations of arecord continue to > produce an amplified, heavily distorted signal until the usb device is > power cycled. Once the device is reset, the captured signal is at a > normal volume until the problem randomly occurs again. I haven't been > able to predict when the problem is going to occur but I'd guess that > the captured signal is distorted about five percent of the time. > > I'm new to ALSA. Can anyone shed some light on what might be > happening here? I'm also interested in hearing the experiences of > others who are using an m-audio fast track pro. > > .Lewis This is a follow-up to my initial email. I still have not been able to resolve the recording issues with my M-Audio Fast Track Pro and I wanted to give an update on where things currently stand. I've now noticed that when recording audio, I'm actually running into one of two problems: - Some recordings are extremely loud and distorted. - Some recordings sound like they were recorded in 8-bit with lots of hiss. Both issues only show up on some recordings. I did some more testing, and this time around I only used audacity for my test recordings. I'm finding that after resetting the Fast Track Pro, my recordings will sound clean, but it is only a matter of time before either one of the above issues presents itself. In both cases the problem persists on subsequent recordings until I reset the device. I can't predict when things will go wrong, but I do notice that if I switch the playback device in audacity's preferences between each recording, it seems to greatly increase the chances that either of these problems will occur. I've now tested this using arecord and audacity under both Arch Linux and Ubuntu and I'm seeing the same results. Given that these issues are not confined to one Linux distribution, I'm less inclined to believe that it's a configuration problem. I'm by no means an expert on digital audio, but both of these problems seem to somehow involve the issue of bit depth. Does anyone have any clue as to what might be happening here? .Lewis ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
