Login at Kodi Home

itsonlyme · 2012-09-24, 14:07

(2012-09-18, 14:25)itsonlyme Wrote: Version r11949

.mpg, and .ts files containing MPEG2 video, in 16x9 resolution play at 4x3 resolution (play OK with Raspbmc).

I do not know if this issue is the responsibility of OpenElec or XMBC. If not OpenElec please could you point it out to the appropriate person.

Also:-
Logitech K400 keyboard does not work every time. I have not noticed this with earlier versions of OpenElec, but it may well be the same problem referred to in the Raspberry Pi forums but which had not previously occurred with mine.

The display resolution is fixed with either build 11991 or my replacement of an HDMI switch. Sorry I cannot say which.

Many thanks.

hkramski · 2012-09-24, 23:26

Hi all,

after trying several flavours of XBMC on my RasPi I came (back) to OpenELEC because of the outstanding performance of the recent test images. However, there is a showstopper I never had with XBian 0.7.1 and other XMBCs based on Alpha5.

I'm using "hdmi_force_edid_audio=1" to enable AC3 pass through of my Samsung TV to its optical out. With this setting in effect, every video (SD, mpeg2, AC3) stutters massively, I get no sound and XMBC even sometimes crashes and gets restarted. In contrast to rduke's problem, I do not switch audio channels (most of my files only have one) but simply try to play an AC3 video.

This happens with r11949 (when I stepped in) up to the most recent r11989. A debug log is here: https://www.dropbox.com/s/ggox2t2zq68dnes/xbmc.log (full of audio errors).

With disabling hdmi_force_edid_audio all is well except for I only get stereo. In XBian 0.7.1 and earlier versions AC3 pass through was working well with my setup.

TIA
Heinz

Jester · (This post was last modified: 2012-09-25, 09:48 by Jester.)

Just FYI for the people who just upgraded to 11999 it seems to reset your screen resolution to 640x480 so make sure you set it to something higher before you ask why the resolution looks like crap after this update Wink

Mighty be due to:
https://github.com/xbmc/xbmc/commit/9779...b1fc757170

For the dev's, I don't know if you guys set a default res in guisettings.xml but it might need updating due to this change, again not sure, just sayin....

**sraue** · 2012-09-25, 23:47

Hi,

OpenELEC Development build (r12005):
http://sources.openelec.tv/tmp/image/ope...05.tar.bz2

to update a older build without reinstalling see:
http://wiki.openelec.tv/index.php?title=...g_OpenELEC

Not much changes, except for some updates:

updated XBMC to the last and greatest XBMC master checkout :-)
updated to Kernel linux 3.2.30 with some fixes for RaspberryPi support
updated RPi bootloader and drivers
various other improvenments, fixes and package updates

