•   
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 339
  •   
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
#46
(2015-07-14, 18:23)fritsch Wrote: I would use gst-launch directly to reproduce. It's a bit hard at the beginning to fiddle out the right params - but that way the intel people will be able to reproduce. Though i am not sure they will fix it for us. As it seems that this stream mixes progressive with interlaced and yadif just copes with that, while the intel vpp gets programmed by us. But we will see.

Try to adjust that:
Code:
gst-launch-0.10 filesrc location="/home/fritsch/1032_20130801154100.ts" ! tsdemux ! vaapidecode ! vaapipostproc deinterlace=1 deinterlace-method=3 ! vaapisink

I was able to reproduce the issue via this commandline:
Code:
gst-launch-1.0 filesrc -v location=test-usa-svu-1.ts ! decodebin ! vaapipostproc deinterlace-method=3 ! vaapisink

Playback is smooth (though of course showing the interlacing lines) with this commandline:
Code:
gst-launch-1.0 filesrc -v location=test-usa-svu-1.ts ! decodebin ! vaapisink

I captured the console output from the two test files:
http://pastebin.com/PPAQzemZ
http://pastebin.com/YQebMza9

It doesn't look exactly the same as we see in Kodi - it actually twitches like it's going back and forward in time, whereas Kodi just skips the frames so it's jerky.
Reply
#47
Settings -> Live TV -> Clear Data and retry.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#48
(2015-07-14, 22:29)puithove Wrote:
(2015-07-14, 18:23)fritsch Wrote: I would use gst-launch directly to reproduce. It's a bit hard at the beginning to fiddle out the right params - but that way the intel people will be able to reproduce. Though i am not sure they will fix it for us. As it seems that this stream mixes progressive with interlaced and yadif just copes with that, while the intel vpp gets programmed by us. But we will see.

Try to adjust that:
Code:
gst-launch-0.10 filesrc location="/home/fritsch/1032_20130801154100.ts" ! tsdemux ! vaapidecode ! vaapipostproc deinterlace=1 deinterlace-method=3 ! vaapisink

I was able to reproduce the issue via this commandline:
Code:
gst-launch-1.0 filesrc -v location=test-usa-svu-1.ts ! decodebin ! vaapipostproc deinterlace-method=3 ! vaapisink

Playback is smooth (though of course showing the interlacing lines) with this commandline:
Code:
gst-launch-1.0 filesrc -v location=test-usa-svu-1.ts ! decodebin ! vaapisink

I captured the console output from the two test files:
http://pastebin.com/PPAQzemZ
http://pastebin.com/YQebMza9

It doesn't look exactly the same as we see in Kodi - it actually twitches like it's going back and forward in time, whereas Kodi just skips the frames so it's jerky.

bugs.freedesktop.org please in VAAPI section. Let's see what the vaapi guys tell.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#49
(2015-07-14, 22:30)fritsch Wrote: bugs.freedesktop.org please in VAAPI section. Let's see what the vaapi guys tell.

Ok, will do.
Reply
#50
(2015-07-14, 22:29)fritsch Wrote: Settings -> Live TV -> Clear Data and retry.

http://sprunge.us/QDWT

Starting at 20:30:58 is the EPG data reset.

Other PVR plugins don't work either (installed TVHeadend addon at 20:33:55

But I guess this is getting too offtopic now.
Reply
#51
Jep, needs another bump - will ask @seo what is happening currently.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#52
so again this "forced disabled pvr clients" stuff. and regular (and not so regular) joe has no clue he was supposed to "set up" his pvr client. "set up" means "save defaults" as they are provided by the addon. just damn save! meh
Reply
#53
So as a workaround: Go to addon settings and press "save" once :-) Haha.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#54
that's by design. broken by design. have a good night
Reply
#55
(2015-07-14, 22:31)puithove Wrote:
(2015-07-14, 22:30)fritsch Wrote: bugs.freedesktop.org please in VAAPI section. Let's see what the vaapi guys tell.

Ok, will do.

Bug filed here in case you want to track it. Let me know if there's anything I should add, or feel free to jump in.
https://bugs.freedesktop.org/show_bug.cgi?id=91339
Reply
#56
So the artifacts are still there in the latest OE build, I uploaded a short video to demonstrate it (MCDI / Lanczos3): https://www.youtube.com/watch?v=ABUnO2fpf2w

Sorry for the quality and format, but it took me almost half an hour to upload anything Sad
Reply
#57
@hanzoh: That seems sadly driver related and we can't do a single thing about it ... You should see the issue even worse with: http://solidrun.maltegrosse.de/~fritsch/burosch1.mpg

So - I don't see those as heavily as you do. When you disable Lanczos3 Optimized - they should still be there, right?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#58
(2015-07-14, 09:30)fritsch Wrote: @Hufvudet: https://dl.dropboxusercontent.com/u/5572...adbb32.tar <- can you give that one a try ... should have nothing changed besides a rebase on rc2.

If it works for you - I will update the link above.

Working great for me. One question about dithering. My setup is kodi limited - xrandr full - tv limited and I was reading this by that madvr guru guy madshi:

It is true that with a prefect color neutral grayscale, letting madVR render to 16-235 means that madVR doesn't have to dither. However, even black & white movies are usually not 100% color neutral. They often have a slight color tint. And as soon as chroma is anything but exactly color neutral, madVR instantly has to dither. Which is the case for 99.99% of all movies out there. And once madVR dithers, it shouldn't matter too much whether you configure madVR to output PC or TV levels.

Yeah, sure, in theory having madVR output 16-235 should be slightly better. But in real life I don't think there's much of a difference between 16-235 and 0-255 output. Of course 16-235 allows the preservation of BTB/WTW, which might be a plus because some displays might be calibrated to show a tiny tiny bit of BTB/WTW or something.


I know this isn't madvr, and that we shouldn't get anal about everything, but should one perhaps enable dithering even when sending limited range to tv from kodi? Or I might have misunderstood this completely.
Reply
#59
Nope you understood correctly. Try it and tell us after some weeks of testing :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#60
Hahaha, you dare me to see any difference? Smile

But I was wondering also, when you enable dithering, is it always "on" when in playback like static noise or is it dynamic in some way?

Anyway, it's great that we have this option now. In fact, we have just about every option now for perfect vaapi playback!!
Reply
  •   
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 339
  •   



Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18
This forum uses Lukasz Tkacz MyBB addons.