• 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7
  •   
Beta Advanced MAME Launcher - MAME frontend for Kodi
#1
Brick 
Image

Welcome to Advanced MAME Launcher

Advanced MAME Launcher is a MAME front-end for Kodi. It supports both MAME arcade ROMs plus Software Lists (about 100.000 ROMs in total).

Features
  • Browse and launch MAME arcade Machines.
  • Browse and launch MAME Software List ROMs.
  • Very easy to setup. Automatically extracts all metadata from MAME XML database and scans your MAME ROMs and Software Lists.
  • Optimized for blistering speed and efficiency.
  • Includes lots of filters to browse your MAME machines easily and conveniently.
  • Supports Catver.ini, Catlist.ini, Genre.ini, NPlayers.ini, Bestgames.ini and Series.ini.
  • Support MAMEInfo.dat, History.dat, Command.dat and Gameinit.dat. Information provided by these DAT files can be accesed from the context menu.
  • Expanded artwork & asset support including Titles, Snaps, Cabinets, Control Panels, PCBs, Flyers, Marquees, Clearlogos and Trailers. AML views are compatible with Advanced Emulator Launcher views.
  • Organise and unify all your treasured MAME Machines or Software List ROMs with the special in-built Favourites category.
  • ROM and CHD audit for MAME machines and Software List items. The ROM auditor supports Merged, Split and Non-merged sets.
  • Automatic Fanart generation from other pieces of artwork.
  • Automatic generation of MAME machines and SL item plots with useful information.
  • Custom MAME machine filters. The filters are configured by editing an XML file and enable having your custom game lists with no ROM/artwork duplicates.
  • Integrated addon configuration checker.
  • Extensive number of statistical information, ROM scanner and ROM auditor reports. These reports can be read with the context menu or as an external TXT files.
  • Export any MAME filter, including the MAME Favourites or any MAME custom filter, into an Advanced Emulator Launcher virtual launcher. This enables conveniently browsing your fine-tuned MAME machines from AEL without ROM or asset duplicates in your setup.
  • Integrated PDF Manual reader. PDF Manuals must be composed of scanned images (99% of the game manuals fall into this category).
  • (*) Integrated CBR/CBZ Manual reader.
  • Display the most played ROMs for MAME and Software List items.
  • Display the last played ROMs for MAME and Software List items.

(*) Planned features, not implemented yet.

Advanced MAME Launcher or Advanced Emulator Launcher?

Why two different addons capable of launching MAME? Should I use Advanced MAME Launcher or Advanced Emulator Launcher?
  • AML is much easier to configure than AEL. AEL is a general launcher whereas AML is tailored specifically for MAME.
  • AEL only shows the MAME ROMs you have. As opposed, AML shows every single MAME machine, even the ones you don't have the ROMs for.
  • AML includes a set of powerful Machine/ROM filters that makes navigation of MAME and Software Lists easy and convenient.

The answer is that you can use both! AML and AEL have been designed to work in tandem to enrich the retrogaming experience for Kodi users.

Installation & Downloads

AML is now available on the Kodi Official Addon Repository. To install it, go to Settings and then to Addon settings, Install from repository. AML is under the category Program add-ons and Game add-ons, Game providers.

NOTE If you are upgrading to AML 0.9.9 from a previous version make sure you read the Release Notes first! The Release Notes links are in the third post of this thread.

Development builds are also available from GitHub by clicking HERE. You can have both the stable version and the development version installed on the same machine. They behave like different addons and do not inferfere with each other.

Getting Started

Setting up MAME ROMs, CHDs and assets

If you need help setting up MAME in Linux or Windows you have a some good tutorials here, here and here. You can also ask questions about how to setup MAME in this thread but please try to read the tutorials first in order not to ask the same basic questions again and again.

Supported MAME ROM sets: AML currently supports Merged, Split, and Fully Non-Merged.

This is the recommended MAME directory layout. You have to create all the directories yourself, AML does not create any directory automatically.
Code:
/home/kodi/AML-ROMs/                --> Place MAME arcade ROMs and BIOSes here
/home/kodi/AML-assets/              --> Place MAME and Software Lists assets here
/home/kodi/AML-CHDs/                --> Place the CHDs here
/home/kodi/AML-SL-ROMs/             --> Place the Software Lists ROMs here
/home/kodi/AML-SL-CHDs/             --> Place the Software Lists CHDs here
/home/kodi/AML-assets/samples/      --> MAME samples (optional)
/home/kodi/AML-assets/catver.ini    --> Catver (optional)
/home/kodi/AML-assets/catlist.ini   --> Catlist (optional)
/home/kodi/AML-assets/genre.ini     --> Genre (optional)
/home/kodi/AML-assets/nplayers.ini  --> Number of players (optional)
/home/kodi/AML-assets/bestgames.ini --> Best games catalog (optional)
/home/kodi/AML-assets/series.ini    --> Series catalog (optional)
/home/kodi/AML-assets/history.dat   --> History DAT (optional)
/home/kodi/AML-assets/mameinfo.dat  --> MAME Info DAT (optional)
/home/kodi/AML-assets/gameinit.dat  --> Gameinit DAT (optional)
/home/kodi/AML-assets/command.dat   --> Command DAT (optional)

