libdvdcss2 (skip if you don’t need DVD playback)
also
libdvdcss2
Kaffine and Xine still did not performing as require
Radeon driver used with ATI-HD-3200 graphics,
– lots of frames dropped and random green and blue screens
Radeon driver used with ATI-HD-4250 graphics,
– lots of frames dropped, blank selection screen at start sometimes,
– but mouse pointer detected where selections were
Updated vlc, no problems found, so deleted Xine and Kaffeine
Deleted the above listed packages as indicated,
if not required from above list
nb. with respect to package list
=> left installed due to dependencies/necessity
< => deleted
same Kaffeine problem, OpenSuse 12.3 64bit. Looked like xine dependency problem; xine freezing. Received this line in terminal:
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
vo_vdpau:
Can't create vdp device : No vdpau implementation.
Installed package libvdpau_600 , kaffeine now displays video … bad quality playback/choppy, but no freeze.
Well, VDPAU is originally an NVIDIA thing, it doesn’t work too well on ATI/AMD cards and libvdpau_r600 is still experimental AFAIK (they have VAAPI instead, which is supported as well by xine in the latest version).
And apparently xv doesn’t work on your card, because xine takes xv if VDPAU is not available.
So look for a line “video.driver:” in the file ~/.kde4/share/apps/kaffeine/xine-config (for xine-ui it would be ~/.xine/config) and try to set it to the different values.
Or you could try to enable glamor, maybe xv works better then.
To do this, create a file /etc/X11/xorg.conf.d/20-glamor.conf with this content:
it doesn’t work too well on ATI/AMD cards
false … <facetious mode> in fact, it works so poorly, that the AMD devs working on the OSS driver stack have chosen it (VDPAU) as the means to utilize UVD </facetious mode> lol!
and libvdpau_r600 is still experimental AFAIK
In this context it refers to using the gallium vdpau state tracker on the applicable hardware and to conduct the accel and presentation work via shaders. For that, and in its present form, it is very limited in its abilities and is buggy, so, yes, experimental would be an appropriate tag. And such contextual usage is very, very unlikely to be developed any further (though anyone could if they so pleased) given that support (i.e. code) for utilizing the UVD engine has now been inserted.
And apparently xv doesn’t work on your card, because xine takes xv if VDPAU is not available.
So look for a line “video.driver:” in the file ~/.kde4/share/apps/kaffeine/xine-config (for xine-ui it would be ~/.xine/config) and try to set it to the different values.
Indeed, I’m wondering if the setting has been changed from the default “auto” to specifying “vdpau”, or whether there is a greater issue at play … Xv should work just fine for the hardware mentioned by both users reporting the playback issue … they should check to make sure they have libXv installed (and if so, xvinfo as well, and then run it to see if if reports any problems)
Or you could try to enable glamor, maybe xv works better then.
glamor does not currently contain Xv support … adding it is actually a GSoC2013 project … in any regards, this hardware is better served by standard EXA … (though, whether you’d run up against situations in which the former provides much inferior performance, and whether you’d actually be able to perceive that is another matter … but still, its relative immaturity is a genuine argument/knock against it)
Hm? Of course I meant the current state with VDPAU “emulation” via libvdpau_rx00.
I don’t know how far the UVD support in the radeon driver is though.
If the driver natively supports the VDPAU interface I see no reason why xine’s “vdpau” backend shouldn’t work on AMD cards as well.
Indeed, I’m wondering if the setting has been changed from the default “auto” to specifying “vdpau”, or whether there is a greater issue at play …
That was my first thought as well, but I tested it. Even if you explicitely set “vdpau” xine does take another output backend if VDPAU isn’t available. And it isn’t on my Radeon 9600… (I don’t have libvdpau_r300 installed)
glamor does not currently contain Xv support … adding it is actually a GSoC2013 project …
Ah, ok. Sorry, didn’t know that.
I thought Xv acceleration was the main point of glamor…:shame:
So it only supports XRender acceleration at the moment?
It supports all devices with UVD2 and greater (save for a few chipsets for whom its currently problematic, but for whom its also being looking into to extended said support too). You need the DRM that is going into 3.10, a recent Mesa build (itself built with the vdpau supports), and the appropriate uvd firmware for your device, (and likely an updated libdrm for the mesa build). Lastly, app support.
That was my first thought as well, but I tested it. Even if you explicitely set “vdpau” xine does take another output backend if VDPAU isn’t available. And it isn’t on my Radeon 9600… (I don’t have libvdpau_r300 installed)
ahh, okay, thanks.
I thought Xv acceleration was the main point of glamor…:shame:
So it only supports XRender acceleration at the moment?
The main point of glamor is being a generic means of providing EXA (by way of OpenGL) … its useful in that you don’t have to work up a full blown DDX (or add such support for newer hardware into an existing one) and, instead, can focus on development on the 3D driver
Thanks for the info.
But this thread is about openSUSE 12.3 so this won’t help the OP then, I 'm afraid…
The main point of glamor is being a generic means of providing EXA (by way of OpenGL) … its useful in that you don’t have to work up a full blown DDX (or add such support for newer hardware into an existing one) and, instead, can focus on development on the 3D driver
I knew that glamor is 2D acceleration over OpenGL but I didn’t know what it supports exactly.
I know now that it is mainly EXA support via OpenGL.
And EXA is just about XRender, isn’t it?
At least it’s initial goals were, according to Wikipedia:
Indeed, it was primarily informational … though I will counter the later with a “since when does running 12.3 prevent a user from upgrading to those components I mentioned”
[quote]The main point of glamor is being a generic means of providing EXA (by way of OpenGL) … its useful in that you don’t have to work up a full blown DDX (or add such support for newer hardware into an existing one) and, instead, can focus on development on the 3D driver
I knew that glamor is 2D acceleration over OpenGL but I didn’t know what it supports exactly.
I know now that it is mainly EXA support via OpenGL.[/quote]Two items to add:
first, a correction. I was wrong, as Glamor is apparently “based on UXA’s framework actually”
second, to expand upon the prior description and to add a further point towards the benefit that glamor can provide:
[LIST]
EXA doesn’t support all of Render’s features … so the operations end up getting done in software … an amusing side-story is that the former XAA only acceled a couple of features, but shortly after the intro of EXA, and during XAA’s period of coexistance alongside the newer EXA, even those limited capabilities ended up bit rotting and, hence, XAA effectively became useless and no different then shadowfb
I don’t know a lot about UXA, but know that Intel’s original motivation was in part to rework how EXA worked (in relation to pixmap migration; it was removed) … they would later realize that that design decision was wrong … and along came SNA, which is similar to EXA in so far as that it once again contained a pixmap migration strategy.
In order to get EXA to properly support more Render ops, access to the 3D engine’s shaders would be required, which means that a whole lot of devel effort would need to be expended to build the DDX up … SNA provides just that – it utilizes shaders to accel the Render operations (and Intel/Chris Wilson, continues to improve upon this).
And now, getting to the point about glamor – it allows you to leverage the development work on the 3D driver for the hardware to achieve the desired end result, as well as providing support for more of Render features (and for any future improvements to the protocol) … i.e. all of this by essentially doing Render on top of OpenGL
[/LIST]
And EXA is just about XRender, isn’t it?
At least it’s initial goals were, according to Wikipedia:
Yep. One of the side benefits under it is that its use of offscreen memory for acceling Render ops also is an available feature for video playback (i.e. Xv rendering can also make use of offscreen memory)
As a tack on comment to this statement – (though it is not explicitly stated in the commit) it now appears as if VA API will, in the future, also realize this functionality as well: [Mesa-dev] Initial VA-API state tracker](http://lists.freedesktop.org/archives/mesa-dev/2013-June/040742.html)
Edit: which makes me wonder if some XvBA work is also in store in the future…
FWIW, I was playing around with the Gears on Gallium distro last night (which is essentially openSUSE 13.1 based) and added kaffeine and multimedia stuff (restricted formats, blah blah blah). While it was still smooth, I did happen to observe very high cpu utilization in Kaffeine (xine based). MPlayer based was fine. Didn’t check VLC. It was gettng late and I forgot to test Xine directly … can’t recall what the terminal messages for Kaffeine were now, but it did indeed contain some complaints. Not sure if I was hitting something like what you two were seeing on not. Going to look at this again when I have some time.
basically the setup is in no-man’s-land, latest sw all round,
kernel 3.10.0-rc7-1-desktop, kde-4.10.4, openSUSE 13.1 from factory, Tumbleweed
so the consequences are accepted
vlc no complaints, ok for music, tv, dvd etc.
xine and kaffeine, dvd menu selection problems, only green screen seen,
can select by moving mouse around but do not see what is being selected,
flashes of the menu are seen when menu jumping,
can start playing dvds by trial and error,
once running cpu usage and video output look ok
Finally got back to this. In my case, its xine; specifically, its not working with vdpau and libvdpau_r600 (and UVD)
vo_vdpau: VideoSurface doesn't support yuy2, sorry.
… interesting as I don’t recall any colourspace related problems when testing previously with shaders (as opposed to UVD)… anyway, after it fails to create the vdpau output, xine falls back to an alternative vo codec. xine itself doesn’t give any further meaningful terminal output, but if you launch kaffeine via terminal, you get a little finer detail that it is opting to xv (which is what I’d expect). However, it (xv performance) is not behaving as efficiently as It should – the cpu utilization is almost double where it should be.
I have a TV card in my PC and was using Kaffeine for DVB-T… Since updating to KDE 4.11 and kernel 3.12, kaffeine now fails, tried xine and that also fails…
Result when I starting any of them in terminal mode
justinch@macdsktop:~> xine
This is xine (X11 gui) - a free video player v0.99.7.
(c) 2000-2010 The xine Team.
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.
libva info: VA-API version 0.33.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/fglrx_drv_video.so
libva info: va_openDriver() returns -1
^C
justinch@macdsktop:~> kaffeine
justinch@macdsktop:~> kaffeine
justinch@macdsktop:~> Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.
libva info: VA-API version 0.33.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/fglrx_drv_video.so
libva info: va_openDriver() returns -1
kaffeine(7125) DvbEpgModel::~DvbEpgModel: filter list not empty
QProcess: Destroyed while process is still running.
I now cannot watch any TV channels or play video files with kaffeine/xine. Note the file ‘fglrx_drv_video.so’ does not exist on my system.
Using the ATI’s Radeon driver for this system HD5xxx graphic card…
So do you have the package xvba-video installed? If yes uninstall it. It only works with fglrx.
Is that env var set?
echo $LIBVA_DRIVER_NAME
And as I already said, you can also try to set a different video driver. If you can’t start xine or kaffeine just edit the config file with a text editor (~/.kde4/share/apps/kaffeine/xine-config for kaffeine, ~/.xine/config for xine).
Or run xine with the -V option:
(I don’t have libvdpau_r300 installed)