Kodi Community Forum
Beta Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Game Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=291)
+---- Thread: Beta Advanced Emulator Launcher - Multi-emulator frontend for Kodi (/showthread.php?tid=287826)



RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - axlt2002 - 2016-12-07

(2016-12-07, 11:53)Wintermute0110 Wrote: @axlt2002 and @coremailrx8 The "launching app not found lnk_launcher_app" bug was fixed on 0.9.5 some time ago. However, development of 0.9.5 has been going on. Currently master branch on Github is quite unstable: 0.9.5 introduces much more features than any other previous release and currently I'm testing everything and solving small bugs here and there introduced by changes in the code due to new features.

@axlt2002 I only have Linux machines so I myself do not use LNK launcher at all!

@axlt2002 Yes, Github master reports 0.9.3 because I forgot to update the AEL version in release 0.9.4. Once 0.9.5 is ready for the masses I will bump the version to 0.9.5.

Thanks Wintermute0110 for your answer.

Well, the acutual version downloaded from github makes what it is supposed to do for Windows games. I just hope you can fix the two refinements I have reported in my post:

- Nfo, assets and artworks can be manually added in a second step but having it done while adding the LNK would be more comfortable (and this is working in the actual 0.9.4)
- For the MS-DOS command window, it would be nice to have it launched minimized. I suppose that there is a line in AEL code where "cmd.exe" (or "start.exe"?) is executed...

I'm of course available for any kind of test you would need on a Windows machine. Nod


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - kiaenigma27 - 2016-12-07

(2016-12-07, 11:46)Wintermute0110 Wrote:
(2016-12-07, 01:51)kiaenigma27 Wrote: Guys this has probably been asked a million times but i cant find an answer.

Managed to import all of my systems and games and all is working a treat.. last thing I need to do is sort out the displayed names for my MAMe roms.

what do you have to do to get it to display the game name rather than the rom zip file name?

I guessed you might need a DAt file for some kind but cannot find one for mame.

No need for additional DATs. AEL includes an offline scraper for MAME and some other systems that works out-of-the-box. Currently only some systems are included (you can see which ones here) and as soon as possible I will include databases for all platforms.

When scanning MAME ROMs, go to AEL addon settings, on tab "ROM scanner" make sure both "Ignore Scrapped Titles (use ROM filenames instead)" and "Clean No-Intro/TOSEC Title Tags" are unchecked. Delete all your ROMs from MAME launcher and rescan. Now the MAME ROMs will have the correct title/name and metadata (except plot).

Note that for No-Intro ROMs I recommend to check the "Ignore Scrapped Titles (use ROM filenames instead)" option.

thanks for this although i tried it and roms still show with their abbreviated zip names

So just to be sure i have everything setup right.

Clear my roms list from mame.

Under Rom scanner i have

Metadata scan policy: NFO Files
Assett scan policy: Local Images
Ignore scraped titles: unchecked
Clean no intro: unchecked

then under rom scrpaing i have

Metadata scraping: Offline scrpaer

this still only shows rom file names

what have i done wrong


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-08

(2016-12-07, 21:38)kiaenigma27 Wrote: thanks for this although i tried it and roms still show with their abbreviated zip names

So just to be sure i have everything setup right.

Clear my roms list from mame.

Under Rom scanner i have

Metadata scan policy: NFO Files
Assett scan policy: Local Images
Ignore scraped titles: unchecked
Clean no intro: unchecked

then under rom scrpaing i have

Metadata scraping: Offline scrpaer

this still only shows rom file names

what have i done wrong

All settings OK except:

Metadata scan policy: "NFO Files + Scrapers" OR "Scrapers only"

"Scrapers only" is self explanatory. "NFO Files + Scrapers" will load first the ROM NFO file if it exists. If it does not exists then it will use the scraper selected on "Metadata scraping".


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-08

(2016-12-07, 14:39)axlt2002 Wrote: - Nfo, assets and artworks can be manually added in a second step but having it done while adding the LNK would be more comfortable (and this is working in the actual 0.9.4)

I don't quite understand what you mean. When you create the LNK launcher you configure the ROM path (LNK path actually), asset directory, etc. Then, when you scan for ROMs if when NFO files and assets are loaded. What is the feature broken in current master branch compared to 0.9.4?

(2016-12-07, 14:39)axlt2002 Wrote: - For the MS-DOS command window, it would be nice to have it launched minimized. I suppose that there is a line in AEL code where "cmd.exe" (or "start.exe"?) is executed...

Mmm... that's something related to Windows itself. I don't know if it can be solved easily. I will try to do some tests on a Windows machine, maybe changing the arguments. This is the line of code that launchers LNK files. Currently I use the /b argument. Any ideas?


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - kiaenigma27 - 2016-12-08

