[alsa-devel] snd-usb-audio syncronisation problem
adrian.stancu.82 at gmail.com
Tue Feb 26 13:53:45 CET 2008
I see, you say that the device knows what sample rate it is supposed
to use, and that this rate should be automatically used. However, in
practice, I guess this does not happen for some reason. For the
recording part, the things stay exactly like for playback, i.e. the
recorded sound is correct as long as the device is (manually, through
another OS) set to the sampling rate at which the recording is made.
Let me give a few examples:
1) I power on the device, and it automatically picks 48k. If i try
playing back something at any other rate (44.1k, 96k etc), the sound
is very distorted.
2) I logically connect the device to the virtual machine, set the
sampling rate to 96k through the creative supplied drivers, disconnect
(WITHOUT powering it off), reload the snd-usb-audio module in Linux.
Now, I can achieve correct playback only at 96k. Anything else is
Of course, I can resample anything on-the-fly (through additional
device in ~/.asoundrc) to match the sampling rate of the device and
get normal sound.
As an additional note, recording at 192k seems *completely* broken. I
mean, If I record at 96k while the device was just powered on (i.e.
set to 48k), there is still a connection between the original and the
recorded sounds. However, at 192k, it looks just like pure noise, at
-- recorded at 96kHz
-- recorded at 192kHz
In both cases, the sound fed to the input was a simple 41.2Hz tone.
On Tue, Feb 26, 2008 at 1:36 PM, Clemens Ladisch <clemens at ladisch.de> wrote:
> Adrian Stancu wrote:
> > I wanted to mention that (from what I noticed until now), it is not
> > possible to get correct playback on this device unless the sampling
> > frequency it is set to (it defaults to 48k when powered on) matches
> > the sampling frequency of the audio stream you send to it. So how is
> > this supposed to work, if the device is set to 48k and my stream has
> > 192k (and I cannot set the device to 192k)?
> The alternate setting of the interface is supposed to set the sampling
> frequency, and this is exactly what the driver does.
> The returned frequency value is correct, so it seems the device knows
> that it is supposed to run at 192 kHz.
> Does recording work with all sample rates?
More information about the Alsa-devel