Catver.ini, Catlist.ini, Genre.ini, NPlayers.ini, Bestgames.ini and Series.ini are optional but recommended.
  • If you configure Catver.ini then filter Machines by Category (Catver) becomes available. You can download catver.ini from progretto-SNAPS.
  • If you configure Catlist.ini then filter Machines by Category (Catlist) becomes available. You can download catver.ini from progretto-SNAPS.
  • If you configure Genre.ini then filter Machines by Category (Genre) becomes available. You can download catver.ini from progretto-SNAPS.
  • If you configure Nplayers.ini then filter Machines by Number of players becomes available. You can download this file from Arcade Belgium.
  • If you configure Bestgames.ini then filter Machines by Score becomes available. You can download this file from progretto-SNAPS.
  • If you configure Series.ini then filter Machines by Series becomes available. You can download this file from progretto-SNAPS.

AML 0.9.4 supports History.dat, MAMEInfo.dat, Gameinit.dat and Command.dat. All these files are optional.

Software Lists hash path is a subdirectory inside the MAME installation directory which contains the Software Lists XML databases.
  • Linux users in Debian/Ubuntu it is typically located in /usr/share/games/mame/hash/.
  • Windows users if you installed MAME in E:\MAME then the Software Lists hash path would be located in E:\MAME\hash\.

The Software Lists ROMs/CHDs must be in a subdirectory whose name must match each Software List name, like in the following example:
Code:
/home/kodi/AML-SL-ROMs/32x/game_1.zip      --> ROMs for 32x Software List
/home/kodi/AML-SL-ROMs/32x/game_2.zip      
...
/home/kodi/AML-SL-ROMs/megadriv/game_1.zip --> ROMs for megadriv Software List
/home/kodi/AML-SL-ROMs/megadriv/game_2.zip
...

Remember to update your mame.ini configuration file to point to the correct directories where you have placed your ROMs/CHDs. Otherwise MAME won't work at all.

Setting up MAME assets and Software List assets

Place MAME assets/artwork in the following directories:

Code:
/home/kodi/AML-assets/artpreviews/   --> MAME artpreview PNG files
/home/kodi/AML-assets/artwork/       --> MAME artwork ZIP files
/home/kodi/AML-assets/cabinets/      --> MAME cabinets
/home/kodi/AML-assets/clearlogos/    --> MAME clearlogos/wheels
/home/kodi/AML-assets/covers_SL/     --> Software Lists covers/boxfronts
/home/kodi/AML-assets/cpanels/       --> MAME control panels
/home/kodi/AML-assets/fanarts/       --> AML will create MAME Fanarts here
/home/kodi/AML-assets/fanarts_SL/    --> AML will create SL Fanarts here
/home/kodi/AML-assets/flyers/        --> MAME flyers
/home/kodi/AML-assets/manuals/       --> MAME machine PDF/CBZ/CBR manuals
/home/kodi/AML-assets/manuals_SL/    --> SL items PDF/CBZ/CBR manuals
/home/kodi/AML-assets/marquees/      --> MAME marquees
/home/kodi/AML-assets/PCBs/          --> MAME PCBs
/home/kodi/AML-assets/samples/       --> MAME Sample ZIP files
/home/kodi/AML-assets/snaps/         --> MAME in-game screenshots
/home/kodi/AML-assets/snaps_SL/      --> Software Lists in-game screenshots
/home/kodi/AML-assets/titles/        --> MAME title screenshots
/home/kodi/AML-assets/titles_SL/     --> Software Lists in-game screenshots
/home/kodi/AML-assets/videosnaps/    --> MAME trailers (MP4 format)
/home/kodi/AML-assets/videosnaps_SL/ --> Software Lists trailers (MP4 format)

When configuring AML, MAME assets path in this example would be /home/kodi/AML-assets/.

MAME machines have a broad range of assets, including Cabinets, Clearlogos, Control Panels, Flyers, PCBs, in-game snaps and title screenshots. Software Lists, however, only have Covers/Boxfronts, in-game snaps and title screenshots. The covers, snaps and titles of each software list must be in their own subdirectory like in this example:

Code:
/home/kodi/AML-assets/covers_SL/32x/       --> Covers for 32x Software List
/home/kodi/AML-assets/covers_SL/megadriv/  --> Covers for megadriv Software List
...
/home/kodi/AML-assets/snaps_SL/32x/        --> Snaps for 32x Software List
/home/kodi/AML-assets/snaps_SL/megadriv/   --> Snaps for megadriv Software List
...

Note that the Software List artwork collections ZIP or Torrent files follow this naming scheme so you only have to decompress or copy the ZIP file/torrent in the appropiate directory.

AML doesn't have (and never will have) asset/artwork scrapers. You can however download full MAME artwork collections from here:
  • Progretto SNAPs MAME Artwork The definitive place in the universe for MAME (and Software Lists) assets.
  • Internet Archive: The Internet Archive is full of treasures! Make sure you do a comprehensive search!
  • Pleasuredome Look for the MAME EXTRAs torrent. It includes a complete and up-to-date MAME artwork collection based on the contents of Progretto SNAPs (*).
  • EmuMovies Has some good artwork collections for MAME (*).
  • HyperSpin Media Forum for HyperSpin users containing artpacks. Clearlogos are called 'Wheels' in HyperSpin parlance (*).
