[Jamie Shaw]

Is an update required to the Profile Editor required for 0.82, or does 0.81 cover this release?

[Jamie Shaw]

Just wanted to give you a massive thanks for this—finally got around to sorting my profiles (all 16 of them, so far…) and updated to 0.81 in less than an hour.
No manual rebuilding of sampling rates required! 🙏

Moving from the old OSSC editor, I severely missed the JSON format as I find it useful for version control and diffing profiles ensuring settings are consistent. With this I finally have it back again.

My only complaint is that you released it a day early—if you’d waited until the 18th, it would’ve been a stellar birthday present. 😂

[Jamie Shaw]

Jumping straight into this because I’m still running 0.79—no time to rebuild the profiles with a six month old in the picture. Using my free time wisely 😂

https://files.sha.wtf/jamie/YoqiQucE81.bin

That’s my “generic” profile for OSSC Pro v0.79

[Jamie Shaw]

I assume this new profile format is similar in structure to that of the Pro profiles now?

Hopefully that’ll spur some work on an editor for those (for both OG and Pro), as it’s my only gripe with the Pro (and I guess the OG now), and it resetting settings when new settings are added.

I understand and appreciate why they do, I personally don’t have the time to re-walk each profile and reconfigure for the 20 or so I have setup. 😅

That said, blissed to see that excellent work continues for both OSSC platforms.

[Jamie Shaw]

This web app can only edit profiles for the normal OSSC, not for the OSSC Pro, is that correct?

Correct. There is no upgrade path from the OSSC to OSSC Pro, if that’s what you’re asking.

[Jamie Shaw]

I’ve resorted to HEX editing in combination with a spreadsheet to import and export timings, but it’s not everyone’s cup of tea.

After I ended up re-doing them all after 0.78, I ended up keeping a spreadsheet too 😅

It’s a good failsafe, but certainly wouldn’t be as easy as a profile editor, or at least conversion to JSON.

[Jamie Shaw]

Whilst it pleases me that the OSSC Pro is getting ongoing firmware updates, the lack of profile editor like the OSSC has is a bit of a kicker.

Having spent a good few hours into fine tuning the 20+ profiles for the consoles I have, it’s a pain having to walk them all for the updates. I completely understand why from a binary point of view, but the ability to convert to and from JSON was an absolute life saver—and great for version control of the directory of profiles I have.

I mean, I’m happy to take a look myself if someone could point me in the right direction.  Building web apps I’m familiar with, but encoding/decoding binaries without some assistance puts me at a non-starter. 😅

[Jamie Shaw]

Thanks for the update. For ease, I’ve organised a replacement OSSC Pro to be shipped out and then this one returned to VGP, as it was only purchased a few months ago and still under warranty. It also means that this unit can be captured for debugging if so required.

Saves the hassle of finding a reliable flasher for JTAG, and any additional problems this may introduce.

[Jamie Shaw]

Cool. Keep me posted. I’ll stick on 0.77 for now then, and get around to upgrading (and fixing) following tests. 🙂

[Jamie Shaw]

Any recommendations?

What’s the risk of a lousy programmer? Bricking the device?

[Jamie Shaw]

Thanks.

I’m kinda at a loss at this stage, having tried several cards (of various sizes), formatters, and devices. All are fine for profiles read/write, but firmware always fails.

In regards to JTAG, it sounds like a viable option if given step-by-step instructions. If it is a bad FW on this board, hopefully a clean flash could resolve that. If I could provide any debug logs, I would… 😅

Failing that, it’s going to be a return for replacement with VGP (and have to deal with the customs for returns 🙃).

[Jamie Shaw]

Firstly, thanks for the assistance with this.  It’s appreciated.  Apologies if this isn’t the correct thread for support, I’m happy to move this over to the GitHub repo to keep it organised if required? (Or a different thread on the VGP forum, as the OSSC Pro was purchased from them 12/02/2025).

So, I’ve tried all of the following:

• SD Card Formatter for Mac, using both “Quick Format” and “Overwrite Format”
• Disk Utility (macOS), using both FAT32 and exFAT, using MBR Partition Map.
• newfs_msdos command via Terminal (macOS)
• A 60GB PlayStation 3
• My wife’s old Panasonic Lumix digital camera

All yield “Failed (-5)”. And just to confirm: no SD card provides -1, no FW file gives -2.

As previously mentioned, saving/loading/renaming profiles on the SD Card gives me absolutely no trouble at all.  I just seem to fall at that CRC check for whatever reason.

And to be on the same wavelength, ossc_pro.bin yields the following checksums:

• MD5: b9c40357d7fd719cfc4f29713ad3e06b
• CRC32: 1b812510

• This reply was modified 1 year, 4 months ago by Jamie Shaw. Reason: Gratitude

[Jamie Shaw]

I normally use the SD Card Formatter for Mac as it’s never given me any problems with any flashcarts (EverDrive, EZ Flash, etc).

I’ve just tried with two other cards, both 32GB (larger than the previous 1GB I’m using for profiles). One formatted to FAT32 with 32k clusters, the other formatted to exFAT.

Both give error -5.

• This reply was modified 1 year, 4 months ago by Jamie Shaw. Reason: Fix duplicated link text

[Jamie Shaw]

Works absolutely fine for profile load/save.  Just firmware updates that seems to be giving an issue.

This is my first upgrade since getting the Pro, which came preinstalled with 0.77.  I could try reinstalling 0.77, to rule out the card…

UPDATE: Tried reinstalling 0.77, same -5 error. I will try a third, larger SD card that might be more reputable.  Other than that, faulty OSSC? 🤔

• This reply was modified 1 year, 4 months ago by Jamie Shaw.

[Jamie Shaw]

Having issues myself with installing the update.  Tried two separate SD cards, both formatted to FAT32.  Both give “error -5” when using the renamed firmware .bin from GitHub.

Thoughts?

[Author]

Posts