You are not logged in.

#1 2012-05-28 11:51:17

firewalker
Member
From: Hellas (Greece).
Registered: 2006-06-05
Posts: 455

[ANSWERED] Intel Graphics HD 3000, VLC & hardware acceleration issue.

I have a laptop with Core i3-2350M + HD 3000.

When I enable hardware acceleration for video playback I have 85~100% cpu usage on Core-0 and a frame rate of about 0.3~3 frames/s (depends form the video resolution).

Any ideas?

Vlc, Tools > Preferences > Inputs & Codes > Use GPU accelerated decoding.

vlc -v xxxx.mp4 (xxxx.mp4 an h.264 file):

VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
[0x8b7a8f0] main libvlc warning: cannot load module `/usr/lib/vlc/plugins/access/libaccess_gnomevfs_plugin.so' (libgnomevfs-2.so.0: cannot open shared object file: No such file or directory)                                                                                                                                                 
[0x8b7a8f0] main libvlc warning: cannot load module `/usr/lib/vlc/plugins/visualization/libprojectm_plugin.so' (libprojectM.so.2: cannot open shared object file: No such file or directory)                                                                                                                                                   
[0x8b7a8f0] main libvlc warning: cannot load module `/usr/lib/vlc/plugins/visualization/libgoom_plugin.so' (libgoom2.so.0: cannot open shared object file: No such file or directory)                                                                                                                                                           
[0x8b7a8f0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0xb6401620] mp4 stream warning: unknown box type btrt (incompletely loaded)
[0xb64030d0] mp4 demux warning: elst box found
[0xb64030d0] mp4 demux warning: CTTS table
[0xb5298408] avcodec decoder warning: threaded frame decoding is not compatible with ffmpeg-hw, disabled
[0xb52adb38] faad decoder warning: decoded zero sample
libva: VA-API version 0.33.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/i965_drv_video.so
libva: Found init function __vaDriverInit_0_32
libva: va_openDriver() returns 0
[0xb5298408] avcodec decoder: Using VA API version 0.33 for hardware decoding.
[0xaee06558] alsa audio output warning: device cannot be paused
[h264 @ 0xb529ff60] Cannot parallelize deblocking type 1, decoding such frames in sequential order

[0xaee06558] main audio output warning: PTS is out of range (-31232), dropping buffer
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 36 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 55 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 74 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 93 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 112 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 131 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 151 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 109 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 129 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 24 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 44 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 64 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 84 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 105 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 126 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 147 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 168 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 23 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 21 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 43 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 65 ms)
[0xaeaaf8c8] main video output warning: picture is too late to be displayed (missing 87 ms)

vainfo:

libva: VA-API version 0.33.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/i965_drv_video.so
libva: Found init function __vaDriverInit_0_32
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.33 (libva 1.1.0.pre1)
vainfo: Driver version: Intel i965 driver - 1.0.16.pre1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileH264Baseline           : VAEntrypointVLD
      VAProfileH264Baseline           : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD

Last edited by firewalker (2012-05-29 06:56:40)


Γίνε ρεαλιστής, μείνε ονειροπόλος ...

Offline

#2 2012-05-29 00:17:17

David Batson
Member
Registered: 2011-10-13
Posts: 640

Re: [ANSWERED] Intel Graphics HD 3000, VLC & hardware acceleration issue.

Haven't got vaapi working with vlc myself.  The problem seems to be with the ffmpeg plugin.  I have discovered several workarounds to eliminate video tearing in vlc (if that is your issue) depending upon the desktop manager that I use.  I use compiz for XFCE and KDE, and add an environment variable for Gnome.

https://bbs.archlinux.org/viewtopic.php … 9#p1018579

Offline

#3 2012-05-29 06:55:51

firewalker
Member
From: Hellas (Greece).
Registered: 2006-06-05
Posts: 455

Re: [ANSWERED] Intel Graphics HD 3000, VLC & hardware acceleration issue.

My video tearing hasn't to do with desktop managers. I start vlc on a "plain X" session and it is still there.

As for my card, I got my answer.

http://forum.videolan.org/viewtopic.php … 71#p342271


Γίνε ρεαλιστής, μείνε ονειροπόλος ...

Offline

#4 2012-05-29 07:37:42

Gusar
Member
Registered: 2009-08-25
Posts: 3,398

Re: [ANSWERED] Intel Graphics HD 3000, VLC & hardware acceleration issue.

firewalker wrote:

My video tearing hasn't to do with desktop managers. I start vlc on a "plain X" session and it is still there.

How is that not about desktop managers? smile. Actually, it's about window managers. Sandy Bridge can only get tear-free video through pageflipping. To get that, you need an opengl compositor, like Compiz.

I find it interesting though that VLC doesn't support vaapi with Sandy Bridge. VLC is supposed to be (or at least I saw it as) the flagship vaapi player. I guess part of the problem is that VLC copies frames back into system memory, while other players display them directly, without any copying.

Online

#5 2012-05-29 17:59:37

David Batson
Member
Registered: 2011-10-13
Posts: 640

Re: [ANSWERED] Intel Graphics HD 3000, VLC & hardware acceleration issue.

Sorry, had my terminology a little off (too lazy to verify at the time).  There's Desktop Environments (Gnome, KDE, XFCE and the like) and Window Managers (metacity, kwin, compiz, mutter and the like).  I should have said Desktop Enviroment instead of Desktop Manager.

Offline

Board footer

Powered by FluxBB