Cannot switch to v17 that quick...
"Use limited range" is NOT enabled.
"Dithering depth" is set to 8
"Render method" is auto
"HQ Scaler" for above 20%
"Hardware acceleration VAAPI" enabled
- MPEG-2 VAAPI enabled
- MPEG-4 VAAPI enabled
- VC-1 VAAPI enabled
- prefer VAAPI enabled
Deinterlace video is auto
Deinterlace method is VAAPI motion adaptiv.
Video scaling method is Lanczos3
Not sure what you mean by "Is the GPU driver set to "Full Range, Limited, whatever""
I need a
Debug Log I need dmesg | pastebinit I need xrandr --verbose | pastebinit
So in your case you upscale all the colors to full range. Let's see what the xrandr tells. It might be that your TV switches to Limited itself when it switches to 50hz. Therefore post the xrandr --verbose command while the LiveTV is playing and _while_ the movie is playing.
Edit: v17 is required as no bugfixes are made to this v6 version at all. Also the upcoming v16 OE don't have these features at all.
@
fritsch, why sync to display could results in like a droning vinyl record. very funny but not useful. it happens even where adjust to screen is not necessary. on live tv for example. is my cpu too slow? n3150.
btw. on a rasp pi 2 it worked okay. (milhouse v17 build from 2 days or so. )
if I remember correctly you use a hacked up OpenELEC build with passthrough force enabled for live streams and additional Sync Playback to Display?
This will never work correctly as audio runs wallclock. The Pi has special code that makes PT work even with Sync Playback to Display as it can change the speed of the closed hdmi loop which no other system can do.
You know the elementary difference between "Sync Playback to Display" and "Adjust Refreshrate to match video"?
yes, i know the difference. i played with both. i only wanted to see, why videos from amazon with disabled sync to displays shows 25 fps (where most videos are 23.97) and when enabled the fps is showed as 23.97 with speeduped video +4.xxx% . so actually no live tv. and the amazon video only have a mp2 audio track.
my change is falsing the realtime flag only. i am currently checking with your build if there is a difference.
i didn't write until now my experience with the "new" behaviour of this realtime flag, because the current behaviour won't be change in the near future: at first. passthroug is working with my change (falsing realtime) without any problem regarding av sync. when i think about it, i don't have any problem with it. so i still cannot understand the workaround with disabled passthrough in live tv. but the worst behaviour is the reencoding to AC3. the loudness is complete wrong and the lipsync is catastrophic. 1,5 sec and up.
after writing this i have also tested your build. the behaviour is the same. but indeed. passthrough was enabled and i have disabled it for now. the droning vinyl record is still present. codec info show mostly sync +10% and avg and error is jumping all the time.
actually i don't use really sync to display, so it is no problem for me at all. only to ask you.
You had this 1080i50 screen right? So for 23.976 fps the "pseudo 25 fps" output is chosen ...
25 / 23.976 == 1,04
yes right. but i was expecting always 23.976 fps in codec info when sync to display is disabled when using inputstream.mpd.
other videos are showing always 23.976 when they are 23.976.
but i see right now, that the codec info screen has to be opened a longer time to update the fps to the expected 23.976.
I managed to compile and install this build on Arch Linux but I have some questions:
1) For deinterlace methods I only get VAAPI Bob/Motion Compensated/Motion Adaptive. Is this correct? The CPU is a G1620.
The question I will get is probably: what is the format? Which leads me to the next question:
2) The codec overlay doesn't show all information. So I can't see what the format is or if software or hardware acceleration is used.
This might not be an issue specific to this build, but I only used this build for Krypton. Any clue?
1) yes
2) all fine. This was changed ->
Debug Log will tell. From the "drops" I see in your codec screen you run an old version.
I compiled it yesterday so I'm not sure if that is old already?
Or is it another problem?
On the stable build of Kodi VAAPI deinterlacing didn't work at all so good to know that it works now.
->
Debug Log and the logfiles from post 1... no time for speculating.