OK, I undertand First of all, I am very happy with the patch you wrote, that just solved the most annoying issue for me, that was the synchronization problem. Second, I did as you instructed with the USB sniffer. I opened the emu control panel (the interface was set to 48kHz), saved the current log file (as log1), set the rate to 96kHz, again saved the current log file (as log2). I diff'ed the 2 files, resulting in a third section, 170 lines. If you are interested in debugging the rate control, I can attach the diff file (or the original logs, if necessary). Will this list allow mail attachments? Of course, I am willing to test anything you like, if you are willing to further debug this. Thanks, Adi On Tue, Feb 26, 2008 at 4:21 PM, Clemens Ladisch <clemens@xxxxxxxxxx> wrote: > Adrian Stancu wrote: > > I see, you say that the device knows what sample rate it is supposed > > to use, and that this rate should be automatically used. > > Not automatically, the driver sets an alternate setting in set_format() > by calling usb_set_interface(). > > > ... > > > 2) I logically connect the device to the virtual machine, set the > > sampling rate to 96k through the creative supplied drivers, > > Apparently, that driver uses some vendor-specific request to configure > the device. To find out what exactly that driver does, you'd have to > use a tool like usbsnoop to record the USB requests. > > > Regards, > Clemens > _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
