SirRockALot
Forum Replies Created
-
AuthorPosts
-
I think that would be neat. Is there some more detailed information on what the smoothing in the RetroTink actually does?
Most filters for pixel art games don’t do much for me, but early 240p/480i 3D games might benefit from this smoothing options or even post-process AA type processing like in the mCable.
February 24, 2019 at 12:36 PM in reply to: Option to auto select YPbPr color space based on detected resolution #25381Yeah, just like selecting the LPF, there should be an Auto option. I think it would also be useful for somebody to actually check what color space those games on the in-between SD/ED/HDTV YPbPr consoles (xbox & ps2) actually use. Like, run a game like GT4 & Soul Calibur 2 in 480i, 480p, 720p, 1080i etc. and check what color space setting is required for those games to output the right colors in all those resolutions.
Or, instead of doing all of that, just press the Undo button 🙂 It’s a convenience, not a necessity.
Looking at the IT6613 HDMI transmitter chip (http://www.ite.com.tw/en/product/view?mid=27) used in the OSSC, it apparently has a S/PDIF input port, quote: “In addition, an S/PDIF input port takes in compressed audio of up to 192kHz frame rate”. For the laymen that sounds like the chip would be capable of just muxing any normal digital audio format into the HDMI output. Does this mean the OSSC could have a digital audio in for the price of the input jack and maybe a few jellybean parts? I guess that wouldn’t help with older consoles that have non-standard sample rates and don’t do ‘compressed’ audio, but at least the usual suspects could be routed this way. Might make for an interesting add-on board / mod project 🙂
+1 in any case
Oh, neat. Guess that avoids the issue entirely. Thanks!
Unfortunate that so many displays seem to have an issue with handling this automatically. My old TV did it just fine. I can only assume that some popular device specified the format wrong and display manufacturers started ignoring it.
Maybe marqs should add password saves to the OSSC 😉
I think this is something that could be improved in future OSSC revisions.
Of course, the SCART spec and the OSSC documentation is clear on what type of sync signal is expected. And that’s all good and fair – if you i.e. fry your device with a 9V DC center-positive labelled power jack by hooking up a 12V DC supply, your fault.
But I’d argue that the sync level issue is more insidious than that. Some cables have the resistor in the SCART head, some in the DIN plug. Some consoles output video level sync and don’t need a resistor. Some RGB mods and RGB output devices have a jumper to switch between the two levels. Sync strippers can also change the situation. Many makers of cables, RGB mods & superguns have apparently gotten this wrong over the years. A 10$ radio shack meter can’t tell you the amplitude of a sync pulse. If you get it wrong, at first nothing might happen. Picture looks fine, but a year later some switch, TV or scaler is damaged.
My point is that making sure your sync signal has the correct magnitude is not easy for the average retro gamer. You either need complete knowledge and understanding of the video signal chain in your console, RGB mod & cable or you need to own & be able to operate a scope to be sure you’re not outputting the wrong levels.
I think adding tolerance, or even better reporting, for TTL-level sync signals would be valuable.
The Xbox has full support (including in-game) for Dolby Digital 5.1, so analog stereo is quite the downgrade. But for like 2-3 bucks you can get a little interposer adapter with an optical out. And then you didn’t really need the 5-wire 360 cable in the first place.
Yeah, I’d never feel comfortable with that hot glue mess sitting behind my console. What’s the point of soldering the 360 cable to the Xbox connector, though? Especially if you’re just going to wire it up for stereo. To me it would make much more sense to simply use the original composite + L/R cable for YPbPr and then buy one of those 2.50$ pass-through adapters with an optical out.
I was curious and did some reading, apparently a softmodded Xbox can output RGsB and with a small cable mod you can output YPbPr over SCART. The OSSC should support both. Might be good alternative to component then.
At the very least I can understand worrying about it. ~50% of my gaming diet is in 4:3 and I really wonder if after a year or two this means the center of the screen will be noticeably dimmer as the sides. Or imagine one always uses the same scanline settings. Guess after a while you have scanlines on everything 😉
Current OLED tech still suffers from permanent burn-in.
https://www.rtings.com/tv/learn/permanent-image-retention-burn-in-lcd-oled
Test shows how good iPhone X’s OLED screen is at preventing burn-inNever understood why they don’t do it. They figured out the hard part, the proprietary plug on the console side. I assume most people would want to connect their Xbox over component, so why offer a SCART RGB cable but not a component one…
That makes about as much sense as running into the shade for two seconds every hour to prevent sunburn…
My experience with PS2/Xbox component cables of the no-name variety on eBay/Amazon has been universally bad. Official 1st party cables or the ones from Monster are a safe bet. They’ll be quite expensive, though. For some reason RGC / RCA does not make component cables for PS2/Xbox. I guess the HD Retrovision guys might consider making one for Xbox once their PS2 component cables are out.
-
AuthorPosts