(*) Registration Required

Setting up Advanced MAME Launcher (Easy mode)

1) Install and run AML for the first time.

2) Open AML settings, in the tab Paths configure the MAME executable and the ROMs path.

3) (Optional) Configure the MAME assets path, MAME CHDs path, Software Lists hash path, Software Lists ROMs path, Software Lists CHDs path, Samples path, Catver.ini path, Catlist.ini path, Genre.ini path, nplayers.ini, bestgames.ini, series.ini.

4) In AML root window select any item, open the context menu, select "Setup plugin". Execute, in consecutive order:

4.1) Extract MAME.xml ... extracts the MAME.xml database from MAME.

4.2) Build all databases converts the MAME XML database into JSON format, strips out unneeded information to boost performance, generates the filter parent/clone lists and processes the Software List XML databases.

4.3) Scan everyting scans your MAME machine ROMs, CHDs and Samples, Software Lists ROMs and CHDs, and MAME machines and Software Lists assets/artwork. Sets all tags having a ? to the appropriate value.

If everything is OK you are now able to navigate all MAME ROMs (arcade/computer machines and Software Lists).

Setting up Advanced MAME Launcher (Advanced mode)

The Setup plugin, Step by step ... menu allows you to execute the AML database setup process step by step, as opposed to automatically. For example, if you install/copy new MAME assets you can execute "Scan MAME assets/artwork ..." to bring the MAME machine artwork database up-to-date. Alternatively, you can run Scan everyting to bring all ROMs/assets databases up-to-date but it will take much longer.
Reply
#2
Advanced MAME Launcher User's Guide

AML root window

AML's root window looks like this:

Image

The number of MAME Machines (about 30.000) is astonishingly big and it would be not practical nor convenient to browse all of them on the same list. Hence, AML includes a set of filters that will show only the Machines that meet the filtering condition. There are 4 kinds of such filters:

1) Main filters Machines (with coin slot), Machines (no coin slot), Machines (mechanical) and Machines (dead).

Machines (with coin slot) roughly correspond with the arcade machines and Machines (no coin slot) roughly correspond with console/computer/calculator Machines (the ones formerly in MESS). Dead machines are those with preliminary driver status (do not work) and have no controls (you cannot interact with them in any way). The Main filters are mutually exclusive. For example, Machines (with coin slot) actually means Machines with coin slot and not mechanical and not dead.

2) Binary filters Machines [with CHDs], Machines [with Samples], Machines [BIOS].

The binary filters define ON/OFF conditions. For example, a given Machine may have CHDs or not, may be a BIOS or not, etc.

3) Catalog filters Machines by Category, Machines by Manufacturer, etc.

When you enter these filters you are shown a catalog defined by the filter. For example, if you enter the Machines by Manufacturer filter you are presented with a list of all manufacturers, if you enter one manufacturer then the whole list of Parent machines by that manufacturer is shown.

4) Software Lists

Allows you to navigate the ROMs defined on each Software List database.

AML Parent Machines list

When you enter any of the filters a list of Parent Machines is displayed:

Image

Every item in the list contains the name of the Machine and a set of flags at the end.

Machine name example with flags
Code:
Dino (rev B) Rc-- [Dev][BIOS][Clo][status]
| | | | |------- Driver status flag
| | | |------------- Parent/Clone flag
| | |-------------------- BIOS flag
| |------------------------- Device flag
|------------------------------- Machine status flag

Machine status flag

The Machine status flags reports whether a Machine has ROMs, CHDs, Samples and Software Lists. After the main MAME database has been created you will see either - or ?, meaning that the machine does not have Roms, Chds, Samples or software Lists or the machine have them, respectively. The ROM scanner will check the existence of the ROMs/CHDs/Samples and change the ? flag into the appropriate lower case letter or upper case letter.

Code:
RCSLD
|||||- Device flag
||||-- Software Lists flag
|||--- Samples flag
||---- CHDs flag
|----- ROMs flag

- Does not have ROMs/CHDs/Samples/SLs
? Machine has ROMs/CHDs/Samples but ROMs have not been checked
r Missing ROMs/CHDs/Samples/SLs (you cannot run the machine)
R You have the ROMs/CHDs/Samples/SLs (you can run the machine)

Driver status flag

The Driver status flag reports about the quality of the emulation of the Machine. It may have any of these 3 values.
Code:
empty Driver status is Good
[Imp] Driver is Imperfect. It works but emulation may have some glitches
[Pre] Driver is Preliminary and emulation not working.

AML Machine Parent/Clone list

When you enter any parent Machine a new window containing both the Parent and Clone Machines is shown. If you click on any Machine in the Parent/Clone list MAME will be launched to play that Machine. Note that you will need to have the corresponding ROMs/CHDs to execute the Machine.
Reply
#3
TODO - Known issues

  1. Android is not supported yet.
  2. Kodi Retroplayer and the MAME cores are not supported yet.

Bugs & Feature Requests

You can ask for feature requests in this thread or directly on GitHub.

