C-Beats

That gets put in there if we get an error from RAHasher attempting to hash the ROM and get us a value for it. You can try to remove that and save the file and try the scan again and see if it comes back like that or not. If it does we'd have to walk through and show ya how to run the executable directly to potentially get you a better answer as to what is going on.

Editing the OP so you don't dox yourself and your API key, but this window shows the issue at hand. You only put the bit in the text box that comes AFTER the /id/ in your Stream URL (should be the same value in the text box on the steam page where you put the information. So in your case you would just put "cadet_stimpy" (without the quotes) not the entire URL.

Again, I don't care about the Games DB ID. It has nothing to do with RetroAchievement functionality. Look for the field I specifically asked you to.

I can't remember which of the Sony systems it is but depending on what command was used to create the CHD (createcd vs createdvd) it can fail in RAHasher which would potentially be the reason we aren't identifying it. If you look in \\LaunchBox\Data\Platforms\Sony PSP.xml is there any "RetroAchievementHash" value assigned to the game in question?

We don't typically offer (or really want) all older versions of LB floating around simply because it makes supporting and troubleshooting a pain in the butt. If there is a specific reason you need any older versions of the app reach out to support@unbrokensoftware.com and state the reason you need an older version and they can get installers.

Also DB ID and RetroAchievements aren't connected. We search by the ROM Cheevo hash using their RA Hasher tool. You don't need to have a DB ID attached to detect RetroAchievements for a game.

If you click that link where it says the number does it go to the right DB page? The number in the DB url and the number shown in the app aren't always the same number.

Basically need something that can translate the raw frame output of MPV into something WPF can consume (as well as audio) and then make sure the two streams stay in sync. I'm unsure if the stutter issue was just in how that translation from MPV -> WPF was happening or MPV itself (though I highly suspect the former)

Only times I've heard something like this reported is when in the Controller options you have "Enable All Controllers" selected. Some machines the scan for controllers seems to take longer than normal and the polling logic causes some systems to lag out the mouse when it's doing so. If you turn that option off I'd assume your mouse would go back to working the way it should. Let us know if that's not the case though.

Achievements are something you earn in game for doing something notable. Badges are a LaunchBox feature that put small images/icons next to a game when enabled so that you can easily see at a glance that certain criteria applies for it (like it's one of your favorite games, it has controller support, you own on a specific storefront, etc, etc)

Games on occasion get matched to the wrong ID. For example I just checked Doom Eternal on the GamesDB and it links to one of it's DLC and not the main game. When you run into issues connecting Steam games like that file a support ticket and we can look at getting it resolved.

We actually implemented that before FFMPEG internally and the only wrapper we found we could use without breaking license resulted in really heavy playback stuttering to the point it was scrapped since it didn't seem quality enough to use in a public release.

What happens when you go to play one of the games you just imported? I can't remember if MAME is set up to use the whole "hey we noticed you don't have an emulator, let me grab one for you" process or not. MAME is a bit odd in that you have to have the version that matches your ROMs and so we can't just grab the newest version and it guarantee to work so lot of those processes don't support grabbing it.

Just use the regular ROM import and turn off any skip settings in the MAME options that appear (skip unplayable, skip casino, etc, etc)

I haven't had a chance to look into it but can pretty much guarantee they changed some of the back end we use to get your library information. They just pushed changes to their own client that ands a lot of interconnections with other storefronts and various other features so wouldn't surprise me to find out they messed around with the back end as well.