Galdelico wrote:Just out of curiosity, Marqs. Any idea about when you'll release the firmware update featuring fully adjustable scanlines? I'm spending quite a long time to tune up my CRT profiles for 480i sources, then I read the Wiki and realized it could all be pretty much useless, should the new firmware land relatively soon.
My plan was to add some usability improvements (profile linking to input, audio gain adjust, and possibly integrate borti's backlight timeout changes) on the next fw and then implement extended scanline controls for the one following that. However, snes_dejitter and cps2_digiav projects have taken my attention recently, so those ossc features are still to be implemented/integrated. I'll probably now just go ahead and cram them into one fw update once those other projects are in suitable state.
paulb_nl wrote:H6rdc0re wrote:My OSSC v1.6 outputs in video levels and setting black level to low (limited range) on my LG 55C6V and LG 55EG910V OLED TV's gives proper levels.
The OSSC outputs Full Range RGB only so you should not be getting proper levels on low if low is truly Limited range. On low, black levels should look crushed with most consoles. White levels will probably look ok because most consoles output max around 240 instead of 255 for white with default gain on the OSSC. Some modded(attenuated) SNES 1-CHIPs/Jrs will output even lower around 225 for white.
If you increase the gain so that full white is 255 then you should be getting proper grayramp levels on Black Level high setting.
Yes, ossc outputs full-range 24bit RGB. It should be very easy to verify/select the correct setting on TV by just using power-on test pattern as reference.
bobrocks95 wrote:Fairly certain Csync is routed to the Hsync pin. I can double check to be certain.
If you use DSUB input for RGBS, keep in mind that c-sync needs to be TTL-level. Also, "digital" sync inputs go through a bit different processing path in the digitizer chip than the analog ones. Both paths have their own set of bugs: interlace is more prone to cause issues with TTL sync, while 240p signals with successive "1"-fields can cause trouble on the analog sync path.