If you find a bug or Kodi shows an error in AEL you can report it in this thread or in GitHub. Try to be descriptive about the problem and the steps you do that cause it. Unless otherwise told, follow these steps:
  • In Kodi Settings, turn Kodi debug log OFF.
  • In AEL Settings, go to Advanced and set the log level to DEBUG.
  • Reproduce the bug.
  • Put your Kodi log file in Ubuntu pastebin or PasteBin.

You can use the Kodi Logfile Uploader addon to help with the log upload process. Thanks to Ronie for this fine addon.

Release history (and release notes)
  1. Advanced MAME Launcher 0.9.10 (released 10 May 2019)
  2. Advanced MAME Launcher 0.9.9 (released 22 March 2019)
  3. Advanced MAME Launcher 0.9.8 (released 23 June 2018)
  4. Advanced MAME Launcher 0.9.7 (released 09 June 2018)
  5. Advanced MAME Launcher 0.9.6 (released 25 May 2018)
  6. Advanced MAME Launcher 0.9.5 (released 11 May 2018)
  7. Advanced MAME Launcher 0.9.4 (released 29 March 2018)
  8. Advanced MAME Launcher 0.9.3 (released 30 May 2017)
  9. Advanced MAME Launcher 0.9.2 (released 12 February 2017)
  10. Advanced MAME Launcher 0.9.1 (released 04 February 2017)
  11. Advanced MAME Launcher 0.9.0 (released 15 January 2017)
Reply
#4
Screenshot gallery

All these screenshots have been taken with the skin Estuary AEL MOD.

AML root window

Image

MAME machines in Parent/Clone mode

Image

Software List items in Parent/Clone mode

Image

MAME autogenerated Fanart

Image

Software List autogenerated Fanart

Image

Display MAME machine ROMs in the Audit database

Image

MAME Custom Filters

Image
Reply
#5
Hi Wintermute0110, I don't know what MAME are you using, but I downloaded the mame0181b (I'm surprised that it has UI, because I read the first tutorial and its supposed to be with commands line) and doesn't have mame.ini, but it has a ui.ini and on that only has paths for artwork. I can find a dir.txt that has this "Place ROM directories here". I believe I need to put something like this /home/kodi/AML-ROMs/ on that file.

Do I nedd to create a folder named samples because it's on the add-on settings?
Reply
#6
@KODser I did the final test during development using 0.180 in Linux. Yeah, newer versions of MAME integrate a simple UI on MAME itself. The UI will launch if you execute MAME without any command line parameter. This UI is a big step forward to not having an UI at all. However, MAME's UI is not as good as most external frontends.

If you are using Windows:

1) Install MAME from MAMEDEV and place it on an easy, short directory, for example e:\mame

2) Click on Start menu, then type cmd to open a terminal.

3) In the terminal go to the directory you installed mame and execute mame -createconfig

Code:
c:\windows> e:
e:\ > cd mame
e:\mame > mame -createconfig
e:\ > exit

4) Your mame.ini will be located in e:\mame\mame.ini. I recommend Notepad++ to edit mame.ini

If you are using Linux:

1) Open a terminal.

2) At the prompt type

Code:
$ mame -createconfig

3) mame.ini will be located on ~/.mame/mame.ini. ~ means the user directory: for example, if your username is kodi then ~ = /home/kodi/

Report if you need more help, find a problem or have a feature request.
Reply
#7
Yes, I downloaded it from the mamedev. In my case its mame64 -createconfig. this ini has a lot more options

Do I need to create a folder named samples because it's on the add-on settings?

Thanks
Reply
#8
Inside the MAME installation directory there is a directory to place your samples (the default). You can place you samples there and then tell AML the directory.

Samples are optional. They are used by some games (typically very old ones) with poor sound emulation.

Remember that the two important things in AML settings are the mame executable and the ROM path. The rest is optional. Also, edit mame.ini if you change the default ROM path. I believe in windows the default ROM path is (following with the previous example) is e:\mame\roms\ but I do not have Windows, I'm talking by memory.
Reply
#9
Yes, the default MAME ROM path is mame/roms.
When I was scanning for ROMs without the samples folder, Kodi gave me, not only a prompt saying that I haven't config a samples folder (that is fine), but gave me an actual error. With the Samples folder path everything worked fine

I guess I will need a new hard drive just for Progretto SNAPs artwork. I will try Hyperspin to serch artwork for some Games. It's a shame that Progretto doesn't allow to search artwork for a specific game
Reply
#10
(2017-01-20, 18:19)KODser Wrote: Yes, the default MAME ROM path is mame/roms.
When I was scanning for ROMs without the samples folder, Kodi gave me, not only a prompt saying that I haven't config a samples folder (that is fine), but gave me an actual error. With the Samples folder path everything worked fine

I guess I will need a new hard drive just for Progretto SNAPs artwork. I will try Hyperspin to serch artwork for some Games. It's a shame that Progretto doesn't allow to search artwork for a specific game
Maybe you found a bug. If so, try to reproduce it and post a debug log!

You can search for individual machine artwork in Arcade Database, which is the site AEL uses for MAME scraping. That will allow you to some tests with artwork. Search using the MAME short name of the machine in Arcade Database.

And yeah... MAME ROMS plus artwork is about 100 GB. Software Lists another 50 GB. If you add MAME CHDs add another 500 GB. Software List CHDs are 1300 GB.
Reply
#11
Why don't you add that scraper to AML and only allow to scrape by machine/game, for obvious reason?
Reply
#12
(2017-01-20, 18:56)KODser Wrote: Why don't you add that scraper to AML and only allow to scrape by machine/game, for obvious reason?

