July 24, 2019 at 5:47 AM #27124James-FParticipant
I do not agree with the above.
Using the recommended HDMI to Component conversion box results in an excellent picture through the OSSC.
You have to make sure you are using DVI mode on the RT2x since the Component conversion box will output limited range if the RT2x is in HDMI mode, and you want full range when pairing with the OSSC.July 24, 2019 at 6:41 PM #27137nmalinoskiParticipant
Hold the 2X/Filter button while connecting usb power to enable DVI mode, release after 2 led flashes.
Note that in DVI mode there is no audio output, and will output RGB Full Range (0-255).
HDMI default now is YCbCr 4:4:4 Limited Range (16-235) which is the default for video content, and TVs have better support for that mode,, was RGB Full before this firmware update.
I’m not sure I fully understand these two bits. First, after enabling DVI mode, does that change survive reboots, or do you need to hold 2X/Filter when applying power every time? If that setting doesn’t survive reboots, then I can see this being a problem for those who want to integrate an RT2X into a larger setup who also have a need for DVI mode.
Secondly, what is meant by “HDMI default“? Is it possible to switch between multiple combinations of RGB/YCbCr and Full/Limited ranges, and, if so, how? Is it automatic? And do these settings also survive reboots?
I’d like to see another board revision with something like a DIP switch bank for those who prefer to set it and forget it. I would leave the input and mode toggles as-is (and make sure that those configurations survive reboots), and then move all of the weird, I-feel-like-I’m-resetting-my-router’s-NVRAM, power-on button holding to the switch bank, like the HDMI/DVI toggle, and the RGB/YCbCr and full/limited range stuff if that’s actually applicable.July 24, 2019 at 7:10 PM #27138James-FParticipant
RetroTink 2x designed to work with TVs, therefor HDMI YCbCr limiter range is the default like most BluRay players or Set-Top boxes.
HDMI 1.0 standard mandates to accept this type of signal, and it is supported by 100% of TVs with HDMI inputs.
DVI mode is for compatibility with older monitors (PC) which don’t accept HDMI at all or will not even turn on with HDMI signal, hence it is not saved after power off.
Also, to avoid the chance of “my RT2x doesn’t output sound” reports, since DVI does not carry audio packets.
DVI is RGB only and has no Limited Rage since it is exclusively a computer standard which replaced VGA.
You can switch to DVI RGB Full Range using the method above, otherwise powering on normally is HDMI YCbCr Limited Range.
Since the OSSC expects SD analog YPbPr signal at the input with 0v being black, that’s what we are trying to provide to it.
The HDMI to Components box mentioned above will treat the 0-255 (Full Range) from the HDMI input as 0-0.7v (standard analog video range) as expected, therefor we need to provide full range for this box to output SD analog YPbPr signal that the OSSC expects.
You can of course keep the RT2x in HDMI mode, but the output will be Limited Range YPbPr which is NOT a standard SD YPbPr signal that the OSSC expects.
Actually, it’s quite lucky that this conversion box is of so high quality for such a low price.August 9, 2019 at 2:27 PM #27362
I also have the older revision board, and im very interested in this update. My retrotink 2x is just UNUSABLE with the N64 audio.
Where can i find the FIRMWARE file?
And i have another question, is it possible to add PAL-M (brazilian TV color system, wich is similar to NTSC in resolution and refresh rate) support in the future? I have many PAL-M devices that only outputs black & white when connected to the retrotink 2x.August 14, 2019 at 3:21 AM #27440
Well, i´m going to answer myself, maybe someone in the future will find this useful.
I have updated to the new 3.2 firmware (my pcb is 3.1), using the fw (for the 3.1 pcb) from this link:
The audio clipping in N64 unfortunately is NOT FIXED, at least in the 3.1 PCB.
It clips constantly with my N64. I have to plug the N64 audio directly to the TV or the receiver/soundbar to have decent audio.
Besides the new modes i didn´t see any other noticeable improvement. If someone is considering to buy the cable + pic programmer to fix audio issues, don´t even bother for the 3.1 PCB (at least in my opinion).August 14, 2019 at 1:57 PM #27445cleitonspindolaParticipant
Are you from Brazil? I have a retrotink 2x (3.1 PCB) and have problems with audio sometimes in 3DO using S-Video. Can you contact me email@example.com to talk about update.
ThanksAugust 15, 2019 at 1:48 AM #27458
Yes, i´m from Brazil. I have sent you an e-mail.
Anyway, just tested for PAL-M in the new firmware, and as expected it doesn´t work (black & white only).
Mike should def fix this, as PAL-M is just an NTSC signal with a PAL colour carrier. (ref: https://en.wikipedia.org/wiki/PAL-M).
- You must be logged in to reply to this topic.