dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68792] Problems during playback of h264 files using UVD and VLC on AMD E-350 CPU
Date: Mon, 14 Oct 2013 08:49:02 +0000	[thread overview]
Message-ID: <bug-68792-502-2jlbIFGPmu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68792-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Grigori Goronzy <greg@chown.ath.cx> ---
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > (In reply to comment #5)
> > > > You have to enable VDPAU output as well.
> > > 
> > > Sorry, but where and how?
> > > In VLC?
> > > *.conf file?
> > >
> > 
> > In preferences go to the "Video" tab and select VDPAU from the list of
> > outputs.
> 
> I didn't have VDPAU, there.
> That's why I'm asking.
> Have a look at my attachments.
> VDPAU is only enable under "Input/Codecs".
> Is my VLC version missing something?
>

Yes, you do not have VDPAU video output support enabled in your VLC build. You
may need a newer version (>= 0.6) of libvdpau and recent VLC master.

> 
> With that I get only every several seconds one frame but good audio.
> 
> lib/gallium> vlc /data/Filme/Serenity\ -\ HD\ DVD\ Trailer.mp4
> VLC media player 2.1.0 Rincewind (revision 2.1.0-0-gedd8835)
> [0x8a94290] main interface error: no suitable interface module
> [0x89973f8] main libvlc error: interface "globalhotkeys,none" initialization
> failed
> [0x89973f8] main libvlc: VLC wird mit dem Standard-Interface ausgeführt.
> Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
> [0xb4a306c0] avcodec decoder: Using G3DVL VDPAU Driver Shared Library
> version 1.0 for hardware decoding.
> [0xb4a306c0] avcodec decoder: Using G3DVL VDPAU Driver Shared Library
> version 1.0 for hardware decoding.
> [0xb4a402f0] main vout display error: Failed to resize display
> [0xb4a306c0] avcodec decoder error: more than 5 seconds of late video ->
> dropping frame (computer too slow ?)
> [0xb4a306c0] avcodec decoder error: more than 5 seconds of late video ->
> dropping frame (computer too slow ?)
> [0xb4a306c0] avcodec decoder error: more than 5 seconds of late video ->
> dropping frame (computer too slow ?)

Please try again with latest Mesa, updated patches have been committed. I can
play high-bitrate 1080p files without any framedrops and reasonable CPU load
(~40-50%) on an E-450 now, even without VDPAU video output, which means that
the inefficient readback path is used. With VDPAU video output enabled on VLC
master, CPU usage is much lower.

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

[-- Attachment #1.2: Type: text/html, Size: 3645 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:[~2013-10-14  8:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 13:32 [Bug 68792] New: Problems during playback of h264 files using UVD and VLC on AMD E-350 CPU bugzilla-daemon
2013-10-06 12:19 ` [Bug 68792] " bugzilla-daemon
2013-10-08 17:20 ` bugzilla-daemon
2013-10-08 18:40 ` bugzilla-daemon
2013-10-09 14:50 ` bugzilla-daemon
2013-10-09 16:27 ` bugzilla-daemon
2013-10-10  1:27 ` bugzilla-daemon
2013-10-10 11:22 ` bugzilla-daemon
2013-10-11  2:33 ` bugzilla-daemon
2013-10-11  2:37 ` bugzilla-daemon
2013-10-11  2:38 ` bugzilla-daemon
2013-10-14  8:49 ` bugzilla-daemon [this message]
2013-11-19  6:38 ` bugzilla-daemon
2013-11-19  6:39 ` bugzilla-daemon
2013-11-19  6:39 ` bugzilla-daemon
2015-04-13  3:00 ` bugzilla-daemon
2019-09-18 19:05 ` 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-68792-502-2jlbIFGPmu@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;
as well as URLs for NNTP newsgroup(s).