2014-10-16, 01:16
(2014-10-16, 01:10)pootler Wrote: Unfortunately no luck with the hauppauge remote
pootler
Thanks. Not really sure what else to suggest right now.
(2014-10-16, 01:10)pootler Wrote: Unfortunately no luck with the hauppauge remote
pootler
(2014-10-15, 22:37)popcornmix Wrote: I have a guess what it may be. Can you try setting "sync playback to display"This was already enabled
Quote:and A/V sync to resample. Any different?while this was set to "Adjust PLL". It didn't have any effect.
Quote:Also can you try (in config.txt)This instead seems to have cured it. Changed A/V sync back to adjust PLL and still it seems to have worked - thanks!
hdmi_clock_change_limit=50
(2014-10-16, 05:22)menakite Wrote: I'm curious now - based on the name, I'd say that it limits the HDMI clock changes, and I assume that 50 is smaller than the default. Was the default value increased in recent firmwares? Also, why does this only affect a certain frame rate?
(2014-10-16, 13:00)popcornmix Wrote: Default is 175 (ppm). It has not changed for a long long time.Thanks for the detailed explanation.
Framerate is not significant, but how well the video timestamps and audio timestamps match the data is significant.
Run with mmal, sync video to display and set A/V sync to resample and watch the codec info.
The "rr" parameter shows how much audio needs to be resampled to keep the audio and video clocks synced.
While omxplayer uses a different algorithm, it still has to do a similar compensation.
It alllows up to 0.1% adjustment in HDMI pixel clock, but limits each change step to that specified by hdmi_clock_change_limit.
hdmi_clock_change_limit=50 equates to allowing 0.005% hdmi clock adjustment per step.
I suspect that either your 25Hz videos are encoded in such a way that the timestamps require significant adjustment (can be verified with "rr" number varying from 1.00 or oscillating),
or your receiver is more fussy in that mode.
Quote:Note: The default settings work fine for 99% of TVs/receivers - there are just some models that are unusually fussy - what receiver are you using?It's a recent LG TV (32LB650).
(2014-10-16, 17:47)doveman2 Wrote: Can I roll-back to Gotham stable by just extracting (and renaming as needed) the files from the zip (including the bootloader files) to the FAT partition of the SD card, or will running Helix have updated any files on the ext4 partition that will no longer be backwards-compatible with Gotham?
(2014-10-16, 05:22)menakite Wrote:Got it again :-(Quote:Also can you try (in config.txt)This instead seems to have cured it. Changed A/V sync back to adjust PLL and still it seems to have worked - thanks!
hdmi_clock_change_limit=50
It's hard to say for sure that something random is not happening though. I'll report back in a couple days.
# uname -a
Linux rpi512 3.17.1 #1 PREEMPT Thu Oct 16 22:13:26 BST 2014 armv6l GNU/Linux
# vcgencmd version
Oct 12 2014 13:00:44
Copyright (c) 2012 Broadcom
version 231a26c97857bfd939a62267a890f90b00c9d584 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20141016221217-r19393-g4556014 [Build #1016]
# uname -a
Linux rpi512 3.17.1 #1 PREEMPT Fri Oct 17 21:06:44 BST 2014 armv6l GNU/Linux
# vcgencmd version
Oct 17 2014 17:56:05
Copyright (c) 2012 Broadcom
version 845092531e360acd37f2f1964157f8079c77edfb (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20141017210533-r19393-g4556014 [Build #1017]