Actually, I had a second though about this. Including Arcade Database scraper in AML is not necessary. You can make AML/AEL to work in tandem so AEL will scrap the artwork for your MAME ROMs!

I will use Unix/Linux paths, if you are using windows then change /home/kodi/ by e:\, for example.

1) Create a temporary directory /home/kodi/mame-assets/

2) Create a MAME launcher in AEL. As the ROM path you choose the directory you have your MAME ROMs. As the asset path you choose /home/kodi/mame-assets/

3) AEL automatically will create the following dirs,

Code:
/home/kodi/mame-assets/banners/
/home/kodi/mame-assets/boxback/
/home/kodi/mame-assets/boxfront/
/home/kodi/mame-assets/cartridges/
/home/kodi/mame-assets/clearlogos/
/home/kodi/mame-assets/fanarts/
/home/kodi/mame-assets/flyers/
/home/kodi/mame-assets/manuals/
/home/kodi/mame-assets/maps/
/home/kodi/mame-assets/snaps/
/home/kodi/mame-assets/titles/
/home/kodi/mame-assets/trailers/

4) Create the following directories yourself,

Code:
/home/kodi/mame-assets/cabinets/
/home/kodi/mame-assets/cpanels/
/home/kodi/mame-assets/marquees/
/home/kodi/mame-assets/PCBs/

5) In AEL select the MAME launcher, context menu > Edit Launcher > Manage ROM list > Manage ROMs assets directories... Then change the following paths

Code:
Change Boxfront  path to /home/kodi/mame-assets/cabinets/
Change Boxback   path to /home/kodi/mame-assets/cpanels/
Change Cartridge path to /home/kodi/mame-assets/PCBs/
Change Banners   path to /home/kodi/mame-assets/marquees/

6) In AML configure your ROM path and MAME executable. As asset directory select /home/kodi/mame-assets/

7) Now, you can use AEL ROM scanner to scrap your MAME assets (remember to use the Arcade Database scraper).

Those scraped assets can be shared between AML/AEL. Whenever you make changes in the assets using AEL then refresh the assets in AML. Go to AML root menu, open the context menu > Setup > scan assets/artwork...
Reply
#13
Before I saw this message, I downloaded the artwork "by hand" and used the scan on AML, the problem is that it doesn't show anything.

my path config - http://i.imgur.com/MWz368E.png

I have a pretend zip called - Street Fighter II The World Warrior (World 910522).zip on the ROMs path
I downloaded the artwork and changed the name of the different assets to Street Fighter II The World Warrior (World 910522).png and scanned the artwork. it doesn't show artwork on that machine (capcom/Street Fighter II The World Warrior (World 910522))
Don't know what I'm doing wrong

Other question, for skinning, the assets have the same name? if I do listItem.banner on the mame launcher it shows the marquee or I have to change to listItem.marquee?
Reply
#14
(2017-01-21, 19:37)KODser Wrote: Before I saw this message, I downloaded the artwork "by hand" and used the scan on AML, the problem is that it doesn't show anything.

my path config - http://i.imgur.com/MWz368E.png

I have a pretend zip called - Street Fighter II The World Warrior (World 910522).zip on the ROMs path
I downloaded the artwork and changed the name of the different assets to Street Fighter II The World Warrior (World 910522).png and scanned the artwork. it doesn't show artwork on that machine (capcom/Street Fighter II The World Warrior (World 910522))
Don't know what I'm doing wrong

Go to the machine, context menu > View machine data. You will see the database entry for that machine. At the end you will see if AML picked you artwork or not. Also, remember that MAME ROMs must have special names (the MAME short names). Otherwise MAME won't work. For example, Street Fighter II ROM must have a name like sfii.zip, and assets must be names sfii.png.

Currently the implementation of AML is very naive, I think only png images work. I will add a more complete one supporting many artwork types ASAP.

Also, AML 0.9.0 has one bug: MAME will always launch in windowed mode! I will solve this ASAP.

(2017-01-21, 19:37)KODser Wrote: Other question, for skinning, the assets have the same name? if I do listItem.banner on the mame launcher it shows the marquee or I have to change to listItem.marquee?

AML infolabels are currently totally compatible with AEL infolabels, like in this example:

Image

Here you can see all the artwork infolabels set by AML at the moment.
Reply
#15
I tried to do what you said.
1) changed banners, boxfront and boxback and cartriges path to marquees, cabinets, cpanels and PCBs
2) changed the name to sf2.zip
3) Scan for new roms. when he scrapes this way it doesn't find any artwork so I enter the MAME launcher and edited the fs2 rom metadata with Arcade database. It searches and knows that is for Street Fighter, but after that it gives an error

