Re: [alsa-devel] Audio-gd NFB-17.32 (VIA VT1731)

Re: [alsa-devel] Audio-gd NFB-17.32 (VIA VT1731)

[Clemens Ladisch]

Torstein Hegge wrote:
> I think we can conclude that the VIA VT1731 has the same issue as the
> C-Media CM6631.
>
> I'll add the VT1731 as one of the devices that needs a reset after
> sample rate change in the next iteration of the sample rate workaround
> patch.

Why not just do it for all UAC 2 devices?


Regards,
Clemens

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar

Re: [Alsa-user] Audio-gd NFB-17.32 (VIA VT1731)

[Torstein Hegge]

On Mon, Mar 25, 2013 at 08:38:16 +0100, Clemens Ladisch wrote:
> Torstein Hegge wrote:
> > I think we can conclude that the VIA VT1731 has the same issue as the
> > C-Media CM6631.
> >
> > I'll add the VT1731 as one of the devices that needs a reset after
> > sample rate change in the next iteration of the sample rate workaround
> > patch.
> 
> Why not just do it for all UAC 2 devices?

If new devices that needs this just keeps popping up, that might indeed
be the better solution.


Torstein

Re: [alsa-devel] Audio-gd NFB-17.32 (VIA VT1731)

[chris hermansen]

Torstein, Clemens, list:

On Mon, Mar 25, 2013 at 6:48 AM, Torstein Hegge <hegge@resisty.net> wrote:
> On Mon, Mar 25, 2013 at 08:38:16 +0100, Clemens Ladisch wrote:
>> Torstein Hegge wrote:
>> > I think we can conclude that the VIA VT1731 has the same issue as the
>> > C-Media CM6631.
>> >
>> > I'll add the VT1731 as one of the devices that needs a reset after
>> > sample rate change in the next iteration of the sample rate workaround
>> > patch.
>>
>> Why not just do it for all UAC 2 devices?
>
> If new devices that needs this just keeps popping up, that might indeed
> be the better solution.

For what my opinion is worth, this seems like the ideal solution to
me.  It doesn't seem to introduce much additional overhead and it
improves the behaviour of two interfaces / three physical devices of
which we are aware.

Is it worth testing such a "universal" application against devices
known to work without it?  Do any of us have such a device?


--
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar