Take and Scrape Your Own Screenshots

CoolCat

@meleu hi.
Yes, im using the second method and worked great for me.
I was talking of have a standard layout for easier maintenece.
The script allready presume some stuff, as far as i saw.
For me the script solve the "Issue", im tring just to put things together for dont lost my screenshot setup, and have it running nice.

Sorry, my fault. I changed the subject even if it is topic related. Your english is ok :)

Best wishes,

meleu

@CoolCat said in Take and Scrape Your Own Screenshots:

@meleu hi.
Yes, im using the second method and worked great for me.

Phew~
:-)

I was talking of have a standard layout for easier maintenece.

It's up to the user define it at retroarch.cfg and choose something that makes sense to him/her (this is the RetroPie way-of-life :-D ).
I like only one /home/pi/screenshot directory for every system, our mate @herb_fargus likes to put the screenshots i /home/pi/RetroPie/roms/SYSTEM/images directory. You seem to prefer /home/pi/RetroPie/screenshots/SYSTEM...

The script allready presume some stuff, as far as i saw.

Indeed, the method 1 forces some directories, but we assume that the user has the knowledge to edit the script to change it to his/her taste (if hasn't, we are here to help).

The method 2 takes the directory from retroarch.cfg.

Now I would like to talk about something you said previously:

It would be handy if it could do it as batch on a screenshot folder.
If i have the screenshots allready it fill the gaps.

If you wanna scrape all the screenshots you already have you can use my runcommand-onend.sh script (from method 2). You just have to give it the proper arguments (the 1st and the 3rd ones) and make sure that your screenshots have the same name as the rom (except the extension). Something like this:

# IT'S JUST AN IDEA. I DID NOT TEST IT. CHECK BEFORE EXECUTE!
for system in "$(ls -d1 /home/pi/RetroPie/roms/*)"; do
    for rom in "$(ls -1 "$system")"; do
        /opt/retropie/configs/all/runcommand-onend.sh "$system" blablabla "$rom"
    done
done

Cheers!

herb_fargus

@meleu my reasoning for keeping the images in the rom folder is it makes it more portable so if you only want to transfer snes Roms to a new build they are already scraped without need to scrape again or dump everything but it's just my preference for my builds, they can be placed wherever as you said.

CoolCat

@herb_fargus yes, i said to have a screenshots and saves folder was for better maitanance and follow the retropie structure of dirs.

As pointed out if you have all screenshot in one folder could have conflict of same titles and diferents ports.

Otoh, have the save files and screenshots on the rom folder just bloats the folder.

I hope retropie got a little more polished in this field having this done by default at install (course you could change that after setup, though).

I will try the atract mode, it seems to have tweak emulstation (that miss some stuff) and i dont know if it used metadata as filters (tag).

Another nice feature is use crc for identify roms. (Probabbly best suited for cartridges)

http://www.arosworld.org/forum/viewthread.php?thread_id=144

Anyhow i love the retropie way of doing stuff, just miss a feature here or there but it glues things very nice, at least for me it feels ther right way of game center :)

Best wishes.

CoolCat

@CoolCat ps: here it has a video just out of curiosity :)

meleu

I've noticed that the Take and Scrape Your Own Screenshots wiki wasn't listed in the wiki's front page nor the sidebar. Then I've just added. ;-)

meleu

I noticed that this trick doesn't work for "ports". The reason is the same as the runcommand launching images doesn't work for ports.

derebo

Hi,

I'm running v1.1.10 against a non-merged full 0.37b5 romset (checked in Clear Mame Pro) with 2241 roms to notice many hash not found issues.

eg.
2016/12/25 14:31:43 INFO: mame\1943kai.zip, hash not found
2016/12/25 14:31:43 INFO: mame\005.zip, hash not found

As the romset is perfect, is there any way I could provide @sselph or any interested with any data you may need so that they could be properly hashed?

Regards,

meleu

@derebo (assuming you are using the method 1) I think it's happening because mamedb is down, so the method 1 won't work for mame roms...

Maybe you can try this trick here for mame:
https://retropie.org.uk/forum/topic/6056/manually-generate-mame2003-gamelist

derebo

Thank you for writing back @meleu I think my "method" is somewhere inbetween. The fact is my non-merged full 0.37b5 romset (2241 roms) matches perfectly the 0.37b5 snaps (2241 snaps, a lot of work saved!) so what I do basically is:
1.- add
screenshot_directory = "/home/pi/RetroPie/roms/mame-mame4all/images/"
to
/opt/retropie/configs/mame-mame4all/retroarch.cfg
2.- move roms to Retropie/roms/mame-mame4all
2.- move snaps to Retropie/roms/mame-mame4all/images
3.- run
/opt/retropie/supplementary/scraper/scraper -add_not_found=true -append=true -download_images=false -image_dir="images" -image_path="images" -image_suffix="" -img_format="png" -img_workers=0 -no_thumb=true -thumb_only=false -thumb_suffix="" -use_ss=true -use_gdb=true -use_ovgdb=true -workers=4

Then gameslist.xml is created. I think those steps might be useful to users who already have a preference for snapshot packages.

However, I wonder what would be the best approach in the following scenario where there it no a rom <--> snap match:

1.- add
screenshot_directory = "/home/pi/RetroPie/roms/snes/images/"
to
/opt/retropie/configs/snes/retroarch.cfg
Move all 3438 No Intro SNES roms (Nintendo - Super Nintendo Entertainment System (20161130-222348_CM).dat) to
Retropie/roms/snes
Move all 3352 .png snapshots (No-Intro 20061119 Super Nintendo Entertainment System Screenshots.7z) to
Retropie/roms/snes/images

One more problem, snapshots name do not match rom names but it is relatively easy to sort it out.
Eg. Actraiser (U).png versus ActRaiser (USA).zip
So I have run a number or find and replace to swap U for USA, J for Japan and so on. Once .png files match their counterparts in the roms folder, the same scraper command is run to generate gamelist.xml
In any case, it is clear that there are less snapshots than rom files so there will be roms without snap. Any ideas on how to find out (list) what are those roms?

PS. I am going to have a good look at that link. Thank you for it.