Jump to content
LaunchBox Community Forums

Lightspeed: Ultra-Fast Mame Importer Tool


Jason Carr

Recommended Posts

19 minutes ago, CriticalCid said:

Great to see you back with a new version. I really love it!

 

I just tested it and besides the issue that @JCSRT05 has reported I’ve also noticed that the release date parser doesn’t work for quite a few games. I can only speculate but I think it could be related to games which originally had those ‘export release’ notes because games like Captain Commando are affected by this.

 

Thanks Cid! Do you mean the date is not correct or not present at all? You mean the date in Launchbox, not at the Lightspeed listview, right? Or both?

  • Like 1
Link to comment
Share on other sites

24 minutes ago, Antropus said:

Thanks Cid! Do you mean the date is not correct or not present at all? You mean the date in Launchbox, not at the Lightspeed listview, right? Or both?

The year is correct but the day and month are set to January 1st. For example, that’s the case for Captain Commando while it clearly says in the notes November 1991.

It's also just in LaunchBox because Lightspeed only shows the year as far as I can see.

 

Btw. the file corruption is gone for me in Beta-2. Lightspeed now imports the games to my existing setup perfectly fine! :)

 

I’m wondering if it is too soon to ask for an additional feature?

You may or may not know that Jason has reworked the ‘Additional Apps’ feature in LB 7.7 to make it work better with clones. LB now automatically adds all clones as additional apps to the parent on import. You still have only one entry per game but you can also launch all clones within LaunchBox now. It would be great if Lightspeed could do the same.

You could use the LB importer to import your MAME ROMs to see how it works if you haven’t tinkered with it since 7.7 came out.

  • Like 2
Link to comment
Share on other sites

@flores9, can you post a screengrab showing the contents of your "SupportFiles" folder under the Lightspeed installation folder as well?

I also noticed something unusual in your setup, but I don't know if it might be related:
All your paths are set to "E:\EMULADORES\EMULADORES\" except your Roms and Softlists, which are pointing to "E:\EMULADORES\". They should be all at the same level, for example: ROMS, Flyers, Snap folders should be all inside of the mame root folder.

 

Edited by Antropus
Link to comment
Share on other sites

1 hour ago, Antropus said:

About the merged set, it's not ideal, but it *should* work. Exactly like what happens with the GUI present in the official mame, that does not recognize the children roms as present, because it doesn't deep scan the .zip files, Lightspeed doesn't either. So, although the games will be fully playable, if you try to force your list to contain only the present ROMS, a lot of them will be missing, so make sure that option is off!

Will pick the split set then, ugg, 20Gb more... at least is not the system one, that CHD can go to Tb!

Link to comment
Share on other sites

Your "Softlists.DB" file is corrupt for some reason. Just reinstall Lightspeed and you should be good. Not sure what happened in there.

Use this version instead, that has a bug fix mentioned above:

Version: 0183_Beta2
Date: 2/27/2017 10:55am

https://drive.google.com/file/d/0B23vaxsfSk1yQUQ1aXZpSThpbUk/view?usp=sharing

 

Edited by Antropus
Link to comment
Share on other sites

I have tried the 0183_beta2 now.

Instead of creating double information in the platform xml files not supported, Lightspeed now deletes the platform xml files.

I have tried to import the gameboy platform from software lists.

I also noticed that Lightspeed replaced my Emulators.xml with just one emulator for MESS, everything else is gone.

Keep up the good work. :)

Link to comment
Share on other sites

@audunv, do you mean it's deleting the xml files and not recreating them correctly? It should read them into memory, parse everything and re-create the files at the end of the process. Are they simply gone at the end of the process?
About the emulators.xml, that's definitely concerning.

@CriticalCid, did you run into the same problem reported above? Did your other platform xml files get deleted as well? Making sure that this is not a permission related issue.

 

Link to comment
Share on other sites

I know what's going on with emulators.xml. It's a little over-complicated the way I wrote the parser for it. I will simplify things tonight and get this fixed. I don't have anything imported by Launchbox in my library, so all my tests were done taking in account the stuff imported by Lightspeed only, which explain the problems related to other platforms not supported by Lightspeed, so your tests are definitely very appreciated and they will help to get things ironed out for everyone. Thanks!

  • Like 1
