[Voyage-linux] Re: voyage-mpd and Ayre QB9

[Demian Martin]

My guess is that Ayre made some changes in the driver that may have effected
its operation with the current Linux code. We have tested the 1.0.23 and
1.0.24 code with the latest firmware from Gordon at Wavelength. The Ayre
firmware should be very similar. You may want to try the earlier 1.0.23
version of Alsa to see if it works any better. It’s a pain to setup, compile
and install the whole suite. You may only need to install the driver and
libs since the other stuff should work with either. To keep it simple and
quick just compile the USB audio drivers.

The only significant changes in .23 to .24 are:
ALSA: usb-audio: parse clock topology of UAC2 devices 
(Possibly the descriptors in the Ayre don't match here?)

.23 is where the USB audio class 2 stuff was introduced.
            -Demian

-----Original Message-----
From: Frank Lübeck [mailto:frank at luebecknet.de] 
Sent: Tuesday, May 03, 2011 6:11 PM
To: Demian Martin
Cc: voyage-linux at voyage.hk
Subject: Re: [Voyage-linux] Re: voyage-mpd and Ayre QB9

On Mon, May 02, 2011 at 03:13:48PM -0700, Demian Martin wrote:
> We have had good success with Voyage Linux, the latest Alsa (1.0.23 &
> 1.0.24) and The Wavelink from Wavelength that uses the same code for the
USB
> interface. Here is the specific section of MPD (again latest) that we use:
> 
> audio_output {
>        type          "alsa"
>        name          "USB"
>        device        "hw:1"    # optional
>        mixer_device  "hw:1"        # optional
>        mixer_control "PCM"         # optional
>        mixer_index   "0"           # optional
> }
> 
> This bypasses any other setup configs in the system and you may need to
> figure out the ID of the usb device, use aplay -l to identify it. This has
> worked well with any of the USB devices we have tried, however there are
> very few UAC2 devices in the world that do not use Gordon Rankin's code.
> Those that do I have been unable to get for testing yet.
>       Demian
>       Auraliti

I have tried that, but it didn't work. The problem seems to be that the
device it not correctly initialised. 
My guess is that this is a small problem for someone who knows the technical
details. But I'm still not sure if the error is in (the firmware of) the
device or in the Linux USB subsystem (or maybe the Linux USB audio drivers).

Frank