c64 C64 Dreams (massive curated C64 collection)

[stigzler]

Final post, promise! Everything's working really well apart from the manuals and the magazines from the magazine set (zzap). Does anyone have these working?

[Zombeaver]

I'm not exactly sure what you're asking. If you mean in general, yes. If you mean with your importer I don't know as I haven't tested it. Manuals are toggled in-game via the keyboard/controller hotkeys. Magazines default to the web version but this can be changed if you replace with the included xml in the "Default Local" folder in the magazines subfolder.

I appreciate the contribution.

[stigzler]

Hey. Thanks for the reply. Yeah- my bad on the game manuals thing. I was thinking they weren't available because not available in the Launchbox context menu, but they are totally available in BigBox!

The magazines thing is a different matter. I've posted a vid below showing the problem. In it, I alternate between the stock c64-dreams-v0.60 folder bigbox installation and a local (testing) one - with full install of C64 Dreams, the latest hotfix and the magazine pack, so all mags have the additional .cbz files. What you'll see in the vid is the stock c64-dreams-v0.60 (and by extension the stock Data\Platforms\Magazines.xml) work perfectly, showing zzap. However, If I run my local version, I cannot see zzap  - only 4 mags. Weird thing is, if I copy the Magazines.xml directly from stock to my local version, then zzap still isn't seen. Not sure what it is - LB caching? Some LB/BB settings which are rendering zzap invisible? 

Even tried copying the local and web xmls into the Data/Platforms folder. Still no dice. However, I can access zzap from the game menu (both local and web) - although this is a file in the game folder?

Any ideas? (btw - the more I get into this, the more amazed I am at how much work went into this). 

Edited April 22 by stigzler

[Zombeaver]

1 hour ago, stigzler said:

I was thinking they weren't available because not available in the Launchbox context menu, but they are totally available in BigBox!

