• 1
  • 175
  • 176
  • 177(current)
  • 178
  • 179
  • 277
OpenELEC Testbuilds for RaspberryPi Part 2
Just to confirm - 25Hz is not correct for PAL it should definitely set a refresh rate of 50Hz.

Also, it looks like the player is detecting the wrong framerate in the stream (see 23:16:07 389.255035) below. The stream is 1080i 50fps
(2014-01-30, 01:05)markius Wrote: Just to confirm - 25Hz is not correct for PAL it should definitely set a refresh rate of 50Hz.

Maybe if you are talking about interlaced content on a composite television.

For progressive output to a HDMI display, then outputting 25Hz where supported makes more sense.
When we output to a 50Hz display, we have to send each image twice. That achieves nothing other than wasting CPU and memory bandwidth.
I guess the thing to do would be to check what a non-Pi build of Gotham does with the same material and display.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Not talking about composite or anything like that.

25 *fields* per second (EG 1080i - "interpolated") is still 50 *frames* per second. Deinterlacing my friend!

Also the non gotham builds on the Pi do 50Hz for the same content and it doesn't look like crap!

Edit: clarfication of fields per second vs frames per second
Ahh I get my friend. I don't come across much interlaced content where I live.
(2014-01-30, 01:21)MilhouseVH Wrote: I guess the thing to do would be to check what a non-Pi build of Gotham does with the same material and display.

It will pick the *biggest* multiple of the framerate that is supported.
If your TV supports 150Hz then it will choose that as the best match for a 25fps video, and use several times as much cpu to do it.
It doesn't mean that's the correct think to do...
Sure, just wondering if it would help clarify if the Pi is doing something wacky, or if it's a general XBMC "issue" (I suspect it's the latter).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
@delinend:
Code:
advancedsettings>

  <video>
    <adjustrefreshrate>
      <override>
        <fps>25.0</fps>
        <refresh>25.0</refresh>
      </override>

      <override>
        <fps>29.97</fps>
        <refresh>30.0</refresh>
      </override>

      <override>
        <fps>30.0</fps>
        <refresh>30.0</refresh>
      </override>
    </adjustrefreshrate>
  </video>

</advancedsettings>
For Frodo..
Obviously if Gotham is doing the opposite switch values. Smile
You are correct about 1080i PAL source if you want to display all the fields.
But 24fps, 25fps or 30fps progressive displayed at double refresh rate or in the case of 24fps a pulldown to 60p won't let you see anymore pictures or fields or make a soccer game more fluid.
On my TV there's no difference in "flicker" between 25hz and 50hz at all, and yes I have all CMR and image processing options off.
(2014-01-30, 01:32)markius Wrote: Not talking about composite or anything like that.

25 *fields* per second (EG 1080i - "interpolated") is still 50 *frames* per second. Deinterlacing my friend!

Also the non gotham builds on the Pi do 50Hz for the same content and it doesn't look like crap!

Edit: clarfication of fields per second vs frames per second

Yes, that's why I've been clarifying what I'm saying with 25 fps progressive is fine at 25 Hz.
Interlaced content with deinterlace enabled is different, as the deinterlace algorithm doubles the framerate, so 50 Hz would be better.
Thanks for the pointer, tuxen

I added...
Code:
<video>
     <adjustrefreshrate>
       <override>
         <fps>25.0</fps>
         <refresh>50.0</refresh>
       </override>
  </video>

...to advancedsettings.xml which is a good workaround for now.

However, any content that is genuinely 25 frames per second will also output at 50Hz which it has been pointed out is a waste of resources.
I suspect the issue is further upstream. Interpolated/interlaced content should set the refresh rate to double the frames per second and for some reason, in these builds it does not do that.

FYI:
Code:
OpenELEC:~/.xbmc/userdata # cat /proc/version
Linux version 3.13.0 (neil@nm-linux) (gcc version 4.8.2 (GCC) ) #1 PREEMPT Mon Jan 27 16:27:02 GMT 2014
OpenELEC:~/.xbmc/userdata # /usr/lib/xbmc/xbmc.bin --version
XBMC Media Center 13.0-ALPHA12 Git:2667375
Copyright (C) 2005-2013 Team XBMC - http://xbmc.org
OpenELEC:~/.xbmc/userdata # cat /etc/version
devel-20140127205936-r17176-gcaa2854
OpenELEC:~/.xbmc/userdata #

EDIT: <refresh>50.0</refresh> !! Big Grin
New OpenELEC Gotham build: #0130
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 3.13.0 #1 PREEMPT Thu Jan 30 03:12:31 GMT 2014 armv6l GNU/Linux

