2017-09-11, 04:47
Yeah, my setup runs into those two problems as well. Once AEL is no longer blocking we can replace the kill command with an equivalent kodi-send quit. That will be a much more stable solution as well.
(2017-09-11, 15:58)yevaman44 Wrote: Hi again ,
I use AEL with zephyr skin and I have a problem with my screenshot that are too big.
I dunno if it's ael related but can you tell me to reduce the resolution of thoses pics to fit the box perfectly ?
where can I find the xml or code ?
Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
Mega Drive - Retroarch (Linux wrapper Retropie).xml
Mega Drive - Retroarch (Linux wrapper LibreELEC).xml
./Launchers artwork SEGA/ -> has artwork and metadata NFO files for SEGA platform
./Launchers XML Linux/ -> has XML configurations for standard Linux (all platforms in one directory)
./Launchers XML Linux wrapper/ -> has XML configurations for standard Linux (using a wrapper script to close/open Kodi)
./Launchers XML Linux RetroPie/ -> has XML configurations for RetroPie (using a wrapper script to close/open Kodi)
./Launchers XML Linux LibreELEC/ -> has XML configurations for LibreELEC (using a wrapper script to close/open Kodi)
./Launchers XML Windows/ -> has XML configurations for Windows
./Launchers XML Android/ -> has XML configurations for Android
(2017-09-12, 14:40)Wintermute0110 Wrote: @crono141 Your idea of creating a temporary file with AEL's categoryID, launcherID and romID and then using autoexec.py is a really good one! I will maybe modify my script to include it. Also, have a look at this post in the Gamestarter addon that describes the latest AEL development. I think I could add your script for RetroPie to the AEL asset library including the launching scripts to simplify the configuration.
@everyone Let me summarise the current status of 0.9.7:
1) More or less AEL is ready for a 0.9.7 release, as you can see in the changelog. Currently I have to make sure the scrapers in the ROM scanner use cached contents which I estimate about 8 hours of coding. Also, the feature of creating Parent/Clone groups using the filenames of the ROMs have proven challeging because currently the No-Intro/Redump audit code is coupled with the Parent/Clone group generation. I think I will move that feature for 0.9.8 to not delay the release of 0.9.7.
Note that AEL 0.9.7 will require Kodi Krypton and up (Jarvis is not supported any more).
2) This and next week I'm going to be really busy with real life, but I will have a free-time window over the last week of September. I will try to make a release of 0.9.7-beta1 around then.
3) With the addition of the new XML configurations and wrapper scripts to use AEL in LibreELEC and RetroPie distributions I may have to think on a new layout for the AEL asset library. For example, configurations for SEGA now look like this (example from Launchers - SEGA directory):
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
The artwork and the XML configurations are on the same directory. However, if I include more configurations like this:
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
Mega Drive - Retroarch (Linux wrapper Retropie).xml
Mega Drive - Retroarch (Linux wrapper LibreELEC).xml
We can end with a lot of XML files on the same folder which can be confusing for some people! Maybe the configurations can be separated for each platform:
Code:./Launchers artwork SEGA/ -> has artwork and metadata NFO files for SEGA platform
./Launchers XML Linux/ -> has XML configurations for standard Linux (all platforms in one directory)
./Launchers XML Linux wrapper/ -> has XML configurations for standard Linux (using a wrapper script to close/open Kodi)
./Launchers XML Linux RetroPie/ -> has XML configurations for RetroPie (using a wrapper script to close/open Kodi)
./Launchers XML Linux LibreELEC/ -> has XML configurations for LibreELEC (using a wrapper script to close/open Kodi)
./Launchers XML Windows/ -> has XML configurations for Windows
./Launchers XML Android/ -> has XML configurations for Android
What do you (everybody) think?
(2017-09-12, 14:40)Wintermute0110 Wrote: @crono141 Your idea of creating a temporary file with AEL's categoryID, launcherID and romID and then using autoexec.py is a really good one! I will maybe modify my script to include it. Also, have a look at this post in the Gamestarter addon that describes the latest AEL development. I think I could add your script for RetroPie to the AEL asset library including the launching scripts to simplify the configuration.
@everyone Let me summarise the current status of 0.9.7:
1) More or less AEL is ready for a 0.9.7 release, as you can see in the changelog. Currently I have to make sure the scrapers in the ROM scanner use cached contents which I estimate about 8 hours of coding. Also, the feature of creating Parent/Clone groups using the filenames of the ROMs have proven challeging because currently the No-Intro/Redump audit code is coupled with the Parent/Clone group generation. I think I will move that feature for 0.9.8 to not delay the release of 0.9.7.
Note that AEL 0.9.7 will require Kodi Krypton and up (Jarvis is not supported any more).
2) This and next week I'm going to be really busy with real life, but I will have a free-time window over the last week of September. I will try to make a release of 0.9.7-beta1 around then.
3) With the addition of the new XML configurations and wrapper scripts to use AEL in LibreELEC and RetroPie distributions I may have to think on a new layout for the AEL asset library. For example, configurations for SEGA now look like this (example from Launchers - SEGA directory):
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
The artwork and the XML configurations are on the same directory. However, if I include more configurations like this:
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
Mega Drive - Retroarch (Linux wrapper Retropie).xml
Mega Drive - Retroarch (Linux wrapper LibreELEC).xml
We can end with a lot of XML files on the same folder which can be confusing for some people! Maybe the configurations can be separated for each platform:
Code:./Launchers artwork SEGA/ -> has artwork and metadata NFO files for SEGA platform
./Launchers XML Linux/ -> has XML configurations for standard Linux (all platforms in one directory)
./Launchers XML Linux wrapper/ -> has XML configurations for standard Linux (using a wrapper script to close/open Kodi)
./Launchers XML Linux RetroPie/ -> has XML configurations for RetroPie (using a wrapper script to close/open Kodi)
./Launchers XML Linux LibreELEC/ -> has XML configurations for LibreELEC (using a wrapper script to close/open Kodi)
./Launchers XML Windows/ -> has XML configurations for Windows
./Launchers XML Android/ -> has XML configurations for Android
What do you (everybody) think?
(2017-09-12, 14:40)Wintermute0110 Wrote: 3) With the addition of the new XML configurations and wrapper scripts to use AEL in LibreELEC and RetroPie distributions I may have to think on a new layout for the AEL asset library. For example, configurations for SEGA now look like this (example from Launchers - SEGA directory):
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
The artwork and the XML configurations are on the same directory. However, if I include more configurations like this:
Code:Mega Drive - Fusion (Windows).xml
Mega Drive - Retroarch (Linux).xml
Mega Drive - Retroarch (Linux wrapper).xml
Mega Drive - Retroarch (Linux wrapper Retropie).xml
Mega Drive - Retroarch (Linux wrapper LibreELEC).xml
We can end with a lot of XML files on the same folder which can be confusing for some people! Maybe the configurations can be separated for each platform:
Code:./Launchers artwork SEGA/ -> has artwork and metadata NFO files for SEGA platform
./Launchers XML Linux/ -> has XML configurations for standard Linux (all platforms in one directory)
./Launchers XML Linux wrapper/ -> has XML configurations for standard Linux (using a wrapper script to close/open Kodi)
./Launchers XML Linux RetroPie/ -> has XML configurations for RetroPie (using a wrapper script to close/open Kodi)
./Launchers XML Linux LibreELEC/ -> has XML configurations for LibreELEC (using a wrapper script to close/open Kodi)
./Launchers XML Windows/ -> has XML configurations for Windows
./Launchers XML Android/ -> has XML configurations for Android
What do you (everybody) think?
(2017-09-14, 02:21)htpc guy Wrote: Does this addon support roms that are stored on an SMB share? It feels like I have everything set up correctly but my roms are not launching successfully.Artwork could be on a network share or remote but ROMs must be on a locally mounted filesystem. Reason is that emulators do not support remote files! That will change for Kodi Retroplayer but for now ROMs must be on a local filesystem (note that you can mount your smb share to make it available locally)
New Launcher setup
Launcher: c:\program files\Dolphin\Dolphin.exe
Rom Path: \\server\games\wii
Rom Extension: ciso
Rom Arguments: -b -e $rom$"
When I launch a rom I get the following error from Dolphin when it launches: The specified file "\server\Games\Wii\Gametitle.ciso" does not exist
Obviously the path is incorrectly formed for a network path. However the kodi log shows the final argument as:
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() apppath "C:\Program Files\Dolphin"
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() romext "ciso"
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() raw arguments "-b -e "$rom$""
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() final arguments "-b -e "\\FREENAS\Software\Roms\Game Library\Wii\MarioKartWii (USA).ciso""
19:14:28.124 T:14972 ERROR: AEL INFO : fs_write_Favourites_JSON() File special://profile/addon_data\plugin.program.advanced.emulator.launcher\most_played.json
(2017-09-14, 10:39)Wintermute0110 Wrote:(2017-09-14, 02:21)htpc guy Wrote: Does this addon support roms that are stored on an SMB share? It feels like I have everything set up correctly but my roms are not launching successfully.Artwork could be on a network share or remote but ROMs must be on a locally mounted filesystem. Reason is that emulators do not support remote files! That will change for Kodi Retroplayer but for now ROMs must be on a local filesystem (note that you can mount your smb share to make it available locally)
New Launcher setup
Launcher: c:\program files\Dolphin\Dolphin.exe
Rom Path: \\server\games\wii
Rom Extension: ciso
Rom Arguments: -b -e $rom$"
When I launch a rom I get the following error from Dolphin when it launches: The specified file "\server\Games\Wii\Gametitle.ciso" does not exist
Obviously the path is incorrectly formed for a network path. However the kodi log shows the final argument as:
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() apppath "C:\Program Files\Dolphin"
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() romext "ciso"
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() raw arguments "-b -e "$rom$""
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() final arguments "-b -e "\\FREENAS\Software\Roms\Game Library\Wii\MarioKartWii (USA).ciso""
19:14:28.124 T:14972 ERROR: AEL INFO : fs_write_Favourites_JSON() File special://profile/addon_data\plugin.program.advanced.emulator.launcher\most_played.json
Sent from my SC-02G (typie typie)
(2017-09-15, 02:43)htpc guy Wrote:(2017-09-14, 10:39)Wintermute0110 Wrote:(2017-09-14, 02:21)htpc guy Wrote: Does this addon support roms that are stored on an SMB share? It feels like I have everything set up correctly but my roms are not launching successfully.Artwork could be on a network share or remote but ROMs must be on a locally mounted filesystem. Reason is that emulators do not support remote files! That will change for Kodi Retroplayer but for now ROMs must be on a local filesystem (note that you can mount your smb share to make it available locally)
New Launcher setup
Launcher: c:\program files\Dolphin\Dolphin.exe
Rom Path: \\server\games\wii
Rom Extension: ciso
Rom Arguments: -b -e $rom$"
When I launch a rom I get the following error from Dolphin when it launches: The specified file "\server\Games\Wii\Gametitle.ciso" does not exist
Obviously the path is incorrectly formed for a network path. However the kodi log shows the final argument as:
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() apppath "C:\Program Files\Dolphin"
19:14:28.097 T:14972 ERROR: AEL INFO : _command_run_rom() romext "ciso"
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() raw arguments "-b -e "$rom$""
19:14:28.104 T:14972 ERROR: AEL INFO : _command_run_rom() final arguments "-b -e "\\FREENAS\Software\Roms\Game Library\Wii\MarioKartWii (USA).ciso""
19:14:28.124 T:14972 ERROR: AEL INFO : fs_write_Favourites_JSON() File special://profile/addon_data\plugin.program.advanced.emulator.launcher\most_played.json
Sent from my SC-02G (typie typie)
I have no problems manually launching roms for Dolphin, or Retroarch using UNC paths. I can launch them from the emulators or from command line. Launchbox doesn't seem to have an issue with it either but I would much prefer to use Kodi.