Code:
18:11:32.183 T:12844  NOTICE: special://profile/ is mapped to: special://masterprofile/
18:11:32.183 T:12844  NOTICE: -----------------------------------------------------------------------
18:11:32.183 T:12844  NOTICE: Starting Kodi (17.0-RC3 Git:20170111-4d93228-dirty). Platform: Windows NT x86 32-bit
18:11:32.183 T:12844  NOTICE: Using Release Kodi x32 build
18:11:32.183 T:12844  NOTICE: Kodi compiled Jan 12 2017 by MSVC 190024210 for Windows NT x86 32-bit version 6.3 (0x06030000)
18:11:32.183 T:12844  NOTICE: Running on ASUSTeK Computer Inc. N61Vn with Windows 10, kernel: Windows NT x86 64-bit version 10.0
18:11:32.194 T:12844  NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
18:11:32.194 T:12844  NOTICE: Host CPU: Unknown, 2 cores available
18:11:32.194 T:12844  NOTICE: Desktop Resolution: 1366x768 32Bit at 60Hz
18:11:32.194 T:12844  NOTICE: Running with administrator rights
18:11:32.196 T:12844  NOTICE: Aero is enabled
18:11:32.197 T:12844  NOTICE: special://xbmc/ is mapped to: C:\Program Files (x86)\Kodi
18:11:32.197 T:12844  NOTICE: special://xbmcbin/ is mapped to: C:\Program Files (x86)\Kodi
18:11:32.197 T:12844  NOTICE: special://xbmcbinaddons/ is mapped to: C:\Program Files (x86)\Kodi/addons
18:11:32.197 T:12844  NOTICE: special://masterprofile/ is mapped to: C:\Users\Diogo\AppData\Roaming\Kodi\userdata
18:11:32.197 T:12844  NOTICE: special://home/ is mapped to: C:\Users\Diogo\AppData\Roaming\Kodi\
18:11:32.197 T:12844  NOTICE: special://temp/ is mapped to: C:\Users\Diogo\AppData\Roaming\Kodi\cache
18:11:32.197 T:12844  NOTICE: special://logpath/ is mapped to: C:\Users\Diogo\AppData\Roaming\Kodi\
18:11:32.197 T:12844  NOTICE: The executable running is: C:\Program Files (x86)\Kodi\kodi.exe
18:11:32.247 T:12844  NOTICE: Local hostname: diogo-asus
18:11:32.247 T:12844  NOTICE: Log File is located: C:\Users\Diogo\AppData\Roaming\Kodi\/kodi.log
18:11:32.247 T:12844  NOTICE: -----------------------------------------------------------------------
18:11:32.482 T:12844  NOTICE: load settings...
18:11:32.496 T:12844 WARNING: CSettingString: unknown options filler "timezonecountries" of "locale.timezonecountry"
18:11:32.497 T:12844 WARNING: CSettingString: unknown options filler "timezones" of "locale.timezone"
18:11:32.507 T:12844  NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
18:11:32.507 T:12844  NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
18:11:32.507 T:12844  NOTICE: Default Video Player: VideoPlayer
18:11:32.507 T:12844  NOTICE: Default Audio Player: paplayer
18:11:32.507 T:12844  NOTICE: Disabled debug logging due to GUI setting. Level 0.
18:11:32.507 T:12844  NOTICE: Log level changed to "LOG_LEVEL_NORMAL"
18:11:32.515 T:12844  NOTICE: CMediaSourceSettings: loading media sources from special://masterprofile/sources.xml
18:11:32.522 T:12844  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
18:11:32.534 T:12844  NOTICE: Loaded playercorefactory configuration
18:11:32.535 T:12844  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
18:11:32.535 T:12844  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
18:11:32.584 T:12844  NOTICE: Running database version Addons26
18:11:35.953 T:12844  NOTICE: ADDONS: Using repository repository.xbmc.org
18:11:35.953 T:12844  NOTICE: ADDONS: Using repository repository.exodus
18:11:35.953 T:12844  NOTICE: ADDONS: Using repository repository.northebridge.by.design.kodi
18:11:35.953 T:12844  NOTICE: ADDONS: Using repository superrepo.kodi.krypton.all
18:11:36.022 T:9676  NOTICE: Found 2 Lists of Devices
18:11:36.022 T:9676  NOTICE: Enumerated DIRECTSOUND devices:
18:11:36.022 T:9676  NOTICE:     Device 1
18:11:36.022 T:9676  NOTICE:         m_deviceName      : {2E9BDD33-3B3C-4FD2-8F00-5594C6EF36CE}
18:11:36.022 T:9676  NOTICE:         m_displayName     : SPDIF - Realtek Digital Output (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_displayNameExtra: DIRECTSOUND: Realtek Digital Output (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_IEC958
18:11:36.022 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.022 T:9676  NOTICE:         m_sampleRates     : 48000
18:11:36.022 T:9676  NOTICE:         m_dataFormats     : AE_FMT_FLOAT,AE_FMT_RAW
18:11:36.022 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512
18:11:36.022 T:9676  NOTICE:     Device 2
18:11:36.022 T:9676  NOTICE:         m_deviceName      : {F242F203-04B8-4FAF-8CBF-B1CACE8C911C}
18:11:36.022 T:9676  NOTICE:         m_displayName     : Speakers - Speakers (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_displayNameExtra: DIRECTSOUND: Speakers (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
18:11:36.022 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.022 T:9676  NOTICE:         m_sampleRates     : 48000
18:11:36.022 T:9676  NOTICE:         m_dataFormats     : AE_FMT_FLOAT
18:11:36.022 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512
18:11:36.022 T:9676  NOTICE:     Device 3
18:11:36.022 T:9676  NOTICE:         m_deviceName      : default
18:11:36.022 T:9676  NOTICE:         m_displayName     : default
18:11:36.022 T:9676  NOTICE:         m_displayNameExtra:
18:11:36.022 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
18:11:36.022 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.022 T:9676  NOTICE:         m_sampleRates     : 48000
18:11:36.022 T:9676  NOTICE:         m_dataFormats     : AE_FMT_FLOAT
18:11:36.022 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512
18:11:36.022 T:9676  NOTICE: Enumerated WASAPI devices:
18:11:36.022 T:9676  NOTICE:     Device 1
18:11:36.022 T:9676  NOTICE:         m_deviceName      : {2E9BDD33-3B3C-4FD2-8F00-5594C6EF36CE}
18:11:36.022 T:9676  NOTICE:         m_displayName     : SPDIF - Realtek Digital Output (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_displayNameExtra: WASAPI: Realtek Digital Output (Realtek High Definition Audio)
18:11:36.022 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_IEC958
18:11:36.022 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.022 T:9676  NOTICE:         m_sampleRates     : 192000,96000,48000,44100
18:11:36.022 T:9676  NOTICE:         m_dataFormats     : AE_FMT_S24NE4MSB,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_RAW
18:11:36.022 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_512,STREAM_TYPE_AC3
18:11:36.022 T:9676  NOTICE:     Device 2
18:11:36.022 T:9676  NOTICE:         m_deviceName      : {F242F203-04B8-4FAF-8CBF-B1CACE8C911C}
18:11:36.022 T:9676  NOTICE:         m_displayName     : Speakers - Speakers (Realtek High Definition Audio)
18:11:36.023 T:9676  NOTICE:         m_displayNameExtra: WASAPI: Speakers (Realtek High Definition Audio)
18:11:36.023 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
18:11:36.023 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.023 T:9676  NOTICE:         m_sampleRates     : 192000,96000,48000,44100
18:11:36.023 T:9676  NOTICE:         m_dataFormats     : AE_FMT_S24NE4MSB,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_RAW
18:11:36.023 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_512,STREAM_TYPE_AC3
18:11:36.023 T:9676  NOTICE:     Device 3
18:11:36.023 T:9676  NOTICE:         m_deviceName      : default
18:11:36.023 T:9676  NOTICE:         m_displayName     : default
18:11:36.023 T:9676  NOTICE:         m_displayNameExtra:
18:11:36.023 T:9676  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
18:11:36.023 T:9676  NOTICE:         m_channels        : FL,FR
18:11:36.023 T:9676  NOTICE:         m_sampleRates     : 192000,96000,48000,44100
18:11:36.023 T:9676  NOTICE:         m_dataFormats     : AE_FMT_S24NE4MSB,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_RAW
18:11:36.023 T:9676  NOTICE:         m_streamTypes     : STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_512,STREAM_TYPE_AC3
18:11:36.182 T:12844  NOTICE: Found screen: Generic PnP Monitor on NVIDIA GeForce GT 240M    , adapter 0.
18:11:36.183 T:12844  NOTICE: Primary mode: [email protected] 60.00 - Full Screen
18:11:36.183 T:12844  NOTICE: Additional mode: [email protected] 60.00 - Full Screen
18:11:36.183 T:12844  NOTICE: Previous line repeats 2 times.
18:11:36.183 T:12844  NOTICE: Additional mode: [email protected] 60.00 - Full Screen
18:11:36.184 T:12844  NOTICE: Previous line repeats 2 times.
18:11:36.184 T:12844  NOTICE: Additional mode: [email protected] 60.00 - Full Screen
18:11:36.184 T:12844  NOTICE: Previous line repeats 2 times.
18:11:36.184 T:12844  NOTICE: Additional mode: [email protected] 60.00 - Full Screen
18:11:36.184 T:12844  NOTICE: Previous line repeats 2 times.
18:11:36.184 T:12844  NOTICE: Additional mode: [email protected] 60.00 - Full Screen
18:11:36.185 T:12844  NOTICE: Checking resolution 15
18:11:39.181 T:7792  NOTICE: Running database version Addons26
18:11:39.223 T:7792  NOTICE: Running database version ViewModes6
18:11:39.224 T:7792  NOTICE: Running database version Textures13
18:11:39.266 T:7792  NOTICE: Running database version MyMusic60
18:11:39.281 T:7792  NOTICE: Running database version MyVideos107
18:11:39.298 T:7792  NOTICE: Running database version TV29
18:11:39.300 T:7792  NOTICE: Running database version Epg11
18:11:40.641 T:12844 WARNING: JSONRPC: Could not parse type "Setting.Details.SettingList"
18:11:40.833 T:12844 WARNING: CApplication::Initialize - startup.xml taints init process
18:11:40.875 T:12844  NOTICE: initialize done
18:11:40.875 T:12844  NOTICE: Running the application...
18:11:40.875 T:12844  NOTICE: starting upnp client
18:11:40.881 T:8368  NOTICE: ES: Starting UDP Event server on port 9777
18:11:40.881 T:8368  NOTICE: UDP: Listening on port 9777 (ipv6 : false)
18:11:41.931 T:12376  NOTICE: script.tv.show.next.aired: ### TV Show - Next Aired starting background proc (6.0.15)
18:11:42.260 T:12376  NOTICE: script.tv.show.next.aired: ### no prior data found
18:11:44.354 T:12376  NOTICE: script.tv.show.next.aired: ### starting data update
18:11:46.270 T:11636  NOTICE: Skin Helper Service --> skin helper service version 1.0.100 started
18:11:46.484 T:5344  NOTICE: script.grab.fanart: Grab Fanart Service Started
18:11:46.639 T:12844   ERROR: Misplaced [
18:11:46.639 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem(-3).Title,"[OK]")
18:11:46.639 T:12844   ERROR: Misplaced [
18:11:46.639 T:12844   ERROR: Error parsing boolean expression !String.Contains(ListItem(-3).Title,"[OK]") +!String.Contains(ListItem(-3).Title,"Fav") + !String.Contains(ListItem(-3).Title,"Broken")
18:11:46.642 T:12844   ERROR: Misplaced [
18:11:46.642 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem(-2).Title,"[OK]")
18:11:46.645 T:12844   ERROR: Misplaced [
18:11:46.645 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem(-1).Title,"[OK]")
18:11:46.651 T:12844   ERROR: Misplaced [
18:11:46.651 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem(2).Title,"[OK]")
18:11:46.652 T:12844   ERROR: Misplaced [
18:11:46.652 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem(1).Title,"[OK]")
18:11:46.655 T:12844   ERROR: Misplaced [
18:11:46.655 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem.Title,"[OK]")
18:11:46.659 T:12844   ERROR: Unmatched ]
18:11:46.659 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem.Title,"Fav") | String.Contains(ListItem.Title,"Broken")]
18:11:46.659 T:12844   ERROR: Misplaced [
18:11:46.659 T:12844   ERROR: Error parsing boolean expression String.Contains(ListItem.Title,"[OK]")
18:11:46.869 T:8052  NOTICE: NEXTUP SERVICE NOTIFICATION Service -> Starting NextUp Service
18:11:46.933 T:8052  NOTICE: NEXTUP SERVICE NOTIFICATION Service -> ========  START NEXTUP SERVICE NOTIFICATION  ========
18:11:46.933 T:11636  NOTICE: Skin Helper Service --> WebService - start helper webservice on port 52307
18:11:46.934 T:8052  NOTICE: NEXTUP SERVICE NOTIFICATION Service -> KODI Version: 17.0-RC3 Git:20170111-4d93228-dirty
18:11:46.934 T:8052  NOTICE: NEXTUP SERVICE NOTIFICATION Service -> NEXTUP SERVICE NOTIFICATION Version: 1.0.32
18:11:47.061 T:10844   ERROR: Skin Helper Service --> ERROR in getDataFromCacheFile for file C:\Users\Diogo\AppData\Roaming\Kodi\userdata\addon_data\script.skin.helper.service\actorimages.json --> expected string without null bytes
18:11:47.061 T:10844   ERROR: Traceback (most recent call last):
18:11:47.061 T:10844   ERROR:   File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\script.skin.helper.service\resources\lib\Utils.py", line 875, in getDataFromCacheFile
18:11:47.184 T:10844   ERROR:     if text: data = eval(text)
18:11:47.184 T:10844   ERROR: TypeError: expected string without null bytes
18:11:47.712 T:6444   ERROR: XFILE::CDirectory::GetDirectory - Error getting plugin://plugin.video.exodus/?action=movies&url=popular&reload=
18:11:47.950 T:12160   ERROR: XFILE::CDirectory::GetDirectory - Error getting plugin://plugin.video.exodus/?action=tvshows&url=popular&reload=
18:12:12.733 T:7036   ERROR: AEL INFO : _gui_scrap_rom_metadata() ROM "sf2"
18:12:20.903 T:7036   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.IndexError'>
                                            Error Contents: list index out of range
                                            Traceback (most recent call last):
                                              File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\plugin.program.advanced.emulator.launcher\addon.py", line 42, in <module>
                                                plugin.run_plugin()
                                              File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\plugin.program.advanced.emulator.launcher\resources\main.py", line 245, in run_plugin
                                                self._command_edit_rom(args['catID'][0], args['launID'][0], args['romID'][0])
                                              File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\plugin.program.advanced.emulator.launcher\resources\main.py", line 1967, in _command_edit_rom
                                                if not self._gui_scrap_rom_metadata(categoryID, launcherID, romID, roms, scraper_obj): return
                                              File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\plugin.program.advanced.emulator.launcher\resources\main.py", line 6928, in _gui_scrap_rom_metadata
                                                gamedata = scraper_obj.get_metadata(results[selectgame])
                                              File "C:\Users\Diogo\AppData\Roaming\Kodi\addons\plugin.program.advanced.emulator.launcher\resources\scrap_metadata.py", line 381, in get_metadata
                                                if fa_year: gamedata['year'] = fa_year[1]
                                            IndexError: list index out of range
                                            -->End of Python script error report<--
Reply
  • 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7
  •   
 
Thread Rating:
  • 2 Vote(s) - 5 Average



Logout Mark Read Team Forum Stats Members Help
Advanced MAME Launcher - MAME frontend for Kodi52