Kodi Community Forum
OpenELEC Testbuilds for RaspberryPi Part 2 - Printable Version

Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166)
---- Thread: OpenELEC Testbuilds for RaspberryPi Part 2 (/showthread.php?tid=184866)



RE: OpenELEC Testbuilds for RaspberryPi Part 2 - allan87 - 2013-12-04

(2013-12-04, 17:25)Trixster Wrote: Chaps, great work, I love all the updates! However, the latest builds still don't seem to save the resoultion settings. With every reset I have to go back and recalibrate the Video settings for each resolution and refresh rate as the settings for the pixel ration square defaults back to 0.500. Any chance a fix for this could be included?
Thanks.
I have had that problem forever. For weeks, maybe moths, anyway. Other settings don't survive a reboot, either (like access restrictions). A workaround is to manually edit the guisettings file and then reboot via ssh (reboot by gui overwrites the settings).

My guess is that certain changes are cached somewhere and are supposed to be written to the guisettings file at shutdown, but they are not.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 17:33)allan87 Wrote: My guess is that certain changes are cached somewhere and are supposed to be written to the guisettings file at shutdown, but they are not.

The most likely reason is that xbmc is crashing when shutting down, and so not writing guisettings.xml.
This was the case a couple of weeks back, but that bug was fixed, and for me it shuts down cleanly now.

It's probably caused by a plugin. If you want to track it down, then move your .xbmc folder out of the way, and see if xbmc with no plugins or user settings shuts down okay
(e.g. change a trivial setting and shutdown, and check it's there when you reboot).

If it does shutdown okay, then try setting up your normal gui settings (including video calibration).
If that works, then install any plugins/skins you use one by one and see if any of those break it.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - allan87 - 2013-12-04

I have lost picture on most video with the new build. Here's the log, showing errors. I can do a debug log later if needed:
Code:
19:17:11 T:3044471312  NOTICE: Previous line repeats 2 times.
19:17:11 T:3044471312  NOTICE: COMXPlayer: Opening: nfs://10.0.100.25/nfs/Media/Movies/The Dark Knight.m4v
19:17:11 T:3044471312 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
19:17:11 T:2721051728  NOTICE: Thread OMXPlayer start, auto delete: false
19:17:11 T:2721051728  NOTICE: Creating InputStream
19:17:12 T:2721051728  NOTICE: Creating Demuxer
19:17:13 T:2721051728  NOTICE: Opening video stream: 0 source: 256
19:17:13 T:2721051728  NOTICE: Creating video thread
19:17:13 T:2695885904  NOTICE: Thread OMXPlayerVideo start, auto delete: false
19:17:13 T:2721051728  NOTICE: Opening audio stream: 1 source: 256
19:17:13 T:2721051728  NOTICE: Creating audio thread
19:17:13 T:2681472080  NOTICE: Thread OMXPlayerAudio start, auto delete: false
19:17:13 T:2721051728  NOTICE: Opening Subtitle stream: 2 source: 256
19:17:13 T:2965369936   ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.audio_render - OMX_ErrorInsufficientResources, insufficient resources
19:17:13 T:2681472080   ERROR: COMXAudio::PortSettingsChanged - m_omx_tunnel_decoder.Establish omx_err(0x80001000)
19:17:13 T:2681472080   ERROR: COMXAudio::AddPackets - error PortSettingsChanged omx_err(0x00000000)
19:17:13 T:2721051728  NOTICE: OMXClock using audio as reference
19:17:13 T:2695885904  NOTICE: not a 3D movie
19:17:13 T:2695885904  NOTICE: Display resolution ADJUST : 1920x1080 @ 30.00 - Full Screen (27) (weight: 0.002)
19:17:13 T:3044471312  NOTICE: Using GL_TEXTURE_2D
19:17:13 T:3044471312  NOTICE: GL: Using BYPASS render method
19:17:13 T:3044471312  NOTICE: GL: NPOT texture support detected
I have tried with several videos. Some work, most don't. I have not identified a pattern, although no HD movies have played correctly. Most SD did not play correctly either.

Also, fyi, I have a 512 MB Pi and the memory setting in config.txt is

# SDRAM size based GPU memory split, uncomment and setup to override 'gpu_mem'
gpu_mem_256=128
gpu_mem_512=256

(2013-12-04, 17:42)popcornmix Wrote:
(2013-12-04, 17:33)allan87 Wrote: My guess is that certain changes are cached somewhere and are supposed to be written to the guisettings file at shutdown, but they are not.
It's probably caused by a plugin. If you want to track it down, then move your .xbmc folder out of the way, and see if xbmc with no plugins or user settings shuts down okay
Do you think the error will show if I just run tail while shutting down?


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - evangelion - 2013-12-04

(2013-12-04, 17:26)popcornmix Wrote:
(2013-12-04, 17:25)evangelion Wrote: Hopefully the Gui sounds will work with HDMI shortly, kinda looking forward to scrolling through Movies etc and hearing the familiar old "tac-a-tac-a-tac-a-tac-a.." Wink

Have you tried Milhouse's latest build?

Just installed it ... awesome work! Switching Skin and/or changing the Gui sounds through the skins Appearance no longer causes a reboot, so very happy!

BUT! slightly disappointed with the Gui sound, on mine I have a choice of Default, which makes that lovely familiar Swishing sound when going back through menus, but a (very) muted (and not on every keypress from what I can make out) kinda dull knock? the other option is the Bursting Bubbles one? those are the only two?

Is there any chance we could have the original "Tac!" sound? pwetty pwease!? Blush


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 18:15)evangelion Wrote: BUT! slightly disappointed with the Gui sound, on mine I have a choice of Default, which makes that lovely familiar Swishing sound when going back through menus, but a (very) muted (and not on every keypress from what I can make out) kinda dull knock? the other option is the Bursting Bubbles one? those are the only two?

