Boxart Buddy [PRE RELEASE] - Scraper & Interactive Boxart Composition

Boxart Buddy is a boxart scraping and image composition tool for MuOS.

Written from the ground up for flexibility and performance, the goal of this application is to allow you to scrape boxart for your rom collection and create “Mixes” of boxart that suit a variety of themes.

Following installation, all functions and configuration can be done on device meaning no XML files, or tinkering with manual configurations. The goal of the application is to beautify your rom collection as quickly as possible.

Boxart Buddy supports all devices that run the latest version of MuOS (2508.1 Canada Goose), including all Anbernic and TrimUI devices (NOTE: I’ve now had multiple reports that this version freezes on TrimUI Devices, so until I get a device and fix the issue it’s not worth using on TrimUI devices, I’ll fix this prior to full release)

This is a pre-release version and testing and feedback is welcome.

Please checkout the readme on github for quickstart guide and installation instructions.

9 Likes

Mega grandiose this scrapper but not work on my TSP, it freeze… but well on my 40X H :wink:

Looks fantastic, nice work!

1 Like

Ahh that’s a shame. I have not physically tested on TSP so I’m not sure why it freezes, but I plan to buy a Brick soon and will test it on that.

1 Like

ok thanks and maybe in your next version make the game liste by console and not by name… it will be more fun and easy to use…

and tell me how to use the template…

and, sorry, i have this error every time when I scrap my games…

i have enough espace on my console…

The game list should be grouped by console first and then name already? Maybe I can add some controls to change the sort order, Are you saying that you would prefer it to be A-Z (not grouped by console?

The error is nothing to do with SD space, it looks like it’s hitting a particular issue with a rom filename, probably a character it doesn’t like (emoji / kanji).

If you’re able to provide the log file (enable first under CONFIG > LOG > FILE LOG - and then restart the app), it will help me fix the problem.

1 Like

Yes by console is more fun…

where are stored the log file ?

And on mix page, i choose my format but when i scrape my game, i have this one and not the one i choose…

and your app use .xml format on MIX like other scrapper ?

and here the right place for the glyph because u use it in wrong place :

BoxartBuddy / glyph / boxartbuddy.png

Did you press Y and filter by system? Sounds like you have all systems selected.

yes i use it and i have only the console i choose but i need it after the scan, rom must be by console and not listed to A-Z

I’m able to replicate the issue with the character encoding, so I will work on a fix for that today, it only happens with certain combinations of characters like “tá,bâ”.

The log file is in /mnt/mmc/MUOS/application/BoxartBuddy/data/logs/{date}.txt

Thanks for note on the Glyph, I’ll change it!

I don’t use XML files for templating, I want to avoid that and make everything configurable in the GUI, but I’m happy to add more options to the layout to make it more flexible.

On the mix page, did you choose the preset using the “START” button? A star will appear above the preset name after you do this. Also the button on the HOME page will contain the name of the preset after you change it.

After you change it you need again “Generate Mixes”

Here is the log file : log-2025-09-23.muxapp (60.4 KB)

change the extension to .txt, the sit not accept txt file sorry…

bellow my mix page and home page (not easy to take the screeshot with the new combinaison on Goose L2+R2+X lol

And after you run the “Generate Mixes”, is the new mix here on the ROM page?

I’m trying to figure out what is wrong, is it failing to generate the correct MIX, or is the export (pack) process failing in some way….

Of course after generating the mixes, you need to “pack”, are you doing this?

i think the export pack…

That’s only showing the screenshot, press right → and then go down to the ‘mix’, is it generated correctly?

Let me know your SD card setup (two SD cards, is catalogue on SD2?). Program assumes if you have 2 SD cards then catalogue is on SD2 (auto). You can manually adjust it in the config (CONFIG > PACK)

yes, i have the image generated…

only use SD1

Great app man :100: Goona try it soon!

1 Like

I’ve released a new version that fixed the issues identified so far and a few others:

  • fixed issues with utf8 string truncation causing fatal error
  • fixed issue with libretro scraper which was causing it to fail, so scraping should be much faster when libretro is enabled
  • fatal errors now emit a crash log for easier bug reporting
  • defaults file logging to enabled at default level during pre-release period
  • fixes the db reset process within config

I’ve also tested the pack process on devices with 1SD and 2SD and it “work for me™”, but still want to help if that doesn’t work for anyone, I’m just not able to replicate. The default behaviour is to install images into “/run/muos/storage/info/catalogue/” after pressing the “PACK” button on the HOME screen.

edit: given that I’ve had multiple reports of failing to install images during the final part of the process (PACK), this is the function that identifies the install path for images as it stands currently. boxart-buddy/boxart-buddy/module/environment.lua at main · boxart-buddy/boxart-buddy · GitHub

I did make late amends to the path finding logic due to the releases of Goose and then Canda Goose so It’s probably that there are issues here. My assumption is that “/run/muos/storage/info/catalogue” points to the correct location of the catalogue folder given the current MuOS configuration but that assumption may well be incorrect.

If reporting PACK issue please tell me your MuOS settings from (CONFIGURATION > DEVICE BACKUP > Metadata Catalogue), as well as you SD card setup (1 or 2), and if this is a fresh install or upgrade, I’ll try and track this down. Thanks

5 Likes