(2016-12-08, 06:18)Wintermute0110 Wrote:
(2016-12-07, 21:38)kiaenigma27 Wrote: thanks for this although i tried it and roms still show with their abbreviated zip names

So just to be sure i have everything setup right.

Clear my roms list from mame.

Under Rom scanner i have

Metadata scan policy: NFO Files
Assett scan policy: Local Images
Ignore scraped titles: unchecked
Clean no intro: unchecked

then under rom scrpaing i have

Metadata scraping: Offline scrpaer

this still only shows rom file names

what have i done wrong

All settings OK except:

Metadata scan policy: "NFO Files + Scrapers" OR "Scrapers only"

"Scrapers only" is self explanatory. "NFO Files + Scrapers" will load first the ROM NFO file if it exists. If it does not exists then it will use the scraper selected on "Metadata scraping".

sorted thank you


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - kiaenigma27 - 2016-12-08

Not sure if this helps anyone but I found out how to get AEL to launch MAME roms with Mame4droid... seems to be no info online but was pretty easy to work out

to use mame4droid with AEL the below argument seems to work (i use shield TV)

start --user 0 -n com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid -a android.intent.action.VIEW -eu Uri "file://%rom%"


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - axlt2002 - 2016-12-08

(2016-12-08, 06:24)Wintermute0110 Wrote:
(2016-12-07, 14:39)axlt2002 Wrote: - Nfo, assets and artworks can be manually added in a second step but having it done while adding the LNK would be more comfortable (and this is working in the actual 0.9.4)
I don't quite understand what you mean. When you create the LNK launcher you configure the ROM path (LNK path actually), asset directory, etc. Then, when you scan for ROMs if when NFO files and assets are loaded. What is the feature broken in current master branch compared to 0.9.4?
Sorry if I was not clear. You got the point by the way: with 0.9.4 the NFO files and the assets are loaded during the scanning of the ROMs...in the current master branch this doesn't happen. I'm just guessing this issue can be related to the fix you made in the master branch to have the LNKs working properly. Any guess on your side?
(2016-12-08, 06:24)Wintermute0110 Wrote:
(2016-12-07, 14:39)axlt2002 Wrote: - For the MS-DOS command window, it would be nice to have it launched minimized. I suppose that there is a line in AEL code where "cmd.exe" (or "start.exe"?) is executed...
Mmm... that's something related to Windows itself. I don't know if it can be solved easily. I will try to do some tests on a Windows machine, maybe changing the arguments. This is the line of code that launchers LNK files. Currently I use the /b argument. Any ideas?
I think is a python command, so there should be some documentation where the arguments that the funciotn os.system() can accept are explained. Do you know if this is a standard python command or it has been overwritten somewhere in the Kodi code?


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-09

(2016-12-08, 19:35)axlt2002 Wrote: Sorry if I was not clear. You got the point by the way: with 0.9.4 the NFO files and the assets are loaded during the scanning of the ROMs...in the current master branch this doesn't happen. I'm just guessing this issue can be related to the fix you made in the master branch to have the LNKs working properly. Any guess on your side?

So the problem is that the ROM scanner do not load NFO files and local assets. OK, will have a look.

(2016-12-08, 19:35)axlt2002 Wrote: I think is a python command, so there should be some documentation where the arguments that the funciotn os.system() can accept are explained. Do you know if this is a standard python command or it has been overwritten somewhere in the Kodi code?

Yes, indeed is a Python function belonging to the os module. The code I use to launch LNK files is equivalent to this:

Code:
start "AEL" /b "lnk_file.lnk"

The problem is not in AEL, is in the Windows command start which is the one that opens the Window. My original question is if there is an alternative way of launching LNK files in Window which doesn't open a console (so called "MS-DOS window").

Also, to everyone: AEL 0.9.5 is being delayed for two reasons: first, a lot of new features were added (including a new Arcade Database MAME scraper and a new totally rewritten filesystem layer that enables assets to be in network units) and second, I've been quite busy with real life. I plan to release 0.9.5 ASAP but expect small bugs due to massive changes in the code. A "small bug" is one that can be solved by doing a small change in the code (like wrong variable name, etc.).

For 0.9.6, I plan to upgrade the launching mechanism to use the Python subprocess module. 0.9.7 will include offline scrapers for all AEL platforms.


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - axlt2002 - 2016-12-09

(2016-12-09, 12:11)Wintermute0110 Wrote:
(2016-12-08, 19:35)axlt2002 Wrote: Sorry if I was not clear. You got the point by the way: with 0.9.4 the NFO files and the assets are loaded during the scanning of the ROMs...in the current master branch this doesn't happen. I'm just guessing this issue can be related to the fix you made in the master branch to have the LNKs working properly. Any guess on your side?

So the problem is that the ROM scanner do not load NFO files and local assets. OK, will have a look.

