From: Forest Bond Subject: Re: VT1708 clicks & pops Date: Wed, 21 Sep 2011 11:46:15 -0400 Message-ID: <20110921154615.GJ1223@alittletooquiet.net> References: <20110916203601.GD8309@alittletooquiet.net> <20110919231413.GD1223@alittletooquiet.net> <20110920190534.GF1223@alittletooquiet.net> <20110921143510.GG1223@alittletooquiet.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5701094569115849028==" Return-path: Received: from storm.alittletooquiet.net (storm.alittletooquiet.net [67.23.28.199]) by alsa0.perex.cz (Postfix) with ESMTP id 2210E243C1 for ; Wed, 21 Sep 2011 17:46:18 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org --===============5701094569115849028== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L1c6L/cjZjI9d0Eq" Content-Disposition: inline --L1c6L/cjZjI9d0Eq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Takashi, On Wed, Sep 21, 2011 at 04:43:15PM +0200, Takashi Iwai wrote: > At Wed, 21 Sep 2011 10:35:10 -0400, > Forest Bond wrote: > >=20 > > Hi Takashi, > >=20 > > On Wed, Sep 21, 2011 at 10:39:44AM +0200, Takashi Iwai wrote: > > > At Tue, 20 Sep 2011 15:05:34 -0400, Forest Bond wrote: > > > > On Tue, Sep 20, 2011 at 09:22:23AM +0200, Takashi Iwai wrote: > > > > > At Mon, 19 Sep 2011 19:14:13 -0400, Forest Bond wrote: > > > > > > On Fri, Sep 16, 2011 at 04:36:01PM -0400, Forest Bond wrote: > > > > > > > I have two boards with a VT1708: > > > > > > >=20 > > > > > > > * VIA EPIA EX15000G > > > > > > > * VIA VB8002 > > > > > > >=20 > > > > > > > I'm using VLC to play audio via PulseAudio to the analog outp= uts. The VB8002 > > > > > > > sounds great, but the EX15000G has random pops and clicks in = the output. Both > > > > > > > machines are running exactly the same configuration (they are= using the same > > > > > > > pre-built OS image). > > > > > >=20 > > > > > > Maybe this issue would be more approachable if I could produce = it without > > > > > > PulseAudio involved? > > > > >=20 > > > > > Yes. > > > >=20 > > > > Heh, I guess I'm probably not going to be able to do that very easi= ly. > > > >=20 > > > > > > Incidentally, these boards both produce a crackling/static soun= d when PulseAudio > > > > > > is playing and the PCM mixer is turned all the way down. I hav= e seen scattered > > > > > > reports of this in various bug trackers. The problem does not = occur when > > > > > > playing via alsa directly. One thing I have noticed is that th= e crackling noise > > > > > > follows the rhythm of the music being played. It actually soun= ds like the music > > > > > > has been heavily distorted (i.e. via extreme digital clipping) = and then > > > > > > attenuated significantly. > > > > > >=20 > > > > > > It seems likely that there are driver issues that PulseAudio is= exposing. What > > > > > > can I do to track them down? > > > > >=20 > > > > > Is the problem related with the driver version? You mentioned the > > > > > difference of drivers installed on your systems. > > > > > If it's a regression of the driver, it'd be easier to figure out. > > > >=20 > > > > No, the issue occurs with both driver versions. > > > >=20 > > > > > Other than that, I'd try to adjust PA, e.g. try tsched=3D0. Usua= lly > > > > > this kind of problem is because of inaccurate playback position > > > > > reporting from the hardware. PA relies (too much) on the playback > > > > > position as default. > > > >=20 > > > > Using tsched=3D0 fixes the pops and clicks on the EX15000G. Any id= ea why I might > > > > see problems on one board but not the other given how similar they = are? > > >=20 > > > Do they have the same HD-audio controller chip (VIA one)? > > > Usually it's an issue of controller chip, not codec chips, so I wonder > > > if they behave differently even with a same controller. > >=20 > > I'm not really sure how to identify the controller chip. alsa-info.sh = output is > > here: > >=20 > > EX15000G: > > http://www.alsa-project.org/db/?f=3Dea56226a7917391d6adf9078650d3a9395f= 51b17 > >=20 > > VB8002: > > http://www.alsa-project.org/db/?f=3D611cc772a3fab7552bbda193b6ad7998f66= a60fb > >=20 > > As I understand it the VT1708 is the codec chip. Is the audio controll= er part > > of the south bridge? Both report having a VT8237. >=20 > Yes, and it's VT1708 also meaning a controller chip, apparently. > The controller chip is what PCI ID shows. >=20 >=20 > > > > The crackling with PCM volume set to 0 persists with tsched=3D0. > > >=20 > > > Hrm, which PA version are you using? I remember vaguely a buggy PA > > > SIMD operations in some old PA versions. > >=20 > > 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 from Ubuntu Lucid. > >=20 > > > Also, when you mute the mixer (nor the PA's mixer), e.g. via > > > "alsamixer -c0", the noise goes away, right? > >=20 > > I do not use the PA mixer. The noise is present with ALSA's PCM contro= l set to > > zero (-51dB). If I move the PCM control up one tick (to -50.8dB) the n= oise goes > > away. >=20 > OK, then it's an issue in the sound driver. > Could you give alsa-info.sh outputs both mute-with-noise and without > noise for comparison? With noise: http://www.alsa-project.org/db/?f=3Dc8119c27951479731f1ba6d8ea62cd3ad91aec1a Without noise: http://www.alsa-project.org/db/?f=3Df40d02f0286a64946bec2ff4243c15ea86e5ea59 > > > > It seems unlikely that this isn't driver or hardware issue. But fi= xing the > > > > pops and clicks without using tsched=3D0 is more important to me. = If you can > > > > provide suggestions as to where I might start looking, I would be h= appy to > > > > try and come up with a fix. > > >=20 > > > As mentioned, the usual problem is the inaccurate DMA position > > > reporting, especially when tsched=3D0 helped. It means a problem of > > > HD-audio controller. We have already many workarounds in the driver > > > code, but more investigations are needed in such a case... > >=20 > > Again, I'm happy to spend the time needed to get this fixed. If you ca= n provide > > hints on where to look, that would be great. Can you point me at some = git > > commits that fixed similar issues? I checked the git log but did not f= ind any > > such commits that changed patch_via.c. >=20 > Well, there are a few possible causes. If it's something wrong in the > codec side, it can be a PM code. The latest driver has a mixer enum > "Dynamic Power-Control". Try to disable it. Okay, I'll give this a try. > OTOH, if it's in the controller side, where you need to take a look at > is hda_intel.c, or sometimes hda_codec.c. Thanks for the info. -Forest --=20 Forest Bond http://www.alittletooquiet.net http://www.rapidrollout.com --L1c6L/cjZjI9d0Eq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk56BscACgkQRO4fQQdv5Aw66ACfe3c5Q8r+IZOzwYRHgjzMACWv ZdAAnR7XtW1+5zTH+DWznV8G0PHGh1ko =ur28 -----END PGP SIGNATURE----- --L1c6L/cjZjI9d0Eq-- --===============5701094569115849028== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============5701094569115849028==--