All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [a52] Strange behavior with 5.1 surround on ALC1220
Date: Wed,  5 May 2021 09:01:07 +0200 (CEST)	[thread overview]
Message-ID: <20210505070107.37255F8025F@alsa1.perex.cz> (raw)
In-Reply-To: <1620198054870762110-webhooks-bot@alsa-project.org>

alsa-project/alsa-plugins issue #21 was edited from davidebeatrici:

I originally encountered the issue ~1 year ago, when I started using a motherboard with an ALC1120 on it.

The out-of-box experience was flawless: I simply connected the optical SPDIF cable to my amplifier/receiver and stereo sound immediately worked.

Once I switched to 5.1 surround, audio output became extremely fast; even videos were affected by it, to the point that they were being reproduced in seconds instead of minutes.

After a few days of research and experiments I managed to workaround the issue by replacing the content of `60-a52-encoder.conf` with:
```
pcm.a52 {
	@args [CARD]
	@args.CARD {
		type string
        }
	type rate
	slave {
		pcm {   
			type a52
			card $CARD
		}
		rate 48000
	}
}
pcm.pulse {
	type pulse
}
ctl.pulse {
	type pulse
}
pcm.!default {
	type pulse
}
ctl.!default {
	type pulse
}
```

Based on https://help.ubuntu.com/community/DigitalAC-3Pulseaudio#Configuring_asound.conf.

After that, I wanted to investigate the cause and report my findings to either ALSA or PulseAudio (depending on the results).

Unfortunately that never happened and I kinda forgot about it, as [libasound2-plugins](https://packages.debian.org/bullseye/libasound2-plugins) was updated a single time in the past year and thus I only had to replace the file's content once more.

Fast-forward to today: I switch from PulseAudio to PipeWire and while troubleshooting https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1143 I decided to try to restore the original file.

Interestingly, the behavior is different compared to PulseAudio: audio, instead of being fast, is crackling. It's basically as if a frame every two is being skipped.

Unfortunately PipeWire reports no errors whatsoever.

Issue URL     : https://github.com/alsa-project/alsa-plugins/issues/21
Repository URL: https://github.com/alsa-project/alsa-plugins

       reply	other threads:[~2021-05-05  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1620198054870762110-webhooks-bot@alsa-project.org>
2021-05-05  7:01 ` GitHub issues - edited [this message]
     [not found] <1620198062166485071-webhooks-bot@alsa-project.org>
2021-05-05  7:01 ` [a52] Strange behavior with 5.1 surround on ALC1220 GitHub issues - edited

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210505070107.37255F8025F@alsa1.perex.cz \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.