Pacman56

@neil9000 I ran the setup with (beta updates to get last beta) against a new folder then copied my Data folder to that new setup location.

@neil9000 I wish I could try someone else large collection (hint hint @cammelspit) like Jason did on the live stream Monday and see how it runs on my cab. If someone wants to volunteer, I would first suggest to clear his/her emumovies info from the xml.

I totally agree with you neil9000. There isn't much disk activity when loading the xml files as observed using Task Manager.

2 days ago, I watched the recorded twitch broadcast which mainly focused on improving BB startup performance with large collections (50K games) which happens to be my collection size. I was so excited that evening! I wanted to put it to the test but for some reason, the performance results I'm experiencing are quite different from the ones I've seen on the stream. This morning I downloaded and installed the latest beta (7.0-beta-23), but my ~50K collection takes 1 min 20 sec to start. In trying to isolate the problem, I created a new (clean) LaunchBox installation folder and copied my production "Data" folder onto it. This of course means, no videos, images, manuals, etc. As a result, performance was slightly improved to a startup time of 58 sec but that still far from what I've seen on the twitch broadcast. A lot of times I hear that moving your LaunchBox folder an SSD improves performance but that was not the case for me as you can see in the Performance Results section below. I decided to start Task Manager and selected the performance tab to see which hardware resources are solicited when starting BB and could clearly see that the storage device on which LB/BB is installed is hardly moving from 0%. After running these tests several time, the xml data gets cached by the OS and the HDD activity stays down to nearly 0% during BB startups. However, the CPU is always at 28% 3.85 GHz during the entire time BB is starting. Once the wheel is displayed, the CPU goes down to ~6% 2.52 GHz. Additionally, when loading the platform view using the following sequence [from the platform view, hit esc, select Options, select Back then Back again], the new “Please Wait” message will appear and it will takes 25 seconds for the view to be displayed. Switching View also takes 25 sec. Any suggestions or recommendations would be greatly appreciated. Hardware: Processor: i5-4690K OC @4.6 using ASUS AI Suite RAM: 16GB GPU: GeForce GTX 950 250GB SSD (Operating System) 1TB HDD (Dedicated to BigBox and emulators) Software: Windows 8.1 (on SSD) LaunchBox 7.0-beta-23 (on 1TB WD Black) BigBox Settings: Theme: Default or CriticalZonev1.3 (performance issue is present either way) Collection Size: 49389 Performance Results (1TB HDD 7200RPM dedicated drive, with all images, videos, etc): Start BigBox: 1 min 20 sec Switch View: 25 sec View Platforms: 25 sec Performance Results (1TB HDD 7200RPM dedicated drive, images and videos removed): Start BigBox: 58 sec Switch View: 25 sec View Platforms: 25 sec Performance Results (250GB SSD OS drive, images and videos removed): Start BigBox: 61 sec Switch View: 25 sec View Platforms: 25 sec

I just performed some testing of the of the new “Download Platform Theme Videos…” feature in LB using LaunchBox v7.0-beta-23 and noticed that when you click on the “Select All” button then click OK, some of my existing Platform videos were deleted after the download completed. The Beyond Compare screenshot below will indicate (see red arrows) the video files that were deleted by comparing the videos between my local workstation and my Arcade cabinet. Note that both computers were synchronized prior to Downloading Platform Theme Videos from my local workstation (left side). It’s no big deal in my case since I can simply re-synchronize from right to left but it may be a problem for others.

@snoopybooh You are correct in that the current version only supports LaunchBox version 6.9 and before. Version 6.9 was the last version that made use of the "LaunchBox.xml" file. The developer of Lightspeed @Antropus is currently working on updating his tool to support the latest version of LaunchBox/BigBox. Although it's been a while, it is well worth the wait. I hope this helps.

@Jason Carr I just finished watching the last broadcast on twitch and I can't tell you enough how happy I was to see the performance gain with the startup of BigBox and large collection during the recorded stream. I also happen to have a 50K collection like cammelspit and look forward to test the next beta. I hope to join you live on Wednesday. One can say that today's stream was a very productive day and will no doubt make a lot of people happy.