Exactly! Thanks for giving a look to that. Smile

(2016-12-09, 12:11)Wintermute0110 Wrote:
(2016-12-08, 19:35)axlt2002 Wrote: I think is a python command, so there should be some documentation where the arguments that the funciotn os.system() can accept are explained. Do you know if this is a standard python command or it has been overwritten somewhere in the Kodi code?

Yes, indeed is a Python function belonging to the os module. The code I use to launch LNK files is equivalent to this:

Code:
start "AEL" /b "lnk_file.lnk"

The problem is not in AEL, is in the Windows command start which is the one that opens the Window. My original question is if there is an alternative way of launching LNK files in Window which doesn't open a console (so called "MS-DOS window").

Ok, I undrestand. I took a look around Internet to find something that could be useful. The only thing that I saw is the /MIN argument in addition to /b you are already using. But I'm not sure this is the way to go...
Anyway, the "user transparent bahaviour" is perfect when a launcher to a specific .exe is created: in this case there is no MS-DOS windows (or console) opened. Personally I think I will go for this solution. The drawbak is that I have to create a launcher for every game/application (not a big issue btw). Going this way, I have noticed these to things:

- As per the ROM scanner, also the creation of the launcher for a game/application (.exe file) is not loading the .nfo and assets
- I have tried to create a .nfo file of an .exe application and the structure is different from the ROM one. For the ROM is the following:

Code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<game>
  <title></title>
  <year></year>
  <genre></genre>
  <publisher></publisher>
  <rating></rating>
  <plot></plot>
</game>

while for the application is:

Code:
<launcher>
    <title></title>
    <platform></platform>
    <year></year>
    <publisher></publisher>
    <genre></genre>
    <plot></plot>
</launcher>

Do you think this would be an issue when there will be skins supporting the visualization of the information?

(2016-12-09, 12:11)Wintermute0110 Wrote: Also, to everyone: AEL 0.9.5 is being delayed for two reasons: first, a lot of new features were added (including a new Arcade Database MAME scraper and a new totally rewritten filesystem layer that enables assets to be in network units) and second, I've been quite busy with real life. I plan to release 0.9.5 ASAP but expect small bugs due to massive changes in the code. A "small bug" is one that can be solved by doing a small change in the code (like wrong variable name, etc.).

For 0.9.6, I plan to upgrade the launching mechanism to use the Python subprocess module. 0.9.7 will include offline scrapers for all AEL platforms.

You don't have to excuse yourself Wintermute0110!!! Take your time...your work is just amazing!!! Thanks!


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-09

(2016-12-09, 12:37)axlt2002 Wrote: Ok, I undrestand. I took a look around Internet to find something that could be useful. The only thing that I saw is the /MIN argument in addition to /b you are already using. But I'm not sure this is the way to go...

Anyway, the "user transparent bahaviour" is perfect when a launcher to a specific .exe is created: in this case there is no MS-DOS windows (or console) opened.

OK, I will try the /MIN parameter, but I'm not sure if that will work. The console if opened by the start.exe command, not by AEL, so I don't know if I can solve that issue. Also, I'm not currently aware of an alternative way of launching LNK files apart from start.exe.

(2016-12-09, 12:37)axlt2002 Wrote: Personally I think I will go for this solution. The drawbak is that I have to create a launcher for every game/application (not a big issue btw). Going this way, I have noticed these to things:

- As per the ROM scanner, also the creation of the launcher for a game/application (.exe file) is not loading the .nfo and assets
- I have tried to create a .nfo file of an .exe application and the structure is different from the ROM one. For the ROM is the following:

Code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<game>
  <title></title>
  <year></year>
  <genre></genre>
  <publisher></publisher>
  <rating></rating>
  <plot></plot>
</game>

while for the application is:

Code:
<launcher>
    <title></title>
    <platform></platform>
    <year></year>
    <publisher></publisher>
    <genre></genre>
    <plot></plot>
</launcher>

Do you think this would be an issue when there will be skins supporting the visualization of the information?

Launcher and ROM NFO files are different because the metadata of a Launcher and metadata for ROMs is different. Notably, "platform" is a property of the launcher, not the ROM.

The ROM scanner is only intended for ROMs, not for Launchers. Using the trick to creating LNK files from game EXE files, you are effectively converting Standalone launchers to ROMs of a special ROM LNK launcher. ROM NFO files and assets are loaded by the ROM scanner. However, Launcher NFOs/assets cannot.

The reason is that assets for Launchers are all of them stored on the same directory and the Launcher fingerprint is part of the filename (to allow 2 launchers with same name not to overwrite assets with each other). Since the fingerprint is random and not known until launcher has been created this means no NFO/assets for the Launcher can be loaded. For ROMs the situation changes: the NFO files/assets have exactly the same filename as the ROM, and there cannot be 2 ROMs with same filename on the same launcher, so the ROM scanner can load them without knowing the ROM fingerprint. Actually, if you deleted ROMs from a Launcher and rescan again, all ROMs will have completely different fingerprints. Have a look at this post for more details.

