Steve
Forum Replies Created
-
AuthorPosts
-
Plug the lumacode RCA into the Y (green) connector on the OSSC Pro.
Set AV2 to RGsB input mode.
At this point, you should get an image but it’ll be a scrambled mess. If you get nothing, check the continuity from the chip-side of the PPU to the PCB side of the Lumacode board.
Assuming you have an image, you’ll then need to do the following:
Set the OSSC mode to “Line Doubler – Adaptive” mode
In the “AV1-3 video in opt.” menu – enable Lumacode and set it to “NES”
In the “Line multiplier opt –> Adaptive LM opt.” menu, set “240p/288p mode” to “SNES 256col”
At this point you should have a crisp stable image but the colours are probably messed up.
Press the Phase button on the remote and change Sampling Phase to around 16 degrees, or until the colours are near enough correct.
You can then tweak the G/Y Offset in the “AV1-3 video in opt.” menu to try and fine tune the colours and get rid of shimmering.
This is the process that worked for me. The image is very sharp although there is some vertical noise, my console has not been recapped so it could be related to that, or the original NES PSU, or any other number of things, but generally speaking, the image is pretty amazing.
Same issue here, Lumacode is enabled in settings but I’m getting no image whatsoever.
-
This reply was modified 2 months ago by
Steve.
Sorry to necro this, but the RGC cable does work, contrary to what he says, as that’s what I’m using with mine.
(Sorry, I thought I’d replied to this days ago, looks like I didn’t notice that the forum had starting blocking my duck.com addy)
Yeah, I had the default input set to AV4 (I forget why as I’m not currently using that anyway), and that’s when I get the “no output” behaviour, as I now have it with it defaulting to the TP output, it’s working just fine.
Thanks for trying it. I’ve tried cycling through all 3 modes, makes no difference.
I did a settings reset, that didn’t help either. I also tried a different monitor via direct HDMI connection, that behaved the same way as well, so looks like it’s a pecularity of my unit.
What I’ve done as a workaround is set the startup mode to the Test Pattern, looks like that’s enough to kick things into life as that will display automatically at startup, and if I switch to composite at that stage then it works straight away. I’m ok living with that.
-
This reply was modified 2 months ago by
-
AuthorPosts