Thank you @SentaiBrad

This morning I tested the “Import > ROM Files” with the latest beta (7.0-beta-8) to see if I should re-import my roms now that the multi-disk support has been implemented for a while. Unfortunately, errors appear when attempting to import my Apple II rom set. I believe this is due to the fact that old computers like the Apple has single sided floppy drives where you sometimes has to flip the floppy disk over to read the other side (side B). Consequently, the roms are named based on the following convention: “Disk 1 Side A”, “Disk 1 Side B”, etc. If you look at the highlighted sections of the screenshots below, you’ll notice that the Disc column is not always filled-in which I think causes the errors and as a result, a number of roms won’t get imported. Note: The file names I’m using are from the official HS xml. I’ve also looked at the naming convention used by TOSEC and they are also using “Side A”, “Side B” in their file names. Any thoughts?

Wow! You've made a lot of progress and it's looking really good. With all the added functionality,this will be awesome. Can't wait to try your next release. Thank you Kris. Chris

@Antropus I just read your last update and cannot believe all the work you've done in so little time. Like other LightSpeed users, I look forward to test the next version and can't wait to try the new features and import Software Lists as well. You cannot imagine the difference you are making to the community with your contribution. Your hard work is very very appreciated.

@Puppet The last version of LaunchBox that made use of LaunchBox.xml was version 6.9. My guess is that you probably started using LaunchBopx with version 6.10 or later which has the config xml files in a Data folder instead of having all config information in LaunchBox.xml. You should probably wait for the next release of Lightspeed which will support split xml files residing in the Data folder. There are ways around that (merging the various xml files into LauchBox.xml file) but it's probably simpler to wait for the next release of Lightspeed if your not sure how to merge those files.

@Antropus Adding the support for importing MAME Software List in LaunchBox/BigBox using LightSpeed is something I could only have dreamed of. I'm so looking forward for this new feature! You're tool is truly amazing! I think the platforms you've listed and the ones suggested by Cid is a pretty good start! Should I re-compress my SL roms as split sets or will merged set be working as well? I think I'll be converting them to split sets anyway (using clrmamepro batch mode) to have best performance when starting a game.

@Antropus I look forward for your next release of Lightspeed. I simply couldn't live without it. Your contribution is extremely appreciated by people like me who updates their complete set of roms, videosnaps and extras at the end of every month. Lightspeed is a must for collector junkies that want to see and play every possible versions (clones) of rom sets.

Ali. If you want to convert between formats you can use the WIT: Wiimms ISO Tools. I've done all of mine using the wit tools. It can also verify the disc integrity, remove update partitions. etc. Works for wii and game cubes discs. I had very good luck with these tools but they're command line and require you to do some reading from his web site. Not sure if I'm allowed to put links to his site here but you can easily google for it. Good luck!

Welcome Kirsten to the LaunchBox community. I recently migrated away from hyperspin and started using BigBox which is simply an amazing front end. Just love the features Jason recently added in version 6.3. This front end is a dream comes true for me. You are now part of a wonderful team with Jason and Brad.

DOS76. You are correct! The problem was also present with version 5.x.

Sorry guys, I just realized I need to use Bitbucket to report bugs.

First of all, I wish to say that I just love LaunchBox/BigBox and didn't think that I would ever migrate away from HS but this FE is so great that I did. Kudos to Jason and Brad! Now, I would like to report a small bug (with version 6.2) and hope this is the right place to do it. If now, please let me know. While managing my emulators (Tools > Manage Emulators > Double-click on my emulator > Click on Associated Platforms), I tend to use the clipboard copy and paste commands when editing the "Default Command-Line Parameters" cell for each new row I create in that grid. The problem is that when editing the "Default Command-Line Parameters" cell and storing its content into the clipboard, the content of the entire row (the 3 columns) is copied rather than the content of the cell being edited. Consequently, when pasting the value on a new row into the "Default Command-Line Parameters" cell, one has to remove the extra text that comes from the "Associated Platform" and "Default Emulator" cells. This is not a big deal but I just thought it should be reported. I can't wait for 6.3 and its new features to be released.