[demolition]

Not that I think it matters much but you do not mention whether your TI99/A is a US or EU model, because the EU model has component output only. It is probably a sync issue and thus it will be the same with either input.

Not that it relates to the RT2x specifically, but I had my TI99/A hooked up through my OSSC (using the component inputs) and it worked great. I know that many owners of the RT2x also have an OSSC, as they supplement each other well.

[demolition]

My problem was also with a 8565R2 machine and with another 6569 based machine there is no problem so this seems to verify your findings. Regarding the quality of 6569 vs. 8565 then I think that the 8565 in general provides a sharper image which cannot be achieved with the 6569 even with a LumaFix. With the RT2x+OSSC combo, I prefer the picture from the 8569 although it only lasts for 20 secs..

[demolition]

You need to consider the quality of the scaler in your monitor. If you present the monitor with a signal that matches its native resolution then it will not need to do any scaling and you have full control over the picture quality. If you would like a softer vertical resolution then it might be good to take advantage of the monitor’s scaler since it might do some kind of bilinear resampling which the OSSC is not capable of doing.

So for 1080p displays, 4x is too much since it will generate more than 1080 lines. It is however possible to use 4x on displays with 1200 lines and then add a few black lines until you reach those 1200 lines. I have a 3x config for my Full HD TV and the above 4x config for the 1600×1200 monitor. I could use 3x on the Dell but then I’d have quite small picture with a lot of black around it since I want to have integer pixel mapping.

[demolition]

I ended up getting a pretty nice picture using these settings to achieve a 1600×1200 output mode which is native for my Dell 2001FP:

Output opt:
240p/288p proc Line4x
Line4x mode Generic 4:3

Sampling opt -> adv. timing (1280×288):
H. samplerate 1620
H. synclen 10
H. backporch 10
H. active 1600
V. synclen 1
V. backporch 10
V. active 300

I see a very slight horizontal tremor but otherwise it looks almost perfect. It is also great for my VIC20 which has been modified with S-Video output.

I have tried using the 320×240 opt. mode however it did not have any impact on the horizontal tremor and it did not produce a better image than Generic 4:3. That being said, the tremor is not really an issue since it is only noticeable if you move up close to the monitor and look for it.

[demolition]

Hooray, I learned something new today – I wanted to change the adv. timing menu, but was confused which mode I was supposed to select since there was no ‘312p’ mode to choose from. What I have now learned is that it starts on the currently active mode so you should not go left/right if you want to tune the current mode. 🙂

So in this case, it started on the 1280×288 mode and now I am able to fine tune it.

I have managed to set up a 1600×1200 output mode which is native for the 20″ monitor I am using and the image quality is really nice now. Apart from a very slight horiz judder, I see no noise and the colors and sharpness is close to perfect, so I am very happy indeed. This is with a standard PAL C64 with Lumafix as my C64 Reloaded exhibits some high frequency noise that I cannot seem to get rid of (I assume it is SMPS noise from its converters).

[demolition]

Where do you change the H.Samplerate for 4:3 generic mode?

[demolition]

From the data sheet:

All ADV728x devices (MIPI CSI-2 or TTL output models) output video data in YCbCr 4:2:2 format.
The video timing is compliant with the ITU-R BT.656-3 or ITU-R BT.656-4 standards.

[demolition]

At first, I was using my C64 Reloaded but found that using a regular C64 with a lumafix produced a much nicer picture (although it could still use some fine tuning). I think the SMPS on the Reloaded board generates some interference with the output video signal.

For some reason, both with the Reloaded and the regular C64, I see that the picture is pretty stable for the first 30-60s and then suddenly it starts to judder as if the phase shifts a bit. If I reset the RetroTINK by using one of the buttons on it (or power cycle the C64), it is again stable for another short while. This is not related to the OSSC since I get the same noise when I hook my TV directly to the RetroTINK output.

So which menu did you use to change the adv. timing of the C64 signal? If I use the 240p menu, nothing that I change in there seem to make any difference.

[demolition]

There is hardly anything to adjust on the RT or the VGA adapter so perhaps this topic belonged more in the OSSC section. It is basically a question of whether it is possible to change how the OSSC treats the 312p signal that it gets from the C64.

To get rid of the noise I see, I at least need to be able to adjust the sampling rate of the OSSC since I can tell that it is off a bit. I will look forward to your findings next week if I haven’t figured it out until then.

[Author]

Posts