[Announce] VA-API/VPP Support for vdr-plugin-softhddevice

johns · June 8, 2015 at 1:23 PM

In the next days i submit the OSD patch for VDPAU and VA-API to my GIT.

The VA-API Part may be unchecked.

Johns

maz · June 17, 2015 at 8:16 PM

Hi,

ich überlege gerade ob ich als nächstes VDR-Bastelprojekt einen Mac mini (Late 2014) zulegen soll: Specs (CPU/Grafik: Intel Core i5 "Haswell" mit Intel Iris 5100)
Eigentlich bin ich mit dem Mac mini 2010 (mit Nvidia GT320M) ganz zufrieden, etwas mehr Performance würde aber nicht schaden, und man könnte ggf. einen besseren Deinterlacer nutzen.
Würdet ihr erwarten dass mit dem 2014er Modell softhddevice mit vaapi schon stabil läuft?

Gruß maz

447377 · July 5, 2015 at 6:27 PM

After my test in february I retried it with newer versions. On the one side I was surprised about the beautiful result without nvidia. But on the otherside there are „droping frame“ - especially in fullscreen mode.
What is the difference to your setups? Please help me...

Thanks a lot
Stefan

My Hardware:
- Asus B85M-E
- Intel G1820 (Haswell)
- 2x 2 GB RAM (512 MB der GPU zugewiesen)

Opensuse 13.2
- softhddevice http://github.com/pesintta/vdr-plugin-softhddevice
- ffmpeg 2.6.3
- mesa 10.7~git20150703
- xf86-video-intel 2.99.917
- vaapi-intel-driver 1.5.1
- libva 1.6.0.pre1

Start with „-P 'softhddevice -a hw:0,7 -d :0.0 -g 1280x720 -v va-api' \“
- 576i: Deinterlace MotionCompensated, Field Order 0/2
- 720p: Deinterlace none, Field Order 0/2
-> No „Frames drop“, everything is perfect, the picture is a dream!

Start with „-P 'softhddevice -a hw:0,7 -d :0.0 -g 1600x900 -v va-api' \“
- 576i: No Frames drop.
-720p: Frames drop

Fullscreen (1920x1080):
Frames drop on 576i and 720p.

With va-api-glx the result is bad. There are breaks, crashs and window isn't scaleable.

Ironmonster · July 27, 2015 at 10:44 PM