I'm not sure what you mean by them being in Big Box. The manuals aren't integrated into LB/BB in any way (unless BB is finding them and doing something with them in the background which I'm unaware of, its unintended if so). As I said, they're toggleable in-game via the hotkeys. Numpad minus + numpad enter on keyboard or back + right thumb stick button on controller. You can navigate them via arrow keys on keyboard or right thumb stick on controller. Pressing the keyboard or controller hotkey combo again brings you back to the game. Viewing them via LB/BB is not intended. The reason for this is because, functionally, everything is frontend agnostic/non-dependent. All functionality from manual toggling to custom music for text adventures, etc. is handled via external scripts and apps that use relative pathing. From Launchbox's perspective it's essentially just Windows shortcuts. You could remove LB/BB from the equation entirely and it would still be fully functional by just starting the .vbs files in each game folder, magazine folder, demo folder, etc. This is by design so that someone could theoretically import into any frontend and it would still be functional.

I don't know what the issue is with the magazines beyond something has gone wrong with your importer since by your own demonstration they work in the normal version. I know that BB itself has its own separate cache, so that could be related. I would recommend checking in LB first.

 

[stigzler]

1 hour ago, Zombeaver said:

I'm not sure what you mean by them being in Big Box. The manuals aren't integrated into LB/BB in any way (unless BB is finding them and doing something with them in the background which I'm unaware of, its unintended if so). As I said, they're toggleable in-game via the hotkeys. Numpad minus + numpad enter on keyboard or back + right thumb stick button on controller. You can navigate them via arrow keys on keyboard or right thumb stick on controller. Pressing the keyboard or controller hotkey combo again brings you back to the game. Viewing them via LB/BB is not intended. The reason for this is because, functionally, everything is frontend agnostic/non-dependent. All functionality from manual toggling to custom music for text adventures, etc. is handled via external scripts and apps that use relative pathing. From Launchbox's perspective it's essentially just Windows shortcuts. You could remove LB/BB from the equation entirely and it would still be fully functional by just starting the .vbs files in each game folder, magazine folder, demo folder, etc. This is by design so that someone could theoretically import into any frontend and it would still be functional.

I don't know what the issue is with the magazines beyond something has gone wrong with your importer since by your own demonstration they work in the normal version. I know that BB itself has its own separate cache, so that could be related. I would recommend checking in LB first.

 

Yeah - that's what I meant - I can access them from via the controller/keyboard. That's why I said they were available in bigbox. I shall choose my words more carefully going forward to try and avoid confusion. 

Don't think it's the importer as it basically just follows your guide to importing step-by-step. However, I will do it manually and see if I get any different results. 

Edited April 22 by stigzler

[Zombeaver]

They definitely work when imported into an existing collection when following my instructions.

[Zombeaver]

It's also worth noting that based on your previous demonstration you're not actually using the XML that defaults to the local versions of the magazines because it's loading up in a browser. I'm not sure if this was intentional or not since you show the relevant folder where the local one is, but to be clear the Default Local one needs to be used if you want the default launch behavior to use the local files (which I assume you do since you downloaded them).

[Zombeaver]

So, looking at your video again, it looks like the icons for them aren't showing up which indicates a cache issue. I don't think I've ever seen that result in a completely ignored playlist before but admittedly I don't use BB a ton to begin with so maybe it's possible. You can refresh the BB cache manually via System Menu > Options > Image Cache; either that or you didn't pull the image files for them over. I assume it's the former though just based on the way it appears. This is why I said I would recommend testing in LB first. I wouldn't mess with BB at all until you've done that (note that LB needs to be set to Platform Category view to display correctly with C64 Dreams).

If that doesn't fix it then I have to assume that something has gone wrong with the import process, either something wasn't pulled over or the sections that need to be added to the parents and platforms xmls weren't added completely/correctly. You'll also want to double check that all of the playlists have been pulled over - Zzap isn't technically a platform, it's a playlist. It's C64 Dreams (Platform Category) > Magazines (Platform) > Zzap!64 (Playlist). The implication if Zzap, specifically, is missing would be that either the Zzap playlist wasn't pulled over or that the parents xml wasn't updated correctly to include it under the Magazines platform.

[stigzler]

Found it. You'd forgotten to add this to 'Files To Import.txt':

Data\\Playlists\\C64 Dreams Magazines - Zzap!64.xml

Also, you'd omitted the '.xml' on the end of `Data\Playlists\C64 Dreams Magazines All Magazines`

I've coded workarounds in my app. Problem was it iterates through Files To Import.txt and uses its contents to auto copy the files therein. Errors in this spill through to the import. 

Because of the suggestions that it was my importer, I did some extensive testing and updated it with detailed user feedback on the import process. I'm satisfied it's pretty solid. It checks every file copy and every xml insert. Outcome from vanilla:

Spoiler

==== COMMENCING C64 DREAMS IMPORT ====
COPYING FILES FROM THE 'C64 DREAMS' SUB-FOLDER
C64 Dreams sub directory import: all files copied successfully.
IMPORTING FILES SPECIFIED IN 'FILES TO IMPORT.TXT'
Skipping Section Header line in Import.txt: [XMLS]
Skipping blank line in Import.txt
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Platforms\Games.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Platforms\Games.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Platforms\Demoscene.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Platforms\Demoscene.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Platforms\Diskmags.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Platforms\Diskmags.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Platforms\SID.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Platforms\SID.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Platforms\Magazines.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Platforms\Magazines.xml]
Skipping blank line in Import.txt
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\Games All Games.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\Games All Games.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\Games Favorites.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\Games Favorites.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 1.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 1.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 2.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 2.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 3.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 3.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 4.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 4.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 5.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 5.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 6.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 6.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 7.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 7.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Best Of - Vol 8.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Best Of - Vol 8.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Text Adventures.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Text Adventures.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams RPGs.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams RPGs.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Shmups.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Shmups.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Zzap Reviewed.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Zzap Reviewed.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Commodore Force.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Commodore Force.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Commodore Format.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Commodore Format.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Commodore Power-Play.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Commodore Power-Play.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Commodore Power-Play.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Commodore Power-Play.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Your 64.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Your 64.xml]
Skipping blank line in Import.txt
Skipping Section Header line in Import.txt: [IMAGES]
Skipping blank line in Import.txt
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\C64 Dreams] to [C:\Users\stigz\LaunchBox - Copy\Images\C64 Dreams]
Skipping blank line in Import.txt
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platform Categories\C64 Dreams] to [C:\Users\stigz\LaunchBox - Copy\Images\Platform Categories\C64 Dreams]
Skipping blank line in Import.txt
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\C64 Dreams] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\C64 Dreams]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\Demoscene] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\Demoscene]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\Diskmags] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\Diskmags]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\Games] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\Games]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\Magazines] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\Magazines]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Platforms\SID] to [C:\Users\stigz\LaunchBox - Copy\Images\Platforms\SID]
Skipping blank line in Import.txt
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\Games All Games] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\Games All Games]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\Games Favorites] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\Games Favorites]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 1] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 1]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 2] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 2]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 3] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 3]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 4] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 4]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 5] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 5]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 6] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 6]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 7] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 7]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Best Of - Vol 8] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Best Of - Vol 8]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams RPGs] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams RPGs]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Shmups] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Shmups]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Text Adventures] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Text Adventures]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams - Zzap Reviewed] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams - Zzap Reviewed]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Zzap Reviewed] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Zzap Reviewed]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Magazines - Commodore Force] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Magazines - Commodore Force]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Magazines - Commodore Format] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Magazines - Commodore Format]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Magazines - Your 64] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Magazines - Your 64]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Magazines - Zzap!64] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Magazines - Zzap!64]
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Images\Playlists\C64 Dreams Magazines All Magazines] to [C:\Users\stigz\LaunchBox - Copy\Images\Playlists\C64 Dreams Magazines All Magazines]
Skipping blank line in Import.txt
Skipping Section Header line in Import.txt: [MUSIC]
Skipping blank line in Import.txt
Import.txt import: successfully copied directory: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Music\C64 Dreams] to [C:\Users\stigz\LaunchBox - Copy\Music\C64 Dreams]
Skipping blank line in Import.txt
Skipping Section Header line in Import.txt: [PLUGINS]
Skipping blank line in Import.txt
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Plugins\C64_Dreams_Extras.dll] to [C:\Users\stigz\LaunchBox - Copy\Plugins\C64_Dreams_Extras.dll]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines - Zzap!64.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines - Zzap!64.xml]
Import.txt import: successfully copied file: [C:\temp\project tests\C64DreamsImporter\c64-dreams-v0.60\C64 Dreams v0.60\C64 Dreams\Data\Playlists\C64 Dreams Magazines All Magazines.xml] to [C:\Users\stigz\LaunchBox - Copy\Data\Playlists\C64 Dreams Magazines All Magazines.xml]
UPDATING LAUNCHBOX XMLS
XML Import: C64 Parents.xml successfully imported to Launchbox Parents.xml
XML Import: C64 Platforms.xml successfully imported to Launchbox Platforms.xml
==== C64 DREAMS IMPORT FINISHED ====
 