Is there any chance we could have the original "Tac!" sound? pwetty pwease!? Blush

It sounds just the same as xbmc on Windows to me.
Is it any different over analogue?


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 17:59)allan87 Wrote: I have lost picture on most video with the new build. Here's the log, showing errors. I can do a debug log later if needed:

Have you disabled passthrough? I mentioned passthrough is not compatible with gui sounds.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-04

One playback issue I've noticed is when switching refresh rate - this issue is present in both todays builds, but not the build from 27 Nov.

I've got "Adjust display refresh rate to match video" set to "Always", and "Pause during refresh rate change" set to 3.2 seconds (approximately how long it takes for my monitor to sync a new resolution/refresh rate). My monitor runs the GUI at 1920x1080 @ 60Hz.

Previously when playing a video that required a refresh rate change (eg. 50Hz SD video on my 60Hz display), there would be silence and a black screen until the 3.2 seconds had elapsed, then the video & audio would begin.

Now, I'm seeing the initial frames of the video and hearing the audio (about 1/10th of a seconds worth), THEN black screen/silence until the 3.2 seconds has elapsed, at which point the video/audio starts again.

It's not a huge issue, but it would probably be better if the video & audio didn't start, stop, and then start again while changing refresh rate.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - evangelion - 2013-12-04

popcornmix, re: Gui sounds. Dunno, don't have an analogue means of playing, the RPi is piped into my AVR through HDMI.

I found the Bursting Bubbles folder in /usr/share/xbmc/sounds/ but overwriting the nav.wav doesn't alter the Gui sound (after rebooting also)


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-04

The GUI sounds on the Pi sound just like they do on my x86 Frodo system. Analogue sounded the same as HDMI.

Other than the limited number of sound "themes" (which is a skin/core issue), I'm not hearing any problem...


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 18:40)evangelion Wrote: popcornmix, re: Gui sounds. Dunno, don't have an analogue means of playing, the RPi is piped into my AVR through HDMI.

You don't have any headphones?


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - evangelion - 2013-12-04

(2013-12-04, 18:44)MilhouseVH Wrote: The GUI sounds on the Pi sound just like they do on my x86 Frodo system. Analogue sounded the same as HDMI.

Other than the limited number of sound "themes" (which is a skin/core issue), I'm not hearing any problem...

Which sound do you have it set to play? I think that might be the problem I'm having. On the Pi here, I have 2 options, Default or Bursting Bubbles.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-04

(2013-12-04, 18:49)evangelion Wrote: Which sound do you have it set to play? I think that might be the problem I'm having. On the Pi here, I have 2 options, Default or Bursting Bubbles.

I have it set to "Skin default" (in stock Confluence, this is the tac-tac-tac sound as you move through menu items). I also tried Bursting Bubbles, which quickly got on my nerves. The only other option is "Off".


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - evangelion - 2013-12-04

(2013-12-04, 18:49)popcornmix Wrote:
(2013-12-04, 18:40)evangelion Wrote: popcornmix, re: Gui sounds. Dunno, don't have an analogue means of playing, the RPi is piped into my AVR through HDMI.

You don't have any headphones?

Yep, just plugged them in, altered the output to Analogue and lo, we have the desired Gui sound. Changing it back to HDMI though produces a rather non-descript dull "thud" -like sound.

While still in the System>Audio menu, scrolling up and down is very hit and miss which item actually produces a sound, on Analogue, they ALL do?

EDIT: Skin Default sound used.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 18:37)MilhouseVH Wrote: Previously when playing a video that required a refresh rate change (eg. 50Hz SD video on my 60Hz display), there would be silence and a black screen until the 3.2 seconds had elapsed, then the video & audio would begin.

Now, I'm seeing the initial frames of the video and hearing the audio (about 1/10th of a seconds worth), THEN black screen/silence until the 3.2 seconds has elapsed, at which point the video/audio starts again.

It's not a huge issue, but it would probably be better if the video & audio didn't start, stop, and then start again while changing refresh rate.

Unfortunately video playback and HDMI mode change are not really synchronised. I believe when the first video frame has been submitted that the GUI gets notified of the resolution / framerate, and then the HDMI mode change happens soon after. Similarly the video/audio happens soon after.
I'm not aware of anything that has changed in that area, but there's nothing to stop it behaving in the way you describe.

You might want to experiment with setting the GUI mode to 1080p24 (or whatever your predominant video rate is) and enabling receiver keep-alive.
In theory you should have no HDMI switching delay for most videos. I'm not sure if the 23.976 vs 24 fps will still cause a switch (although that may be avoidable).

I can investigate if there's some way to detect if that the pause/unpause mode is enabled, and then skip the initial play+pause.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-04

(2013-12-04, 18:58)evangelion Wrote: Yep, just plugged them in, altered the output to Analogue and lo, we have the desired Gui sound. Changing it back to HDMI though produces a rather non-descript dull "thud" -like sound.

While still in the System>Audio menu, scrolling up and down is very hit and miss which item actually produces a sound, on Analogue, they ALL do?

EDIT: Skin Default sound used.

Sounds like your receiver may be going into an idle mode. You could try enabling the receiver keep-alive setting, although I don't think that will help.
Pretty sure hdmi and analogue sound the same with my receiver.


This forum uses Lukasz Tkacz MyBB addons.