2015-07-21, 06:36
Does this mean that IPTV simple addon will now be able to timeshift?
(2015-07-21, 22:03)aytek Wrote: Do you have any suggestions? I think my library is corrupted some how (maybe a power cut caused it).
# uname -a
Linux rpi512 4.1.2 #1 Tue Jul 21 21:03:44 BST 2015 armv6l GNU/Linux
# vcgencmd version
Jul 16 2015 19:12:56
Copyright (c) 2012 Broadcom
version bc619b5e5aa64f2b5fdd24f6b6a4e61907027a35 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20150721210255-#0721-g623255d [Build #0721]
# vcdbg log msg 2>&1 | grep DTOK
001576.768: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
# uname -a
Linux rpi512 4.1.2 #1 Wed Jul 22 23:05:44 BST 2015 armv6l GNU/Linux
# vcgencmd version
Jul 22 2015 21:56:39
Copyright (c) 2012 Broadcom
version 0a6416b75f88e3eab688f151dd07d34144785407 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20150722230456-#0722-g0cfb546 [Build #0722]
# vcdbg log msg 2>&1 | grep DTOK
001579.331: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
popcornmix Wrote:I'm hoping to push a firmware update tonight that solves the pts/dts timestamp issue. Realistically I suspect it may take a few iterations to handle all types of files, but will be good to get some testing soon.
...
The "prefer pts" option is gone. A lot of files seem to play well, but I would expect there to be some regressions.
If you find any files that are stuttery, then samples are useful.
(2015-07-23, 02:02)popcornmix Wrote: Can anyone currently running the advanced deinterlacer with overclock try reducing the overclock?
I'm hoping that gpu_freq=300 (for 1080i60) should be okay with tonight's build. 250 is probably okay for 1080i50.
(2015-07-23, 02:02)popcornmix Wrote: Also the "prefer PTS timestamps" option has been removed.
If you had problems with stutter and needed that option set a specific way, can you test again?
Samples of files that still stutter would be useful.
(2015-07-23, 02:02)popcornmix Wrote: I'm hoping that gpu_freq=300 (for 1080i60) should be okay with tonight's build. 250 is probably okay for 1080i50.Hi.
Samples of files that still stutter would be useful.
(2015-07-15, 14:48)Milhouse Wrote: Stop overclocking sdram_freq - it gives practically no benefit, but can often result in instability with recent firmware.
I too had a completely stable Pi2 for months with sdram_freq=500, but recent firmware resulted in random crashes and freezes, which went away once I stopped overclocking sdram_freq.
You could possibly regain stability by bumping up the sdram voltage, but unlike the Pi1, the Pi2 benefits very little from overclocking sdram (mainly because the ARMv7 SoC has increased L2 cache) so ultimately the increased risk of instability is just not worth the hassle for the meagre improved performance (which you probably won't even notice).
force_turbo=1 #used to push het gpu overclock
initial_turbo=60 #old-line; used this before to help prevent sd corruption --Still not sure if it was useless because off the force_turbo=1
arm_freq=1062
core_freq=590
# sdram_freq=400
over_voltage=4
over_voltage_sdram_c=0
over_voltage_sdram_i=0
over_voltage_sdram_p=2
avoid_pwm_pll=1
v3d_freq=400
h264_freq=400
disable_pvt=1 #Disable adjusting the refresh rate of RAM every 500 ms