I also diff'd the launchbox Platforms.xml and Parents.xml pre and post insert. The Platforms one compares my launchbox diff post insert with the `Platforms XML Insert.txt` All done as directed:

https://www.diffchecker.com/Z8wfFA49/

https://www.diffchecker.com/9GY8UW6N/

I'll update my original post with the new version. 

[Zombeaver]

8 hours ago, stigzler said:

Found it. You'd forgotten to add this to 'Files To Import.txt':

Data\\Playlists\\C64 Dreams Magazines - Zzap!64.xml

Also, you'd omitted the '.xml' on the end of `Data\Playlists\C64 Dreams Magazines All Magazines`

Yep, I can confirm both of these are true. Both are corrected in the current WIP. Good catch.

8 hours ago, stigzler said:

Problem was it iterates through Files To Import.txt and uses its contents to auto copy the files therein. Errors in this spill through to the import.

It would probably make more sense to simply pull everything from Data\Platforms and Data\Playlists as it will always be everything in both folders. The same goes for Images\C64 Dreams, Images\Platforms, Images\Platform Categories\, Images\Playlists, Music\C64 Dreams and \Plugins. It will always be everything in those folders regardless of what's specified (or not) in Files to import.txt. I will probably end up changing Files to import.txt to eventually just state that anyway just to simplify matters. The Parents and Platforms xml inserts would of course remain as they are by necessity.

