How to Install XBMC PVR Xvba for AMD/Nvidia/Intel GPUs

Thank you guys, for the awesome HOW-TO. I got it going on my Asus E35M1-I deluxe with the latest stable XBMC (11) build and CCC 12.2 on Ubuntu 11.11 64-bit.

Now, I'm about to install boblight to run with my Adalight setup and see if this all runs smoothly combined. That is the whole reason I switched to Linux in the first place. I had tearing on Windows.

(2012-04-07 09:55)fritsch Wrote:  @Tinofet:

There are three things that come to my mind:
1) Did you follow the minimal guide? If not - please disable compiz or gnome-shell if you have this running.
2) Check the vsync settings under: System->Settings->System->Video Settings: Vertical Sync: Always on
3) Check the video Settings itself: System ->Video->Playback: XVBA:check, Adjust Refreshrate to match video: check; Sync Playback to Display: Check; Sync Method: Video Clock (Drop/Dup Audio)

If this problem still persists, please pastebin (paste.ubuntu.com) a xbmc.log with debugging turned on.

Your suggestion worked .
But i had to unchecked the "Adjust refresh to match video" as it caused the image to flicker so bad i was about to get epilepsy

@Tinofet
Can you provide a log file with debugging turned on. I would like to see what caused this epilepsy flicker :-)

Since GCC 4.7 a new Bug may be detected while compiling libavcodec/x86/h264_qpel_mmx.c included in the ffmpeg package.

Running on Arch x64 and gcc 4.7 having this issue with the newest git version.
I have the same Problem as described here.

Cu,
Corpswalker

The Problem is solved when using the Eden branch.

For clarification:

xvba: first xvba implementation (works really good, stable, integrated in openelec 2.0) - development stopped
eden: xvba and vdpau second and improved implementation with various player enhancements (works really good, improved performance, stable) - development stopped, backports can probably happen.
master: bleeding edge (not stable, not tested, you will see bugs)

(2012-04-12 21:18)fritsch Wrote:  For clarification:

xvba: first xvba implementation (works really good, stable, integrated in openelec 2.0) - development stopped
eden: xvba and vdpau second and improved implementation with various player enhancements (works really good, improved performance, stable) - development stopped, backports can probably happen.
master: bleeding edge (not stable, not tested, you will see bugs)

So, if I'm building from the source tree on openSUSE 12.1, I should be checking out the eden branch rather than the xvba branch from https://github.com/FernetMenta/xbmc.git - is that correct?

I am basically using the same instructions as in http://forum.xbmc.org/showthread.php?tid...pid1022413

Thanks in advance.

FernetMenta told me the xvba branch shouldn't be used anymore, instead use the master branch.
In case you are compiling with gcc 4.7 the Eden branch is the correct one.

I don't know why the ffmpeg patches of the (stable) Eden branch is not synchronized with the master branches.

(2012-04-13 10:30)Corpswalker Wrote:  FernetMenta told me the xvba branch shouldn't be used anymore, instead use the master branch.
In case you are compiling with gcc 4.7 the Eden branch is the correct one.

I don't know why the ffmpeg patches of the (stable) Eden branch is not synchronized with the master branches.

Master is based on pvr master, which is based on mainline master and now uses ffmpeg 0.10.2.
Maybe it does now compile with gcc 4.7, didn't try myself.

(2012-04-13 10:30)Corpswalker Wrote:  FernetMenta told me the xvba branch shouldn't be used anymore, instead use the master branch.
In case you are compiling with gcc 4.7 the Eden branch is the correct one.

I don't know why the ffmpeg patches of the (stable) Eden branch is not synchronized with the master branches.

As I said: Great Confusion all over the place. Using master was correct two weeks ago. But this "master" from that time is now the eden branch. And current master is, as wsnipex told, directy based on xbmc-pvr master, which bases on xbmc master and is now in the approx one year for frodo to go phase :-)