# vcgencmd version
Jan 28 2014 18:56:53
Copyright (c) 2012 Broadcom
version 8966c433ecd9358a1cdab717d2a1b89999464b10 (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20140130031137-r17182-g6d01e5f

Based on tip of XBMC master (196ae9f, changelog) and tip of OpenELEC master (6d01e5f, changelog) with the following modifications:
  • Includes newclock3 commits (except for 5e9b423 which I've replaced with a static spinner)
  • Excludes the OpenELEC fernetmenta patches (due to conflict with newclock3)
Build Higlights:
  1. Included upstream:
    • PR4083: fix HLS variant selection
    • PR4110: [rbp/omxplayer] Fixed: analog output was not properly enabled

Additional Testing Notes:
  1. Testers should try adding the following entry to their advancedsettings.xml:
    Code:
    <advancedsettings>
      <video>
        <defaultplayer>dvdplayer</defaultplayer>
        <defaultdvdplayer>dvdplayer</defaultdvdplayer>
      </video>
    </advancedsettings>
    and report if it is better/worse than omxplayer. You can still play files with omxplayer using the context-menu "Play using... OMXPlayer".

  2. The following settings are no longer required in config.txt and should be removed:
    Code:
    no_hdmi_resample=1
    hdmi_stream_channels=1
    no_resample_audio is now a default, and hdmi_stream_channels is switched based on audio content. For the time being when using passthrough, 2.0 speaker layout should continue to be used (you will still get 5.1 with AC3/DTS).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2014-01-30, 01:21)MilhouseVH Wrote: I guess the thing to do would be to check what a non-Pi build of Gotham does with the same material and display.

Hi Milhouse.

I have just installed Gotham Nightly build for Windows (XBMCSetup-20140128-56c2654-master.exe ) on my Laptop, with HDMI to my screen in 1920x1080p60. To test 25p/50p on that version.

My only setting in XBMC: Video->Playback->Adjust display refresh rate to match video = Always
No change in advancedsettings.xml !!!

When playing 24p movies, the display switch to 1920x1080p24
When playing PAL25p movies, the display switch to 1920x1080p50 !!

The Windows Gotham build, do the same as Frodo, switching 25p to 50p. And that look's good.

It look's like the problem is only on Pi-build :-(

Best regards
@delinend/@popcornmix:

After plumbing my Pi into my Onkyo 828 amp (what a palava!) I've spent the last couple of hours testing old and new builds with respect to this refresh issue.

I deleted guisettings.xml and set "Adjust display refresh rate to match video" set to "Always", and apart from enabling debug logging, changed nothing else. My advancedsettings.xml does not include any defaultdvdplayer settings, so omxplayer is the default player and that is what I used for all tests.

Going as far back as mid December, all of my Gotham builds have this same 25Hz in, 25Hz out behaviour (or 29.970/30Hz in, 30Hz out). 24Hz in is output at 24Hz. So this is not a recent problem.

I then created a build without any newclock3 patches (but still using the latest Jan 28 firmware), and now 25Hz material is being output at 50Hz (and 30Hz material at 60Hz), so it's definitely a newclock3 patch that is causing this difference in video refresh rate behaviour.

I proceeded to build Gotham with just the following newlock3 patch, and the 25Hz in, 25Hz out and 30Hz in, 30Hz out behaviour returned:
Code:
popcornmix/xbmc/commit/a674b64876f81813036485de22fe15de95d5ed58  [3D] Support switching to 3D resolutions

so that would appear to be the culprit.

Personally I'm not even sure this new behaviour should be classed as "wrong", it seems more logical to me but if it causes juddering on some setups (and doubling the frame rate doesn't) then I guess using the higher frame rate is the way to go...

Here's a debug log, without the 3D switching patch, when playing 24Hz, 25Hz and 29.970Hz material (output at 24Hz, 50Hz and 60Hz respectively).
Here's a debug log, WITH the 3D switching patch, playing the same 24Hz, 25Hz and 29.970Hz material (output at 24Hz, 25Hz and 30Hz respectively).

If you look at where each build detects 3D movies, the difference is clear:
Without 3D switching patch - playing 29.970 material (output at 60Hz):
Code:
09:05:50 T:2928178256  NOTICE: not a 3D movie
09:05:50 T:2928178256   DEBUG: ResolutionUpdateCallBack - change configuration. video:1920x1080. framerate: 29.97. 720x480 format: BYPASS
09:05:50 T:2928178256  NOTICE: Display resolution ADJUST : 1920x1080 (1920x1080) @ 60.00 - Full Screen (19) (weight: 0.001)

and now with the 3D switching patch, same 29.970 material this time output at 30Hz:
Code:
09:10:22 T:2716857424  NOTICE: not a 3D movie
09:10:22 T:2716857424   DEBUG: ResolutionUpdateCallBack - change configuration. video:1920x1080. framerate: 29.97. 720x480 format: BYPASS
09:10:22 T:2716857424  NOTICE: Display resolution ADJUST : 1920x1080 (1920x1080) @ 30.00 - Full Screen (25) (weight: 0.002)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Hi guys, I'm getting the same judder when my TV is switching to 25hz for 25p content, the CPU seems to be at 100% all the time, maybe that is the reason for the judder and not the HZ.
Also every 3 or 4 frames i'm getting a green screen.
DVDPlayer seems to handle HD 24p content very well, FF and BW is a little bit slow but it's not a problem. My RPi is overclocked @1000:500:500.
  • 1
  • 175
  • 176
  • 177(current)
  • 178
  • 179
  • 277

Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi Part 223