I appreciate the work on your app. Importing into an existing library has always been an overly fiddly process that's been more difficult than I would like for people to deal with so if this helps streamline that that's great. The next question would be is it able to deal with subsequent releases when existing (and potentially outdated) data is already present from a previous one? The process has to be repeated when a new version is released. In the case of the individual xmls for the platforms and playlists it's a simple overwrite. With images it's not quite that simple because sometimes files end up getting deleted between releases, or change filetypes (so they wouldn't be overwritten and an unneeded image is left behind if the existing folder isn't deleted beforehand). The inserted portions will change as well, usually just with new data, but sometimes with altered existing data. I'm not sure how difficult that would be to deal with - I would imagine a differential of old to new image files wouldn't be too horrendous albeit time-consuming (and it could always just outright delete the relevant folders beforehand instead, since that's the current process when doing it manually), but the Parents.xml and Platforms.xml changes I would expect to be more difficult since those would contain a lot of non-C64 Dreams data when incorporated into an existing library. Maybe it could just do a diff between the old and new insert files, then compare against the user's existing xmls and then update/add based on that? Sorry, I know this is a bit in the weeds but I just want to make sure that it wouldn't implode when someone attempts to import a new version on top of an existing one.

[stigzler]

No probs. Had the same thought, but didn't know how live the project was. My thoughts:

FIles

As long as launchbox hasn't added any files of its own to any directories that your project imports, likely best to clear any existing files before importing the new files. That will work as long as your releases contain all files necessary rather than a 'cumulative update' where you only include new or updated files. In the latter (think version control) you'd need to produce a full manifest of files/directories to import and any to delete.

Best would probs be a hybrid as method one won't know if there are any root directories to delete. Thus would need a likely small manifest of these (if you want to be super tidy)

Xmls

You're right. A bit more tricky but not impossible. At the moment I just do some string/file manipulation to append yours to the end of existing as per your instructions. I did start to look at XML Element manipulation (comparing existing with potential import) but once realised I could just append text, changed tac quickly! It'll take a bit more research (the main issue was there was no sub element that could be treated as a unique id) but doubt it's impossible. 

Happy to collaborate. 👍

Edited April 24 by stigzler

[Zombeaver]

6 hours ago, stigzler said:

as long as your releases contain all files necessary rather than a 'cumulative update' where you only include new or updated files.

This is how it works currently, yes. Each subsequent release is complete. There is no update process per-se at the moment as there's too much in flux currently from one version to the next and I don't expect this to change until at least v1.0. It requires a complete delete and replace. There have been multiple instances of significant backend changes over the course of the project (and this will be true in the next release as well) so it would be impractical to do it any other way until that's no longer the case.

The relevant folders for the purposes of importing would remain the same as those I listed above though. It would be those plus the main C64 Dreams subfolder of course.

If you have any questions or need help with anything please feel free to hit me up on my Discord. That's where I typically post about ongoing progress and collaborate with other developers like StatMat of the OL64 project.

[stigzler]

Cheers fella. Likewise, if you're thinking about a new release and wanting to have the importer accommodate this, then drop me an IM on here rather than my cluttering up this thread! It may be worth planning more long term and proactively around general deployment strategy given the need to sync c64d and lb Xmls. It's already nagging away at the back of my brain, so I'll invariably have a play with it at some point!

Edited April 24 by stigzler

[Zombeaver]

So I asked this over on my Discord but I'll mention it here as well in case anyone has any ideas:

Does anyone know of a good option for AI upscaling that would yield good results for manual scans (primarily text, but some art as well)? Part of the process for each update is upgrading manual scans wherever possible. A higher quality scan is obviously the preferred method for this, but because of the obscure nature of this stuff that won't always be an option. It seems to me that AI upscaling could be a good option for this but my experiments with it thus far have yielded mixed results. In some cases it's a bit of an improvement, in others it looks a bit like using one of those awful "Eagle" shaders on a SNES game (a smeary mess). It seems like with as much as this tech has advanced in the last few years that surely there has to be a decent option for this kind of thing by now.

If it's free that would be preferred so that I could work on them myself, or if not and someone has access to a relevant platform and would be willing to volunteer some time to work on it I can supply the media in question. I'm open to any ideas here. I realize it's probably not going to work in every scenario, but if this is an avenue to improve some of them I'd like to do it.

[C-Beats]

@seaview59 and @JereBear I believe use an AI upscaler for clear logo requests. @DOS76 may know of one given I know he was working at restoring some digital comics a while back.

[Zombeaver]

Thanks @C-Beats! Hopefully one of them will have some ideas here. I would think there's probably some option out there that would work well here. I've messed around with a few different free options online and didn't have great results, but admittedly I don't have a ton of experience with this.

 

[seaview59]

6 minutes ago, Zombeaver said:

Thanks @C-Beats! Hopefully one of them will have some ideas here. I would think there's probably some option out there that would work well here. I've messed around with a few different free options online and didn't have great results, but admittedly I don't have a ton of experience with this.

 

I use topazlabs.com and imgupscaler.com and with both you sometimes have to prep the image before hand in photoshop in order to get decent results. Usually the prep in photoshop is to blur the image or change the levels, if it was scanned so clearly you can see the halftone print pattern.

[launchretrogirl2562]

29 minutes ago, Zombeaver said:

Thanks @C-Beats! Hopefully one of them will have some ideas here. I would think there's probably some option out there that would work well here. I've messed around with a few different free options online and didn't have great results, but admittedly I don't have a ton of experience with this.

 

Could you send me some examples of manuals or pages you would like to see upscaled. No guarantee of course, but I sure can give it a go and see what the result would be.
If it turns our to be successful I wouldn't mind to write you a how-to so you can do it yourself.

[Zombeaver]

17 minutes ago, seaview59 said:

I use topazlabs.com and imgupscaler.com and with both you sometimes have to prep the image before hand in photoshop in order to get decent results. Usually the prep in photoshop is to blur the image or change the levels, if it was scanned so clearly you can see the halftone print pattern.

I have Photoshop. I'd like to avoid another monthly subscription just for this so imgupscaler is probably out (and as a side note I seriously hate this pricing structure that a lot of these sites have of pay per number of images processed, that entire model would be unusable for my needs). I've heard of topaz, and looking into it a bit it looks like you can pay once and then use local software, which is much more appealing to me. I'm a little concerned about the fact that it says includes 12 months of updates though - does the software outright stop working after 12 months if you don't pay again or does it just not receive updates anymore (this is implied but I want to be sure)?

I'd be leery of the former but if it's the latter that could work. 

12 minutes ago, launchretrogirl2562 said:

Could you send me some examples of manuals or pages you would like to see upscaled. No guarantee of course, but I sure can give it a go and see what the result would be.
If it turns our to be successful I wouldn't mind to write you a how-to so you can do it yourself.

Definitely! I'll send some examples in a couple hours. Thanks for the offer!

[Zombeaver]

Someone on my Discord just recommended Upscayle which is apparently free and open source. I'll be giving that one a shot tonight.

https://www.upscayl.org/