2014-02-11, 16:43
mediainfo
(2014-02-11, 19:49)Trixster Wrote: max_clock_drift=100
max_clock_drift_rate=100
on my 512mb pi makes xbmc lock up if youtube videos are paused for longer than about 10seconds. Without these in config.txt there are no such issues.
(2014-02-11, 20:21)Trixster Wrote: Pretty sure mate, I had 5 youtube clips crash on me back to back with those options in config.txt. I then #'ed the two lines out and now no clips when paused seem to make xbmc hang. Ill do some more testing after the Olympic half pipe finishes!Aside from editing out the lines, you also rebooted. the rebooting may have alleviated the problem.
(2014-02-11, 21:39)allan87 Wrote:(2014-02-11, 20:21)Trixster Wrote: Pretty sure mate, I had 5 youtube clips crash on me back to back with those options in config.txt. I then #'ed the two lines out and now no clips when paused seem to make xbmc hang. Ill do some more testing after the Olympic half pipe finishes!Aside from editing out the lines, you also rebooted. the rebooting may have alleviated the problem.
(2014-02-12, 00:19)Trixster Wrote: I had rebooted after every lock up, and rebooted after each change to config.txt to try and replicate the lock ups. Storage is a 16gb usb drive which is what I'm running the system from. The sd card is an 8gb class 10 card. The pi is a 512mb model. I don't think I'm running out of space. I do not believe I am caching to the usb stick or the sd card. I have no other particular settings or tweaks in either config.txt or advancedsettings which might have given rise to the problem. The only change was the two extra lines of text which i added to config.txt yesterday evening. This afternoon was the first time I'd tried streaming youtube clips since making those two amendments. That 5 separate 720p streams crashed xbmc after having left been on pause for a few minutes each time is what led me to believe the new settings were to blame. Taking those two lines out fixed the issue, and that's what made me make my original post.
It's frustrating that I can't seem to replicate it now, hence my second post!
I am not running a steam now, but df -h gives this:
Filesystem Size Used Available Use% Mounted on
devtmpfs 121.4M 0 121.4M 0% /dev
/dev/mmcblk0p1 124.7M 103.4M 21.4M 83% /flash
/dev/sda 14.0G 1.0G 12.2G 8% /storage
/dev/loop0 93.3M 93.3M 0 100% /
tmpfs 122.9M 0 122.9M 0% /dev/shm
tmpfs 122.9M 356.0K 122.5M 0% /run
tmpfs 122.9M 0 122.9M 0% /sys/fs/cgroup
tmpfs 122.9M 24.0K 122.9M 0% /var
tmpfs 122.9M 4.0K 122.9M 0% /tmp
I had a similar problem with a Microsoft MCE remote clone on Ubuntu 12.04 and XBMC 12.3. For anyone who's interested, a simple workaround is to redefine the remote's volume up and down buttons using xmodmap, and then change XBMC's keymaps accordingly. For example, enter the following in ~/.Xmodmap:
keycode 122 = F13
keycode 123 = F14
and the following in ~/.xbmc/userdata/keymaps/keyboard.xml:
<keymap>
<global>
<keyboard>
<f13>VolumeDown</f13>
<f14>VolumeUp</f14>
</keyboard>
</global>
</keymap>
(2014-02-12, 15:17)doveman2 Wrote: Regarding the issue where the remote volume keys don't repeat, which is apparently an OS-level bug as XBMC doesn't do the repeating itself but relies on the OS to handle this, I wonder if this workaround for Ubuntu can be used with OE?
(2014-02-12, 21:16)dhead Wrote: Raspberry Pi builds doesn't include X.org so this is no go (and this solution only works for keyboards and not for keypress send by lirc).
From a quick googling I guess your remote recognized as keyboard.
Sadly the current state of keyboard support in XBMC is a bit of a mess, with the Raspberry Pi XBMC gets scancodes from the kernel, on OpenELEC x86_64 and i686 from X.Org and on regular Linux distribution from SDL, this is true for Frodo and Gotham.
I've already encountered with the issue you described and more but I didn't thought it worth reporting as the whole keyboard situation seems to me very funny and with Wayland soon on my desktop (Gnome 3.12 next month) I probably will have more issues.