2014-03-22, 07:10
+1 On this SQL library speed issue. Using an SSD causes XBMC to launch before network is available, and forces a reload in order to use it. Any chance a new build can include a fix for this?[
(2014-03-19, 04:51)KeithLM Wrote: I'm experimenting with this on my NUC and it's working fairly well, however I have one problem, since I'm using an SSD XBMC is starting before the network is fully up, preventing it from connecting to my sql server. At least that's what I suspect to be happening because XBMC comes up real quick. Restarting XBMC after the system has started gets it connected. Also I added "net-device-up IFACE!=lo" to /etc/init/lightdm.conf and then it successfully connected on boot. Can anybody offer a solution that won't get wiped out when installing future system updates?
I'm seeing a bit of tearing also. But I know there's threads on that so I'll look into those problems real quick. I had installed XBMCbuntu 12 then updated to 13 beta 2 and didn't notice any video issues, so I don't know if that's a new problem with the 64-bit version or what.
Initially it would only provide two channel sound. Removing PulseAudio fixed that issue. In fact it's better than what I had before since with the previous install DTS-HD wouldn't work. Why is PulseAudio installed? Isn't that nothing but trouble? Any time I see someone with audio trouble and PulseAudio the first piece of advice is remove Pulse. As soon as I rebooted after removing Pulse it was instant success. XBMC even had it on the correct device.
My bluetooth keyboard isn't working with this install, it did before. So that's another minor issue I have to look into.
Update
Tweaking the various video settings, sync and the like, seems to have eliminated any tearing problems. And running "apt-get install bluez-utils" has got my keyboard up and running. All-in-all this is a damn good build.