Link to comment
Share on other sites

1 minute ago, Antropus said:

I know what's going on with emulators.xml. It's a little over-complicated the way I wrote the parser for it. I will simplify things tonight and get this fixed. I don't have anything imported by Launchbox in my library, so all my tests were done taking in account the stuff imported by Lightspeed only, which explain the problems related to other platforms not supported by Lightspeed, so your tests are definitely very appreciated and they will help to get things ironed out for everyone. Thanks!

But should not be any problem importing first with lights peed and then any other no? Or files become botched? 

Link to comment
Share on other sites

7 minutes ago, Johnnydement said:

But should not be any problem importing first with lights peed and then any other no? Or files become botched? 

If you run LS first to get everything there and then import more things with Launchbox next, you should have no problems. But if later on you use LS again to add another platform, for example, it will most likely remove the emulators assigned by Launchbox and will try to assign Mame and Mess again. This should be a fairly simple fix, but the type that needs my attention, so I will look at it tonight since I am at work now :)

  • Like 1
Link to comment
Share on other sites

I found some more issues.

When I import software list roms, Lightspeed automatically adds command line like platform name, for the platform I'm trying to import. I want that field to be empty. 

If you add a command line when selection output, that value is added to gameboy. 
LS1.PNG.da18909ff90ecb6af7e9b8e3139badc5.PNGLS2.PNG.35877382f67bdfed129d210661e83f27.PNGLS3.PNG.108f79386bb9d5a50ac7b499bd6cdad1.PNGThis does not happen for the arcade roms.

 

If I change for example rating or commandline and export again, no changes are made to the platform.xml when choosing "merge to library".

If I choose overwrite library the platform xmls are updated, but platforms not in the export gets deleted.

 

Link to comment
Share on other sites

55 minutes ago, audunv said:

I found some more issues.

When I import software list roms, Lightspeed automatically adds command line like platform name, for the platform I'm trying to import. I want that field to be empty. 

If you add a command line when selection output, that value is added to gameboy. 
LS1.PNG.da18909ff90ecb6af7e9b8e3139badc5.PNGLS2.PNG.35877382f67bdfed129d210661e83f27.PNGLS3.PNG.108f79386bb9d5a50ac7b499bd6cdad1.PNGThis does not happen for the arcade roms.

 

If I change for example rating or commandline and export again, no changes are made to the platform.xml when choosing "merge to library".

If I choose overwrite library the platform xmls are updated, but platforms not in the export gets deleted.

 

About the command line, this is the way it was supposed to work. Software lists need the slist name informed in the command line or else the game will not run, unlike arcade games, where no additional command (other than the name of the rom itself) is necessary. Because of that, when you add any info to the command line, that info is added to the mandatory command line already in there so the game will run. I wrote it to be game based instead of platform based, because some games will need a different command line for pal or ntsc games and a broad command line based on the platform will simply not cut it.

About merging to library, if the game/platform is already in the library, nothing will be added and no info will be updated. If you are planning to change things later on, you will definitely need to use the overwrite option instead, which should affect all platform(s) being exported by Lightspeed. I know, it's not ideal yet, but that is what it does at this point. To change info in batch mode you will need to use Launchbox, but I am not sure if it supports changing command line in batch mode at this point.

About the platforms being deleted, this is related to the issue I will be looking at tonight, together with the emulators.xml issue.

All in all, Lightspeed was always intended to be the first pass when you are starting to populate a brand new library. All the requests to make it compatible with existent library/platforms is a thing that I am slowly migrating to, but Launchbox has a ton of files that I need to read/parse/collect info from and their layout is not always the easiest, like in the case of the emulators.xml file where you can find the very same "<emulator>" tag being used in two different places.

So it takes time to make it completely compatible with Launchbox. Other than that, if you are looking for the quickest way to migrate a huge library of mame games into a brand new Launchbox installation, with all the info and artwork parsed for you automatically, LS is a great tool.

-Kris

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...