[Fluffyredlobster]

H. Samplerate of 1200 with H. Backporch adjustment does the trick for me with VESA 480p Line3x. 🙂

Regarding HDR persistence – Full TX Setup doesn’t solve this for me, my TV still drops out of HDR mode on resolution change.  I don’t use the HDR flag so it’s no issue to me but maybe useful info for someone.

[Fluffyredlobster]

@snk64 While I had everything out for the 480 L3x stuff above I tested your HDR flag issue – I get it as well.  I never messed with HDR on earlier firmware revisions so can’t say if it’s new or not.  Like you said, if you change resolution (or line output mode) the TV reverts to non-HDR (the OSSC menu still says HDR is on, but you have to toggle it off then on again to get the TV back into HDR mode).

It’s probably worth logging a bug on github for it.

[Fluffyredlobster]

@eadzon64 I get similar (not identical) results to you using 480 Line3x from my Windows 98 PC running at 640×480.  I get a few pixels cut from the left and many cut from the right.  Looking at the Windows 98 start bar, the clock is cut off completely, to give an idea of the amount cut – I’d estimate around 10% of overall width.

Like you I could not tweak this out in Sampling options.  I tried a PC Matrox Mystique, AGP Matrox Millenium G200 and an unknown brand Geforce 2 MX400, all directly connected to OSSC, and also tested going via a Voodoo2 – all with the same result.  Windows was set to 640×480 True Colour in all cases.

Even without the cut, the picture quality was better in Line2x mode to my eyes, so I am going to stick to that.

Obviously real DOS mode uses the 400p VGA modes so was unaffected.  While I had everything plugged in I couldn’t resist trying the 1600×1200 Line3x Generic mode for 400p and it looked great but the OSSC rebooted a few times during testing – as the wiki says, not guaranteed to work, so YMMV.

[Fluffyredlobster]

Patrick Sestak – I’ll try my VGA cards and see if I see anything similar.  Can’t do a Voodoo5 but I can do a Voodoo 2 and a couple of Matrox.

400p mode detection would be great if that’s ever possible.  I have two profiles, one for each mode and I always forget to switch to the right one!

[Fluffyredlobster]

Yeah thanks for 10 years of support and updates 🙂

1.10 fixes the input detection loop nicely for me.

[Fluffyredlobster]

So 1.07 and 1.08 do not get “stuck” on AV3 for me.  I still see an occasional sync signal reported on the LCD for a fraction of a second but it correctly rotates back around to AV1.

I’m pretty confident that between this and Pushky reporting the same issue it’s a firmware issue rather than a (my) soldering issue, so I’ll log an issue on github for it.

edit – issue logged: https://github.com/marqs85/ossc/issues/113

• This reply was modified 1 year, 1 month ago by Fluffyredlobster.

[Fluffyredlobster]

Interesting point – I tried reverting to 0.90 but did not try going back to 1.08 / 1.07.  I will try that later today and report back.

[Fluffyredlobster]

Ahh, thanks @Pushky for confirming that – at least I know it’s not something I have broken 🙂

[Fluffyredlobster]

@manuelink64 options 1 and 2 are basically the same thing.  Resistor R35’s pad is connected to pin 46 of U2 so both options achieve the same end.  The resistor pad is just easier to solder to than the pin.  I assume if you go straight ot pin 46 you still need to remove the resistor.

Option 3 I haven’t tried myself but Morpheus_79 a couple of pages back has done a really neat job and I’m tempted to give it a try, just note his comments on the pin numbers being incorrect.

A note on my sync stability – I think I have improved the first issue by reworking the soldering.  The second issue (auto-scanning getting stuck on AV3) still happens but isn’t really a big issue.

[Fluffyredlobster]

Bit of an odd one, not sure if anyone has any ideas.

I’ve done the hardware mod and have good continuity between pin 25 of U1 and pin 46 of U2, via the R35 pad (resistor removed).  Firmware flashed to 1.09 and I can get sync on a number of sources, but it seems less stable than than the 0.x firmware and there is some weirdness when auto-scanning inputs for sync.

When I have a source powered on and connected to AV1 (PAL Amiga 600 in this case) it locks to RGBS @ 15.62kHz but every so often it looses sync and the LCD flashes to 254.86kHz(!).  Here’s a video of it: https://www.icloud.com/photos/#/icloudlinks/076GlmCk42d0QExiG-kzXNqRQ/0/

When auto-scanning all inputs after the test pattern, if no input is connected it gets as far as AV3 RGsB, the LCD flashes up an input frequency then the auto-scan gets “stuck” on the AV3 inputs – it doesn’t loop back to AV1.  Each time it loops round to AV3 RGsB it flashes up a frequency momentarily, usually either 11kHz or 21kHz.  Video: https://www.icloud.com/photos/#/icloudlinks/062olIDHPf5zEEsFDn_sG9KKQ/0/

It’s a Kaico 1.6 (I know, I know…. they were in stock when I bought it in 2019) so I’m not sure if that maybe a factor.  Firmware 0.90 is rock solid.  If anyone has any ideas I’d appreciate it!

 

@TigerMan8285 – you need a 330 ohm resistor in 0603 size – you can get them from any electronics site / store.

[Fluffyredlobster]

Ah 🙂

Try again now, I’ve made it public.

[Fluffyredlobster]

For those asking about editing profiles for v1.x, I updated paulb_nl’s code from http://pbnl.byethost7.com/ossc/profiles/ for my own use as I was very reliant on having named profiles.  I’ve uploaded my changes to github: https://github.com/FluffyRedLobster/ossc-online-profile-editor

Be aware I am not an expert on OSSC firmware – my changes were the result of a lot of trial and error, and testing.  That said, profile editing is working great for me on 1.07.  YMMV and use at your own risk!  Last note – I haven’t hosted this code anywhere other than my own local webserver so if you want to use it you’ll need to host it somewhere.

Happy to take any feedback or bug reports.

[Author]

Posts