OSSC Pro firmware v0.81

[marqs]

Firmware version 0.81 has been released:

* Robustness fixes
** SD card corruption and freezing issues resolved
** Csync output AND-type implementation added as default
** ADV7280 comb filter config setting corrected
* Support for custom Lumacode palettes added

Download link
Update instructions

Note: The following settings have been updated, thus their changes saved using previous firmware versions are not loaded from existing profiles:

* Lumacode and Lumacode palette set (due to new custom palette support)

[Ray T]

Updated from V0.79 without issues.

[tjyllbo]

Thanks again, marqs!

[aotta]

Thank you Marqs! where could we find some more info about custom lumacode palettes working? I’m interested but can’t try for now the new feature since my PRO has sent back to RMA…

Edited:  sorry, just found the info updated in the wiki, i’ll start from there!

• This reply was modified 5 months ago by aotta.
• This reply was modified 5 months ago by aotta.

[cjd280]

I’m running into sync issues with my PVM 14L5 with .81 update and the legacy AV out.  I use YPbPr out (I also tried RGsB, similar issue), and over like 30 seconds the screen slowly turns a pink hue.  I’ve seen this when I first got my Mister connected to it, I had to change some sync settings in it (I forget what they were) to stop it from happening.  If I toggle external sync on and then back off, the colors are back to normal and then slowly turn pink again.

I rolled back to .80 and the issue has gone away.

Is this possibly related to “Csync output AND-type implementation added as default” in the release notes?

[marqs]

You could try setting Output opt. -> CSync combiner to “Legacy (XNOR)” which was the default (and only) type available in v0.80 and earlier.

[cjd280]

Thanks, that seems to be working.

I had tried it originally, but choosing it from settings doesn’t seem to apply it. I chose it from settings this time, then loaded a saved profile and it applied that option. Not sure if that is a bug or not.

I’ve saved it in my profile and its remembering the setting across power cycles now.

[FlashShift]

Hi- I upgraded from 0.78 to 0.81, and had to downgrade:

1. Lumacode seems to be broken; I have the c0pperdragon chip on my PPU on both a NES and a Famicom, works flawlessly with 0.78 however is mostly green and yellow using 0.81. I’ve gone through and verified the settings were correct. Downgrading rectified the problem.

2. It behaves differently with MCR games. While TRON seems to work better on default settings, Spy Hunter appears extremely dark and there is no way to improve it other than to turn off the different clamp settings (which makes the picture jitter). I’ve checked RGB gain on my Axunworks and it is too dark to see even at max with 0.81. Works fine with 0.78.

Would be happy to work with anyone interested in trying to debug the firmware; for now I’m back on 0.78.

• This reply was modified 2 months, 4 weeks ago by FlashShift.

[BuckoA51]

Can you describe your full video chain i.e source into OSSC Pro how (AV1,2,3, what cable?) and what output you’re using (HDMI or Extra AV out?).

[FlashShift]

From NES/Famicom straight into the AV2 port on OSSC Pro (Green/Y, IIRC), out standard HDMI port. Nothing special about the setup. I’ve tried with both AV2 YPbPr and RGsB (and scrolled through the rest for good measure).

For Spy Hunter, it’s going through JAMMA adapter into Axunworks SuperGun (also tested my HAS), into SCART, and out HDMI. Have tried Scaler, Line Multiplier, plenty of different settings. It’s almost black. Can barely see it with 0.81.

[marqs]

It would help if you can test the firmwares in between to help pinpointing where the issue appeared since I have neither hardware.

[FlashShift]

It’ll have to be this weekend but I’ll test 0.79. 0.79 is where the most changes got made to Lumacode.

[BuckoA51]

Also can you let us know which hardware revision of OSSC Pro it is? (sticker on the underside).

[FlashShift]

There doesn’t appear to be a sticker on the bottom; I bought it from Stoneage Gamer maybe six months ago FWIW.

It looks like FW 0.80 is where the problems with Lumacode start. 0.79 works ok. I’ve attached screenshots between the two versions.

[marqs]

@FlashShift You’re using the following settings and tried adjusting sampling phase, right?

* 240/288p mode = SNES 256col
* Lumacode = NES

[Author]

Posts