I just found your UA-cam but your video format is really good. Rarely do videos get comparisons right but I think yours do it really well. One of the best imo.
Great video! It would be interesting to see the same comparison between the encoders with RGB and YPbPr output in 480i and games that feature a lot of detail with saturated color (e.g. Tokyo at nighttime in PGR, the tachometer redline in OutRun2006, and so on.) Color clarity in 480i is the biggest weakness of the Conexant encoder because of the way it lowpass filters the output.
I have a 1.3 with a connexant encoder which when displaying interlaced content over component results in vertical lines and colour bars in the image. This particular console is a modded PAL console set to NTSC-M and only affects interlaced content (progressive looks absolutely fine). My other (1.6) xbox does not seem to suffer from this issue.
Great video! I have a 1.4 TSOP'd console, a 1.4 with an old modchip (both cerbios 2.3.1) and a few soft modded systems. They're all PAL and I have been changing them to NTSC as per the Rocky5 softmod, but wondering how you get the option of NTSC-J as they are too over bright.
Thank you! There is a PrometheOS Tool somewhere floating around, can't recall it's exact name, but it works on all systems, even if only softmodded. At least, AV settings part does! I'd go with that. :)
Great video. If I'm using a component cable on a PAL console, should I start setting it to NTSC-J instead of M? Or J is just better than M on PAL consoles for composite/S-video/SCART? Thanks.
@@PrimeRetroGamer I'm playing on an old 1080p LCD TV, with component cables, it's not the best image quality TV, but has component plugs. Most LCDs here only have HDMI and SCART. In my country I've never seen a CRT with component. All TVs in Europe (even 90s CRTs) support both PAL and NTSC, it's really rare to find a TV that only works with PAL and SECAM.
@@drPeidos If you play in 480p+ with component on that TV you should be good! Yep, that’s why I don’t even bother with PAL, I mod most of my consoles to play with NTSC modes.
Im really interested how you made the diy s-video cable. Where'd you source the parts? I have a crt with a svideo connection so thats why im interested
Funny enough, it's somewhat decent on Xbox! When you fix the black level that is.. Watched back my video with Dreamcast composite and that composite is big ooof.
@@Conoido It seems the CVBS (Composite), Y/C (S-video), and RGB examples are from 480i output where flicker filtering is blurring the picture vertically, plus they may be from the Conexant encoder where the picture is a bit soft overall, especially in saturated colors. The YPbPr (Component) example in turn seems to be from 480p output which excludes both the flicker filter and the lowpass filters used in 480i.
There’s false information that states that on 1.4 and earlier revision consoles produce an rgb signal is just re encoded pal/ntsc svideo/cvbs So it goes from ycbcr (digital) -> pal/ntsc -> rgb and only the 1.6 does a direct ycbcr (digital) -> rgb Thanks for proving that this is a load of shit.
I think that confusion comes from that when outputting 480i/576i, the Conexant video encoder specifically converts from RGB to YCbCr with 4:2:2 color subsampling internally and was set up to have a very aggressive low pass filter on the color difference signals. Going by the datasheet it didn't split the signal to go through separate filter banks for YPbPr/RGB and CVBS, meaning the low pass filtering necessary for the latter affected all signals. As a result color resolution wasn't as good as it should be, particularly visible in detail with saturated colors. It was component video, just heavily filtered. In 480p/720p/1080i, that low pass filter isn't used.
have you ever messed with the program called "Flicker F*cker"? no censor ofc. it removes the built in blur in 480i directly from the xbe, may be interesting to see.
I just found your UA-cam but your video format is really good. Rarely do videos get comparisons right but I think yours do it really well. One of the best imo.
Thank you! I’m still trying to find my footing so to say, so this kind of comment is a great encouragment.
Great video!
It would be interesting to see the same comparison between the encoders with RGB and YPbPr output in 480i and games that feature a lot of detail with saturated color (e.g. Tokyo at nighttime in PGR, the tachometer redline in OutRun2006, and so on.) Color clarity in 480i is the biggest weakness of the Conexant encoder because of the way it lowpass filters the output.
Thanks, so many questions about this back in the day. And almost as much misinformation.
Great explanation, very clear to understand. Thanks 👍
Fyi you can't lower/disable the flicker filtering on a 1.6 (xcalibur) console which blurs the image in 480i.
Excellent video.
Thank you!
I have a 1.3 with a connexant encoder which when displaying interlaced content over component results in vertical lines and colour bars in the image. This particular console is a modded PAL console set to NTSC-M and only affects interlaced content (progressive looks absolutely fine). My other (1.6) xbox does not seem to suffer from this issue.
Conexant looks a tiny bit blurrier but seems to offer nicer colors
Great video!
I have a 1.4 TSOP'd console, a 1.4 with an old modchip (both cerbios 2.3.1) and a few soft modded systems.
They're all PAL and I have been changing them to NTSC as per the Rocky5 softmod, but wondering how you get the option of NTSC-J as they are too over bright.
Thank you!
There is a PrometheOS Tool somewhere floating around, can't recall it's exact name, but it works on all systems, even if only softmodded. At least, AV settings part does! I'd go with that. :)
Great video. If I'm using a component cable on a PAL console, should I start setting it to NTSC-J instead of M? Or J is just better than M on PAL consoles for composite/S-video/SCART? Thanks.
Only better for Composite, S-Video and RGB SCART. Sadly, Component will be washed out no matter what unless you set it back to PAL.
@@PrimeRetroGamer Thanks for the answer. Do you think the Component output will look better if I flash a NTSC BIOS on my PAL console?
@@drPeidos Nope, BIOS is not region/AV mode dependent, so it won't improve anything AFAIK. On what screen are you playing, what is your setup like?
@@PrimeRetroGamer I'm playing on an old 1080p LCD TV, with component cables, it's not the best image quality TV, but has component plugs.
Most LCDs here only have HDMI and SCART.
In my country I've never seen a CRT with component.
All TVs in Europe (even 90s CRTs) support both PAL and NTSC, it's really rare to find a TV that only works with PAL and SECAM.
@@drPeidos If you play in 480p+ with component on that TV you should be good! Yep, that’s why I don’t even bother with PAL, I mod most of my consoles to play with NTSC modes.
Does the different black levels apply when using component cables at 480p.
Im really interested how you made the diy s-video cable. Where'd you source the parts? I have a crt with a svideo connection so thats why im interested
@@kendric_BUF You can buy Xbox AV plug on AliExpress and use S-Video wire from a good quality, generic S-Video cable. Rest is just some soldering.
Compos(h)ite just sucks most of the time on most consoles/etc.! 😅
Funny enough, it's somewhat decent on Xbox! When you fix the black level that is.. Watched back my video with Dreamcast composite and that composite is big ooof.
10:15 I hardly see a difference between composite and RGB
@@Conoido Increase your Video-resolution or get some glasses. It's very obvious...
I do agree that it is not a good example though.
@@Conoido It seems the CVBS (Composite), Y/C (S-video), and RGB examples are from 480i output where flicker filtering is blurring the picture vertically, plus they may be from the Conexant encoder where the picture is a bit soft overall, especially in saturated colors. The YPbPr (Component) example in turn seems to be from 480p output which excludes both the flicker filter and the lowpass filters used in 480i.
There’s false information that states that on 1.4 and earlier revision consoles produce an rgb signal is just re encoded pal/ntsc svideo/cvbs
So it goes from ycbcr (digital) -> pal/ntsc -> rgb and only the 1.6 does a direct ycbcr (digital) -> rgb
Thanks for proving that this is a load of shit.
I think that confusion comes from that when outputting 480i/576i, the Conexant video encoder specifically converts from RGB to YCbCr with 4:2:2 color subsampling internally and was set up to have a very aggressive low pass filter on the color difference signals. Going by the datasheet it didn't split the signal to go through separate filter banks for YPbPr/RGB and CVBS, meaning the low pass filtering necessary for the latter affected all signals. As a result color resolution wasn't as good as it should be, particularly visible in detail with saturated colors. It was component video, just heavily filtered.
In 480p/720p/1080i, that low pass filter isn't used.
have you ever messed with the program called "Flicker F*cker"? no censor ofc. it removes the built in blur in 480i directly from the xbe, may be interesting to see.