•   
  • 1
  • 106
  • 107
  • 108(current)
  • 109
  • 110
  • 168
  •   
  Thread Closed
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)
Okay, trying both, one at a time, and will report back. I see there was a typo in what @popcornmix had. Thanks.
[H]i-[d]eft [M]edia [K]een [V]ideosaurus
My Family Room Theater
(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz
Awesome... this did the trick Big Grin, but why?! 1080p/60 and 59.94 should work too. Using build #1012 now. I have an Epson 5025UB and a BenQ W1070 (in different rooms), with Pi2 connected to each.

(2015-10-12, 23:53)Milhouse Wrote: Try:
Code:
tvservice -s
Image

Noticed that when reboot is done via SSH, Pi's UI rez goes to 23.98 (when I'd last set it to 60.00 or 59.94).
[H]i-[d]eft [M]edia [K]een [V]ideosaurus
My Family Room Theater
I'll probably jinx myself by saying this but with #1009 I haven't seen the problem I've been having with my tuners disappearing from tvheadend, so maybe there were some fixes to power saving issues or something that might have been causing that?

I have been seeing glitches which look like frames being skipped, making movement appear jumpy, with quite low resolution/bitrate AVC files though. Some of these seem to be due to poor encoding and repeat if I replay and also happen playing the files with VLC on my PC but others seem to be caused by OE and don't repeat when I replay the section. The overlay tends to show something like "drop:0 skip:5 pc:1" in total when watching the video but most of those seem to happen near the start, as after just a few seconds it might show "skip:3 pc:1" so these stats don't reflect the issues I notice and don't tend to have increased when I check after noticing them.

I've noticed that the err stat on the 2nd line of the overlay is about +/-10ms in most cases with these files, although sometimes nearer 20ms but if I skip this jumps to around 75ms and then slowly decreases over time, so it appears this does not reset when jumping through the file and continues to calculate an average.

Also aq is locked at a solid 99% whilst vq (video quality?) constantly fluctuates between 95-99% but if I skip backwards or forwards sometimes this drops to 91-95% or even 87-91%.

Code:
General
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom
File size                                : 350 MiB
Duration                                 : 43mn 3s
Overall bit rate mode                    : Variable
Overall bit rate                         : 1 136 Kbps

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : [email protected]
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 5 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 43mn 3s
Bit rate                                 : 1 010 Kbps
Maximum bit rate                         : 4 473 Kbps
Width                                    : 720 pixels
Height                                   : 404 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.145
Stream size                              : 311 MiB (89%)
Writing library                          : x264 core 138 r2358 9e941d1
Encoding settings                        : cabac=1 / ref=5 / deblock=1:1:1 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=20 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=crf / mbtree=1 / crf=19.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Color range                              : Limited
Matrix coefficients                      : BT.709