You can install HTS TVHeadend a PVR backend via XBMC's addon system
(go to: System/Settings/Add-ons/Services/hts-tvheadend install and reboot for more informations see:
http://wiki.openelec.tv/index.php?title=...dend_addon )

It is needed to update the bootloaderfiles which you can find in the build in the folder 3rdparty/bootloader it will be done automatically if you use a build 11766 or newer. For older builds you can update locally via Windows/Linux or via ssh:

login via ssh to your Raspi:
Code:
ssh root@<ipaddress>
remount /flash r/w:
Code:
mount -o remount,rw /flash
from your linux system copy the files via ssh/scp to the Raspi:
Code:
scp 3rdparty/bootloader/* root@<ipaddress>:/flash

because XBMC now supports officially RPi and PVR please use XBMC's Trac (http://trac.xbmc.org/) to report XBMC bugs and OpenELEC's github issue tracker (https://github.com/OpenELEC/OpenELEC.tv/issues) for OS related issues and feature/driver requests.

Milhouse · (This post was last modified: 2012-09-26, 00:12 by Milhouse.)

r12005 still sets the resolution back to 640x480 when it comes up - easily fixed with a visit to Settings and it remembers the correct setting on subsequent boots.

Strange though, as r11978 was happily using 1920x1080 prior to this update (I just copied over the thirdparty bootloader and target files).

Seems to be working well in all other respects (many thanks!)

fma965 · 2012-09-26, 12:11

(2012-09-26, 00:02)MilhouseVH Wrote: r12005 still sets the resolution back to 640x480 when it comes up - easily fixed with a visit to Settings and it remembers the correct setting on subsequent boots.

Strange though, as r11978 was happily using 1920x1080 prior to this update (I just copied over the thirdparty bootloader and target files).

Seems to be working well in all other respects (many thanks!)

it didn't for me

Milhouse · 2012-09-26, 12:20

For what it's worth, I just updated to r12006 and that booted fine at 1080p - may have been a one-off, or some other temporary glitch.

Jackdaw · 2012-09-26, 14:34

My TVCatchup 2.0 with EPG plugin crashes on r12006. It crashes just as it has finished opening the EPG. It works fine on Xbian. In fact it hasn't worked in any of the builds this month.

hkramski · 2012-09-26, 22:02

(2012-09-24, 23:26)hkramski Wrote: I'm using "hdmi_force_edid_audio=1" to enable AC3 pass through of my Samsung TV to its optical out. With this setting in effect, every video (SD, mpeg2, AC3) stutters massively, I get no sound and XMBC even sometimes crashes and gets restarted. In contrast to rduke's problem, I do not switch audio channels (most of my files only have one) but simply try to play an AC3 video.

This happens with r11949 (when I stepped in) up to the most recent r11989. A debug log is here: https://www.dropbox.com/s/ggox2t2zq68dnes/xbmc.log (full of audio errors).

Update: Problem still exists in r12005, but is limited to AC3 2 channel audio files, 6 channel AC3 files or 2 channel MPEG audio files are not affected. However, after playing one problematic (AC3 2 channel) video, all subsequent videos stutter with no sound (up to next reboot), which made me think all were affected. This now clearly looks like an XBMC bug to me; will file a ticket for that.

Heinz

Milhouse · 2012-09-27, 05:13

Just doing some tests with OpenELEC and fresh image installs (ie. empty ext4 partition) and noticed that r12006 continues to come up the first time in 640x480 (I'm using an LG IPS225 1920x1080@60 monitor).

**gimli** · 2012-09-27, 06:18

(2012-09-27, 05:13)MilhouseVH Wrote: Just doing some tests with OpenELEC and fresh image installs (ie. empty ext4 partition) and noticed that r12006 continues to come up the first time in 640x480 (I'm using an LG IPS225 1920x1080@60 monitor).

In XBMC or is the Resolotion on boot 640x480 ?

**sraue** · 2012-09-27, 06:43

(2012-09-27, 05:13)MilhouseVH Wrote: Just doing some tests with OpenELEC and fresh image installs (ie. empty ext4 partition) and noticed that r12006 continues to come up the first time in 640x480 (I'm using an LG IPS225 1920x1080@60 monitor).

what you get if you run "fbset". i have got a new tv recently and noticed wrong resolutions in "fbset" output... not sure if its because of the TV or a new build. also i could not set a resolution other then 1280x720, it only works if i use my hdmi switch...

Code:
root ~ # fbset 

mode "1x1-0"

    # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz

    geometry 1 1 1 1 32

    timings 0 0 0 0 0 0 0

    accel false

    rgba 8/0,8/8,8/16,8/24

endmode

Milhouse · (This post was last modified: 2012-09-27, 07:17 by Milhouse.)

(2012-09-27, 06:18)gimli Wrote: In XBMC or is the Resolotion on boot 640x480 ?

Only in XBMC - resolution on boot is native 1920x1080.

Just testing r12014 and it's the same, XBMC comes up as 640x480 (been testing OE for ages now, this resolution problem is only a recent issue).

(2012-09-27, 06:43)sraue Wrote: what you get if you run "fbset". i have got a new tv recently and noticed wrong resolutions in "fbset" output... not sure if its because of the TV or a new build. also i could not set a resolution other then 1280x720, it only works if i use my hdmi switch...

This is what I get with r12014:

Code:
root ~ # fbset

mode "1x1-0"

        # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz

        geometry 1 1 1 1 32

        timings 0 0 0 0 0 0 0

        accel false

        rgba 8/0,8/8,8/16,8/24

endmode

I can set XBMC to 1920x1080p @ 60 in Settings.

**gimli** · 2012-09-27, 07:50

(2012-09-27, 07:12)MilhouseVH Wrote:
(2012-09-27, 06:18)gimli Wrote: In XBMC or is the Resolotion on boot 640x480 ?

Only in XBMC - resolution on boot is native 1920x1080.

Just testing r12014 and it's the same, XBMC comes up as 640x480 (been testing OE for ages now, this resolution problem is only a recent issue).

Delete guisettings.xml and tell me what happens. No need to tell us the build number, we got it that this happens with recent releases.

(2012-09-27, 07:12)MilhouseVH Wrote:
(2012-09-27, 06:43)sraue Wrote: what you get if you run "fbset". i have got a new tv recently and noticed wrong resolutions in "fbset" output... not sure if its because of the TV or a new build. also i could not set a resolution other then 1280x720, it only works if i use my hdmi switch...

This is what I get with r12014:

Code:
root ~ # fbset mode "1x1-0" # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz geometry 1 1 1 1 32 timings 0 0 0 0 0 0 0 accel false rgba 8/0,8/8,8/16,8/24 endmode

I can set XBMC to 1920x1080p @ 60 in Settings.

Settings != fbset

Milhouse · (This post was last modified: 2012-09-27, 07:55 by Milhouse.)

(2012-09-27, 07:50)gimli Wrote:
(2012-09-27, 07:12)MilhouseVH Wrote:
(2012-09-27, 06:18)gimli Wrote: In XBMC or is the Resolotion on boot 640x480 ?

Only in XBMC - resolution on boot is native 1920x1080.

Just testing r12014 and it's the same, XBMC comes up as 640x480 (been testing OE for ages now, this resolution problem is only a recent issue).

Delete guisettings.xml and tell me what happens. No need to tell us the build number, we got it that this happens with recent releases.

I'm booting a fresh image - there is no guisettings.xml when it boots, just an empty ext4 partition.

FYI, my config.txt:

Code:
config_hdmi_boost=7

disable_overscan=1

So I'm not specifying any HDMI settings, other than overscan and boost to try and stop the HDMI from blanking periodically (doesn't stop it, unfortunately).

I'm currently trying to pin down SD corruption issues due to overclocking, hence why I'm testing with fresh images each time...