beta2

[mk01]

(12th Sep, 2013 03:02 AM)namtih Wrote:  1) I was talking about this new Gotham feature:
http://wiki.xbmc.org/?title=advancedsettings.xml#.3Cnetwork.3E

2) Is it already implemented in xbian? Did someone already test it (Where is Rikardo, our XBMC specialist, by the way?)

3) The problem is, that it's already disabled. So that's why I'm a little but confused why it's still there and mounted.

Terminal

root@xbian ~ # more /etc/usbmount/usbmount.conf | grep ENABLE
ENABLED=0

I just remembered the Yo issues with the code changes in 4.4.4 -> 4.4.6 so answered this separately - the symptoms were exactly like buffering issues but had nothing to do with it.

The super ultra new buffering function is under development for 1 year maybe? Intelligent processes are indeed popular, but sometimes less is better.

Whether it is implemented, ask Koen. RPI version of XBMC is not following the standard cycles as the core was behind, but clever people making progress faster than all believed so many functions are back ported to any / all existing streams and for me it is not easily readable, so I'm not following.

And buffering in general (if not very very bad network) has reasons most of the time on other places - system overloaded - bad settings - bad programming (google add-on) etc.

3) You can double check usbmount with these steps:

Code:

umount /media/8B12-9112
umount /media/usbmount-root-btrfs
rmdir /media/*
DEVNAME=/dev/sda1 usbmount add
DEVNAME=/dev/sda2 usbmount add

and check mounts again. anyhow usbmount uses folder names with UUID. I would bet your xbmc is doing that. can be that you allowed it to mount through policy-kit ?

on standard xbian install, xbmc has right to umount, but not mount.