Audio
ID                                       : 2
Format                                   : AAC
Format/Info                              : Advanced Audio Codec
Format profile                           : LC
Codec ID                                 : 40
Duration                                 : 43mn 3s
Bit rate mode                            : Variable
Bit rate                                 : 122 Kbps
Maximum bit rate                         : 155 Kbps
Channel(s)                               : 2 channels
Channel positions                        : Front: L R
Sampling rate                            : 48.0 KHz
Compression mode                         : Lossy
Stream size                              : 37.5 MiB (11%)
(2015-10-13, 00:15)hdmkv Wrote:
(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz
Awesome... this did the trick Big Grin, but why?! 1080p/60 and 59.94 should work too. Using build #1012 now. I have an Epson 5025UB and a BenQ W1070 (in different rooms), with Pi2 connected to each.

The W1070 only supports frame packing at "24p" for 1920*1080. It seems like after stopping a 3d MKV / bluray iso, Kodi doesn't send a message to the projector to say that it should turn frame packing off (the projector tells me Frame Packing is still on) so the GUI looks wrong (or in your case, it just goes blank). If I set the GUI at anything other than 23.98 / 24 @ 1920*1080, as the projector does not support frame packing for those rates, it works normally. I don't fully understand what is happening under the hood, but through trial and error, I found that it works that way. No great loss to have the GUI at 50hz (other than a flicker when the projector shifts modes).

Cheers
All 3D ISO's work with #1012 now. Great work!!!
just got myself a bluetooth dongle for one of my pi2's running #1003. Having issues as in managed to pair once but lost connection. Deleted connections and cannot pair again. Tried Android phone and Bluetooth speaker - both connect (they show up as devices - allow to connect or trust and connect) but then give Bluetooth error - no such file or directory and disconnect.

No idea what this is all about - any ideas??

thnx

Dennis
(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz

Can you also report output of:
Code:
tvservice -s

when you believe projector is incorrectly in FP mode. I'd like to know if firmware believes it is signalling FP or not.
I found solution for mystery bookmark crash problem.

There is a lot of "10025-xxxx.fi" files and then I delete them, no more crash.
I don't know what is this file, but first number of filename is window ID.

Delete all ".fi" files in folder '.kodi/temp', it solves bookmark crash problem.
(2015-10-13, 11:26)popcornmix Wrote:
(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz

Can you also report output of:
Code:
tvservice -s

when you believe projector is incorrectly in FP mode. I'd like to know if firmware believes it is signalling FP or not.

state 0x12000a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive

(which is different to when the movie is actually playing = "state 0x12000a [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive"
For me, it's not just 3D (frame-packed mode and coming out of it) that had the issue, but 2D as well with UI set to 59.94 or 60.00.
[H]i-[d]eft [M]edia [K]een [V]ideosaurus
My Family Room Theater
(2015-10-13, 11:08)cdvreede Wrote: just got myself a bluetooth dongle for one of my pi2's running #1003. Having issues as in managed to pair once but lost connection. Deleted connections and cannot pair again. Tried Android phone and Bluetooth speaker - both connect (they show up as devices - allow to connect or trust and connect) but then give Bluetooth error - no such file or directory and disconnect.

No idea what this is all about - any ideas??

thnx

Dennis

Test with 5.95.5. If you have the same problem you'll need to report it to the OpenELEC developers as it's going to be a core issue as there are no Bluetooth changes in these builds.
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.
(2015-10-13, 12:58)woronczak Wrote: state 0x12000a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive

(which is different to when the movie is actually playing = "state 0x12000a [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive"

Okay. Sounds like if the refresh rate doesn't change, but the 3D FP mode does then either we don't re-initialise everything, or we do, but the display doesn't see the change.
I'll step through the code and see if anything is skipped when switching from 1080p23.98 FP to 1080p23.98.

Does disconnecting and reconnecting the HDMI cable have any effect? It it does that would suggest we are outputting the correct signal but the display didn't switch correctly.
I've been playing with setting GUI resolution to [email protected] and playing MVC files. My display seems to switch back correctly to non-3D mode when stopping.
I've stepped through the firmware code, and while it can skip the mode change if it believes nothing has changed, it does check the 3D mode, so should spot switches into and out of 3D mode.

I'm interested in the results of "disconnecting and reconnecting the HDMI cable". Ideally you should add "hdmi_force_hotplug=1" to config.txt to ensure the Pi doesn't notice the unplug/plug events.

Can you also report output of:
Code:
vcgencmd measure_clock pixel

when stopping (and gui being wrong). It should be about 74MHz when in 2D mode and 148MHz when in 3D FP mode.
@popcornmix,

Want to start using the testbuilds on my Pi2.
Are there any of my config.txt settings that are obsolete for these builds?

arm_freq=1050
core_freq=550
over_voltage=4
gpu_mem=320
gpu_freq=400
hdmi_pixel_encoding=2
dtoverlay=sdhost,overclock_50=84

over_voltage_sdram_c=0
over_voltage_sdram_i=0
over_voltage_sdram_p=2
avoid_pwm_pll=1
v3d_freq=300
force_turbo=1

Thanks
(2015-10-13, 22:24)rudrood Wrote: @popcornmix,

Want to start using the testbuilds on my Pi2.
Are there any of my config.txt settings that are obsolete for these builds?

arm_freq=1050
core_freq=550
over_voltage=4
gpu_mem=320
gpu_freq=400
hdmi_pixel_encoding=2
dtoverlay=sdhost,overclock_50=84

over_voltage_sdram_c=0
over_voltage_sdram_i=0
over_voltage_sdram_p=2
avoid_pwm_pll=1
v3d_freq=300
force_turbo=1

You can remove avoid_pwm_pll with latest builds. You now get the effect of that by default without harming analogue audio.
You can remove over_voltage_sdram_c and over_voltage_sdram_i as they are set to zero (and also have no effect on Pi2).
Otherwise looks okay.
  •   
  • 1
  • 106
  • 107
  • 108(current)
  • 109
  • 110
  • 168
  •   
  Thread Closed
 
Thread Rating:
  • 10 Vote(s) - 5 Average



Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)510