Of course this is how things work at the moment. If you have a good idea than can be implemented and most important, do not break current stuff, please share it.

In order to fully support AEL, skins have to implement at least 3 views: one view for Categories/Launchers, one view for No-Intro ROMs and one view for MAME ROMs. Categories/Launchers views will be simpler than ROM views cos the former has much less assets.

(2016-12-09, 12:37)axlt2002 Wrote: You don't have to excuse yourself Wintermute0110!!! Take your time...your work is just amazing!!! Thanks!

Thanks! I was not excusing myself, just telling everybody the current plans (which may change on the way Big Grin)


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - axlt2002 - 2016-12-09

Thanks for your great explanation Wintermute0110! Everything is really clear now...lets see if the /MIN argument will have some result otherwise I will go for the standalone launcher option.

Keep in touch for the next relases of the addon. Of course I'm always available to help you with some testing if needed.

For the time being...have a nice and relaxing weekend!


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - kiaenigma27 - 2016-12-12

Sorry guys me again..

So just bought a second shield TV for the cinema room and want to copy the setup from my first shield tv.. what the easiest way?

I thought the kodi backup addon would work but it doesnt.

can i just copy the folders from the addon & user data folders inside kodi?

i copied over the categories xml & settings xml but it gives me an error when trying to browse the roms that launcher cant be found


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-12

(2016-12-12, 16:24)kiaenigma27 Wrote: Sorry guys me again..

So just bought a second shield TV for the cinema room and want to copy the setup from my first shield tv.. what the easiest way?

I thought the kodi backup addon would work but it doesnt.

can i just copy the folders from the addon & user data folders inside kodi?

i copied over the categories xml & settings xml but it gives me an error when trying to browse the roms that launcher cant be found

No worries, this thread is for AEL support Big Grin

On the second Kodi setup install AEL as usual. Then, transfer all you ROMs directories and assets directories to the second setup. Finally, make a zip file with the contents of your USER_DIR/addon_data/plugin.program.advanced.emulator.launcher/ Unzip that in the second setup under USER_DIR/addon_data. IF the ROM paths AND the asset paths are exactly the same on both setups then AEL will show no errors. If you also installed exactly the same emulators in exactly the same paths launching will also work.

In case you need to change the ROM paths for every launcher you can do on "Edit Launcher" context menu and then rescan. Same for artwork paths. Currently you have to change artwork path by path (that is, change titles first, snaps second, etc.). An option can be added to AEL to change all paths at once (by selecting the parent directory that contains all assets subdirectories, just same as when you create a new launcher). If emulator executables are on different paths then you will have to edit the launcher executable for every launcher also.

Edit: if for some reason you have to change ROM paths, assets paths, etc. on the second setup, I think the quickest way is it to manually edit the file categories.xml. Make a backup first in case you screw up. Then, carefully using Search and Replace you can do it much quicker than using AEL's graphical user interface. If you use Windows for editing categories.xml I recommend Notepad++ editor.


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - kiaenigma27 - 2016-12-12

Thanks. all my roms and assets are on a central server thats mapped on both shield tv's so the address are the same


RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2016-12-12

(2016-12-12, 18:14)kiaenigma27 Wrote: Thanks. all my roms and assets are on a central server thats mapped on both shield tv's so the address are the same

OK... in that case, it is necessary to copy all files/directories (and replicate the directory structure) inside USER_DIR/addons/plugin.program.advanced.emulator.launcher. If you just copied categories.xml and not the ROM databases then categories/launchers are configured but then when you try to browse a launcher AEL will say "Launcher empty. JSON/XML not found" or something like that.

Easiest way of transferring USER_DIR/addons/plugin.program.advanced.emulator.launcher is to pack into a ZIP/TAR/RAR file (recursive) and then extract on the destination machine.

Edit: having a complex file/directory structure and just not a single 'launchers.xml' like old good Advanced Launcher is the price to pay for AEL's speed and stability (little price anyway cos a normal user will never need to access USER_DIR/addons/plugin.program.advanced.emulator.launcher). Once 1.0.0 is released and the database format more or less fixed I will add a page on the wiki so power users can edit or make tools to generate ROM databases AEL can use.

Edit 2: by the way, although AEL is now much more stable than AL in terms of keeping ROM database integrity, there is a small possibility that databases can be destroyed by concurrency. Nobody has ever reported this problem so far, but it is never a bad idea to make a backup of USER_DIR/addons/plugin.program.advanced.emulator.launcher from time to time.