January 2, 2019 at 7:31 PM #24559
Hi folks, just got my OSSC yesterday, I’m using it on my PS2, since I only got one monitor, I connected every console of mine (PS4, switch, OSSC) into a HDMI splitter, the hardware configuration is shown as below:
Screen: ASUS PG348Q 34″ monitor (https://www.amazon.com/PG348Q-Ultra-Wide-3440×1440-DisplayPort-Monitor/dp/B01C83BE6U)
HDMI splitter: DigiSun AH231U HDMI 2.0 3×1 Switch with Audio Extractor (https://www.amazon.com/DigiSun-AH231U-Extractor-Support-Controller/dp/B07D8MLC4Q)
Cable: Retro Gaming Cable Packapunch PS2 SCART w/ CSYNC (https://www.retrogamingcables.co.uk/packapunch-range/PlayStation-Packapunch/SONY-PLAYSTATION-PACKAPUNCH-RGB-SCART-CABLE-PRO)
Sound: Extraced from HDMI splitter and send into my USB DAC via TOSLINK.
I can sometimes see my PS2 startup screen with this configuration, but 100% no image in game, no test pattern also, only sound exists. Both PS2 and PS1 games result the same.
The HUD on the OSSC showed:
“AV1: RGBS 525i 15.73kHZ 59.94kHZ”
I changed “TX Mode” from “HDMI” to “DVI”, everything back to normal, but no sound under DVI mode, which is a pain in the butt under my configuration. If I connect the OSSC directly into my monitor, everything is fine, including test pattern, no extra config needed, but I cannot extract the audio to my DAC.
I changed three HDMI cables, the outcome was the same.
Is there any method or configuration that could fix this problem?
Thank you all and apologize for my bad English.January 3, 2019 at 1:43 AM #24564NalatrozParticipant
Yeah sounds like your HDMI Splitter is causing the issue, I run into a similar issue with the HDMI audio extractor I use for my modern consoles so I can hook my headphones up to the extractor and not my monitor 3.5mm jack(Which is just inconvenient for me being behind the monitor) .
It might not be able to handle a 480i HDMI signal. Have you tried forcing a 480p signal through GSM?January 3, 2019 at 5:30 AM #24566nmalinoskiParticipant
Just for clarification, it’s a switcher, not a splitter. A splitter would have one input to multiple cloned outputs, whereas a switcher has multiple inputs to one output.January 3, 2019 at 6:46 AM #24567
I’ve tried GSM but no luck, it still output 525i.January 3, 2019 at 11:25 AM #24578
Just to make sure, didn’t the signal already doubled by OSSC in 2x (bob) mode? Since my monitor cannot identify any interlaced signal, if I saw any, it must be de-interlaced, right?
I’m trying to trouble shoot the actual cause, just don’t understand that why the OSSC still showed 525i when the signal is doubled, and why the whole thing works when TX mode set to “DVI”.January 3, 2019 at 7:16 PM #24587nmalinoskiParticipant
The OSSC’s display describes the input signal, not the output signal; so if you’re feeding it 480i, it’s going to show 525i, regardless of your linedoubling settings.
The default setting for 480i is to line-double with bob deinterlacing, and you should probably verify that yours is set to this by going to Output opt. > 480i/576i proc in the menu and ensuring it’s set to Line2x (bob).
Here’s the manual if you haven’t already been looking at it: http://junkerhq.net/xrgb/index.php?title=OSSCJanuary 10, 2019 at 11:39 PM #24693marqsParticipant
I found a small bug in the way audio infoframe is set up. Feel free to try a test firmware with a fix for that.January 11, 2019 at 5:40 AM #24699
Cool! Give it a go right away, thanks.July 9, 2019 at 9:08 PM #26971marqsParticipant
I got the same DigiSun AH231U HDMI switch for testing, and found out that its issue is similar to some Denon AVRs as the switch relies a bit too much on HDMI metadata. When VIC is set to 0 (unknown), the switch ends up using inoptimal RX/TX configuration for most modes which leads to missing/corrupted/jittery output. With the firmware modified for Denons, test pattern and standard passthru modes work OK since they explicitly set VIC. However, other modes using VIC=0 had still issues but after forcing the default VIC to 2 (480p60), the output seemed to be fine in all modes I quickly tried. One thing I noticed though, is that the switch occasionally had issues locking after a mode switch unless “Full TX setup” was enabled in OSSC Compatibility opts.
To summarize, HDMI signal handling of this switch is not very robust. It can be made to work reliably with OSSC if another compatibility option is added that sets default VIC to a known value.
- You must be logged in to reply to this topic.