I try to compile softhddevice (http://github.com/pesintta/vdr-plugin-softhddevice) and get the following error any hints ?

Code

softhddevice.cpp:1106:29: error: ‘PreAvFilter’ was not declared in this scope
 memcpy(old_preavfilter, PreAvFilter, sizeof(PreAvFilter));
 ^
softhddevice.cpp:1107:30: error: ‘PostAvFilter’ was not declared in this scope
 memcpy(old_postavfilter, PostAvFilter, sizeof(PostAvFilter));
 ^
softhddevice.cpp:1127:33: error: ‘eAvFilterConfigUserDefined’ was not declared in this scope
 && (old_preavfilter == eAvFilterConfigUserDefined
 ^
<builtin>: recipe for target 'softhddevice.o' failed
make[1]: *** [softhddevice.o] Error 1


*** Plugin status:
make[1]: Nothing to be done for 'all'.

Display More

Intel nuc5cpyh (braswell celeron)

xubuntu 15.04 / 4.2.0-040200rc2-generic

ffmpeg version 2.5.7

mesa 10.6.3

vaapi is working e.g. in kodi

vainfo: VA-API version: 0.38 (libva 1.6.0.pre1)
vainfo: Driver version: Intel i965 driver for Intel(R) CherryView - 1.6.0.pre1 (1.6.0.pre1)

nc17 · July 28, 2015 at 5:57 PM

You should install the missing ffmpeg dev - Packages

Code

sudo apt-get install libswresample-ffmpeg-dev libavresample-ffmpeg-dev libswscale-ffmpeg-dev libpostproc-ffmpeg-dev libavfilter-ffmpeg-dev libavformat-ffmpeg-dev libavdevice-ffmpeg-dev libavcodec-ffmpeg-dev libavutil-ffmpeg-dev

zaverel · July 29, 2015 at 2:33 PM

Hello,

It's seems that the last libva-intel-driver master git break vaapi deinterlace.

black screen or fixed display.

i use kodi and softhddevice (vaapi vpp) and both don't work for live tv.

in vdr log:

Quote

Jul 29 14:02:35 [vdr] vaapi/vpp: Wrong number of forward references. Needed 0, got 1
Jul 29 14:02:35 [vdr] Changing to 0 forward reference surfaces for postprocessing_

If i unpatch commit:

VPP: Combine the CSC/Scaling together to optimize the performance

that work like before.

I open 2 bug report :
http://www.mail-archive.com/libva@lists.fr…g/msg03175.html (open)
http://trac.kodi.tv/ticket/16161 (closed)

So could someone confirm the bug ?

Thanks.

Ironmonster · August 2, 2015 at 2:35 PM

Quote from nc17

You should install the missing ffmpeg dev - Packages

thx i was able to compile it now

one last problem is remaning:

i have strange colored bars on some frames video type 576i 720p 1080i doesnt matter:

i remember i read sth. about debug options beiing left enabled ?
I already diasbled #CONFIG := -DDEBUG in the make file

I made a video and some screenshots showing the problem:

https://www.youtube.com/watch?v=BapNsu7a6H0

http://i.imgur.com/gPbdVvP.png

http://i.imgur.com/0mfYSqU.jpg

http://i.imgur.com/bZy372o.jpg (some frames are fine)

only messages i get about every minute:

Code

Aug  2 13:59:38 nuc vdr: video: speed up video, droping frameAug  2 13:59:38 nuc vdr: video: 23:02:07.886  -47  425   0/\ms  34+2 v-buf

rvdb · September 22, 2015 at 10:16 PM

Hi,

New asrock n3700M, I installed debian sid, pesintta softhddevice.
Same horizontal bars on all resolutions.

Somebody already found a resolution?

greetings Rene

ddd · September 22, 2015 at 10:28 PM

What kernel do you use?
There was an bug in <= 4.0 with the Braswell CPU's, see post 2 here http://forum.kodi.tv/showthread.php?tid=231955

fnu · September 22, 2015 at 10:58 PM

There seems always a bug with anything of Intel, either kernel, either driver ...

rvdb · September 23, 2015 at 8:40 AM

ddd

kernel 4.3.0-040300rc1-generic.

Ironmonster · September 23, 2015 at 10:38 AM

I thinks its not related to a specific vaapi, kernel, ffmpeg or intel-driver version.

I tested with pretty every recent version i could find.

Now that we have another report with the same Issue on a Asus n3700M I think its just related to the braswell CPU/GPU und softhddevice.

I gave up trying to get it to work and use Kodi now for TV and Media on my Intel nuc5cpyh.

rvdb · September 23, 2015 at 11:35 AM

Well, some more testing:

if in video.c line 4122 I put a break just after
"case VAProcFilterColorBalance:"

Thus disabeling the colorbalance filters, the bars are gone !

The N3700 should be perfect for a HTPC, but for now the
N24 ticker is still better on XBMC

Ironmonster · September 23, 2015 at 11:52 AM

Quote from xyzzy

if in video.c line 4122 I put a break just after
"case VAProcFilterColorBalance:"

Do you use https://github.com/pesintta/vdr-plugin-softhddevice/ ?

Sadly I cant test it atm.

rvdb · September 23, 2015 at 12:07 PM

Yes, pesintta

rofafor · September 23, 2015 at 9:38 PM

So, what does your log say about "video/vaapi: Supported color balance filter count" ? Maybe the driver announces invalid capabilities for your platform....

rvdb · September 23, 2015 at 10:18 PM

video/vaapi: enabling color balance filters
video/vaapi: Supported color balance filter count: 4
Hue (-180.00 - 180.00 ++ 1.00 = 0.00) (pos = 2)
Saturation (0.00 - 10.00 ++ 0.10 = 1.00) (pos = 2)
Brightness (-100.00 - 100.00 ++ 1.00 = 0.00) (pos = 2)
Contrast (0.00 - 10.00 ++ 0.10 = 1.00) (pos = 2)
video/vaapi: skin tone enhancement supported
Wrong number of capabilities (0) for filter 0x00000005

rvdb · September 24, 2015 at 1:26 PM

Hmm, I believe line 4166
now: VAProcFilterColorBalance, colorbalance_caps,

should be : VAProcFilterColorBalance, &colorbalance_caps,

This is not a solution for the bars, but it does fix the segfault when entering the menu
video - 576i etc. (and also -v va-api-glx)
(there are probably more)

rofafor · September 24, 2015 at 6:53 PM

Thanks for the hint.

Could you disable the color balance filters one by one and bisect what's the nasty one?

Diff

diff --git a/video.c b/video.c
index 87faf47..4de5546 100644
--- a/video.c
+++ b/video.c
@@ -4131,6 +4131,7 @@ static void VaapiSetupVideoProcessing(VaapiDecoder * decoder)
                                colorbalance_caps[v].range.step, colorbalance_caps[v].range.default_value, decoder->filter_n);
                            break;
                        case VAProcColorBalanceHue:
+                           break; // comment to enable
                            VaapiConfigHue.active = 1;
                            Info("%s (%.2f - %.2f ++ %.2f = %.2f) (pos = %d)\n", "Hue",
                                colorbalance_caps[v].range.min_value, colorbalance_caps[v].range.max_value,
@@ -4140,6 +4141,7 @@ static void VaapiSetupVideoProcessing(VaapiDecoder * decoder)
                            decoder->vpp_hue_idx = v;
                            break;
                        case VAProcColorBalanceSaturation:
+                           break; // comment to enable
                            VaapiConfigSaturation.active = 1;
                            Info("%s (%.2f - %.2f ++ %.2f = %.2f) (pos = %d)\n", "Saturation",
                                colorbalance_caps[v].range.min_value, colorbalance_caps[v].range.max_value,
@@ -4149,6 +4151,7 @@ static void VaapiSetupVideoProcessing(VaapiDecoder * decoder)
                            decoder->vpp_saturation_idx = v;
                            break;
                        case VAProcColorBalanceBrightness:
+                           break; // comment to enable
                            VaapiConfigBrightness.active = 1;
                            Info("%s (%.2f - %.2f ++ %.2f = %.2f) (pos = %d)\n", "Brightness",
                                colorbalance_caps[v].range.min_value, colorbalance_caps[v].range.max_value,
@@ -4158,6 +4161,7 @@ static void VaapiSetupVideoProcessing(VaapiDecoder * decoder)
                            decoder->vpp_brightness_idx = v;
                            break;
                        case VAProcColorBalanceContrast:
+                           break; // comment to enable
                            VaapiConfigContrast.active = 1;
                            Info("%s (%.2f - %.2f ++ %.2f = %.2f) (pos = %d)\n", "Contrast",
                                colorbalance_caps[v].range.min_value, colorbalance_caps[v].range.max_value,

Display More

rvdb · September 24, 2015 at 7:16 PM

rofafor:

I already did that,

no matter what filter is set, as soon as
decoder->filters[decoder->filter_n++] = filter_buf_id;
is hit, no matter what the contents of cbal_param the problem exist.

NB there is also a smal problem with the tone filter, in VaapiSetupParameterBufferProcessing
cap_n == 0 so no buffer is created
And also the & is forgotten in vaQueryVideoProcFilterCaps

[Announce] VA-API/VPP Support for vdr-plugin-softhddevice

Participate now!

Users Viewing This Thread