2013-02-05, 22:32
(2013-02-05, 13:27)Angelscry Wrote:(2013-02-05, 06:26)hunterx Wrote: So this Advanced Launcher won't automatically find my ROM's, but I think I read that's a bug currently?You need to perform a scan to add new item to a Launcher.
(2013-02-05, 04:45)gurgietrueshot Wrote:Thank for the report... Bad new it is not yet fixed.... I have to understand now WHY the launchers.xml file is corrupted at its begining an not, like most of the time, at its end.... Pleae could you confirm me that after the bug, the begining of the launchers.xml file is filed with spaces and and the first visible character is a ">".... because... heuuu... that's do not have any sens. The launchers.xml file is writed line by line. I can understand that first lines could be replaced by spaces... but not that a line was partially written...(2013-02-04, 22:58)Angelscry Wrote: Version 1.11.0:
This new version of Advanced Launcher attempt to fix all the annoying bugs appearing during the last days. It first fix the way thumbs and fanart images are saved during update/refresh. I'm not sure it will definitively fix the problem of launchers.xml file corruption (empty saved file) but for now I was not able to reproduce the problem. This version also rollback to the way used by version 1.10.15 to start windows application to avoid problem under Windows systems.
Changelog:Because previous version was really unstable, feedback on this version will be really appreciated.
- Fix launcher thumb image update/refresh.
- Fix launcher fanart image update/refresh.
- Rollback way to start Windows application as for version 1.10.15.
Well I was just about to post and say it appears to be fixed but I tried to change and overwrite some art in my Mame launcher and got the error again. This time it just knocked out the first few lines.
After error: http://pastebin.com/uFtF8rYP
Before Error: http://pastebin.com/w43ss6QH
xbmc.log: http://pastebin.com/yAGTF86q
The error at the end crashed XBMC after I set the launcher delay to 100ms
For the delay, If you do not have a fast computer and if the value is to small.... XBMC will effectively crash. Set the value to 1000ms... then decrease it to slowly until it not crash. For example on my different systems :
Windows 8 Laptop -> delay of 0 ms is ok.
Archlinux Laptop -> delay of 100 ms is ok.
Archlinux HTPC -> delay of 300 ms is ok.
The idea is to reduce to a maximum the delay between the moment of start the application and the moment you switch to this application. This delay was added since Frodo.... With Eden use delay was never needed.
(2013-02-05, 06:38)count_zero Wrote:Are you also be able to make it works using HDMI? I was able to make it work on my linux laptop system (using analogic output) but not on my linux HTPC system (using HDMI output).(2013-02-03, 16:37)Angelscry Wrote: This is how I have configured my linux system to have audio for applications started from XBMC Frodo. I'm using the Archlinux distribution, so I'm not sure this manipulation will be exactly the same for other distributions (Ubuntu, XBMCBuntu, Openelec, etc...). The main cause of the problem is that applications using pulseaudio (XBMC) and applications using ALSA (firefox, mednafen, etc...) cannot always play audio at the same time.
First you need to have ASLA and Pulseaudio packages installed on your system. This is the package I have installed on my systems :
alsa-firmware
alsa-lib
alsa-oss
alsa-utils
pulseaudio
pavucontrol
You have to check that the pulseaudio-alsa package is not installed on your system. If it is installed, just remove it.
Then you will have to edit the /etc/pulse/default.pa file.
First, found the lines refering to module-alsa-sink and module-alsa-source loading and edit them to indicated to use dmix and dsnoop parameters, like this :
Code:load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
Then, found the lines refering to module-udev-detect and module-detect and comment them, like this :
Code:# load-module module-udev-detect
# load-module module-detect
Save the /etc/pulse/default.pa file and reboot your system.
Thanks!
I can confirm this works. I'm not a huge fan of pulseaudio, but this is a workaround.
You need to set your audio playback preferences in XBMC to pulseaudio.
Yes, I only use HDMI for audio output. I have not tested analog or optical audio out.