public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77677] HDMI audio on ati7750 choppy with ALSA multi-channel apps
Date: Fri, 02 May 2014 14:48:36 +0000	[thread overview]
Message-ID: <bug-77677-502-RofqIyLkg6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77677-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=77677

--- Comment #19 from Andy Furniss <adf.lists@gmail.com> ---
I've just changed my HD4890 for a R9 270x, which is roughly AIUI a 7870 and
have hit this issue.

Testing with mplayer I do have some differences, but would probably get duped
if I posted a new bug so -

Kernels tested drm-fixes -

3.15.0-rc2-41381-gabaafc0
3.13.0-rc6-14283-g61ef8be
3.12.0-rc7-01267-g3d3b78c

Both working and non working cases show the same alsa h/w params which is the
same as my old card which always worked eg.

access: RW_INTERLEAVED
format: S16_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 1024
buffer_size: 16384

With mplayer as long as there is video it seems to work OK (20 mins longest
test so far).

Pure audio files or "working" video played with -vc null always fail and sound
like the mp3.

-vo null without -vc null always works OK.

Only s/w decode works, UVD will produced trashed sound, so if that's the
default for xbmc it could be something worth testing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1903 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-05-02 14:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 20:03 [Bug 77677] New: HDMI audio on ati7750 choppy with ALSA multi-channel apps bugzilla-daemon
2014-04-19 20:04 ` [Bug 77677] " bugzilla-daemon
2014-04-19 20:06 ` bugzilla-daemon
2014-04-19 20:08 ` bugzilla-daemon
2014-04-20  1:25 ` bugzilla-daemon
2014-04-20 15:34 ` bugzilla-daemon
2014-04-20 16:36 ` bugzilla-daemon
2014-04-21  1:14 ` bugzilla-daemon
2014-04-21  1:15 ` bugzilla-daemon
2014-04-21  1:16 ` bugzilla-daemon
2014-04-22 16:36 ` bugzilla-daemon
2014-04-22 16:38 ` bugzilla-daemon
2014-04-22 16:42 ` bugzilla-daemon
2014-04-22 16:49 ` bugzilla-daemon
2014-04-25 14:36 ` bugzilla-daemon
2014-04-25 14:45 ` bugzilla-daemon
2014-04-25 14:45 ` bugzilla-daemon
2014-04-25 14:46 ` bugzilla-daemon
2014-04-25 14:47 ` bugzilla-daemon
2014-05-02 14:48 ` bugzilla-daemon [this message]
2014-05-02 21:19 ` bugzilla-daemon
2014-05-02 22:06 ` bugzilla-daemon
2014-05-04  1:51 ` bugzilla-daemon
2014-05-05 14:10 ` bugzilla-daemon
2014-05-05 14:53 ` bugzilla-daemon
2014-05-05 17:07 ` bugzilla-daemon
2014-05-05 18:25 ` bugzilla-daemon
2014-05-06 15:25 ` bugzilla-daemon
2014-05-06 19:07 ` bugzilla-daemon
2014-05-06 19:08 ` bugzilla-daemon
2014-05-09 16:59 ` bugzilla-daemon
2014-05-10 14:01 ` bugzilla-daemon
2014-05-10 14:11 ` bugzilla-daemon
2014-07-07 22:04 ` bugzilla-daemon
2019-11-19  8:48 ` bugzilla-daemon

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=bug-77677-502-RofqIyLkg6@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox