Does anyone have a list of capture cards that support 240p?

[Calle W]

I just ran some tests on different drivers for the SC-512, including the latest one. All drivers except the very first one (108), pick up 240p as 1440x240. When using the latest drivers, it picks up 240p as 720x480i. When set to component input (still using RGB), I can get it to pick the signal up as 1440x240. Under SIGNAL COLORIMETRY it says BT709 when set to component input and BT601 when set to VGA. As far as I know this is the only driver that displays this information. 1440x240 displays as 720x240, but I think it messes stuff up. Could it be the reason for the color space issue? It would be nice to be able to manually pick BT601 for these sources.

Almost all drivers let you set exact framerates (such as 60.10 for the SNES). Unfortunately, if you want to use Amarec live, you need to set the framerate to 59.94 to make sure the output framerate is smooth. The 108 driver can't capture anything except standard framerates (59.94, 29.97 etc.). Also, you can't use the composite/S-video input (or audio) with these drivers if you're using the SC-512. The SNES displays very noticeable jailbars with this card. This is fixable by turning the sharpness to max. However, this doesn't work with if you're using the 108 driver. None of the settings change anything.

I'm currently using the 108 driver, since it does have a bit sharper picture quality and doesn't have any issues with color spaces. None of the drivers fix the Pr delay, so I'm guessing it's hardware related. I currently capture audio via a USB mixer, and it works really well. The jailbars that are present on the SNES really bothers me though, so I can't wait to get a hold of an OSSC. Hopefully the SC-512 accepts the signal from it without any major issues. It should let me upgrade to newer drivers.

The USB3HDCAP (and XCAPTURE-1) apparently does not have issues with Pr delay or color space, so it's definitely an attractive option. I'd love to try the Magewell AIO/DVI, but we'll see when that happens.

[NJRoadfan]

I can confirm the DVI2PCIe card can do 240p and 288p. The card's driver needs custom modes added though, otherwise the card will detect the signals as interlaced as the default modes are all standard VESA resultions. Getting 1:1 pixel mapping should be possible on this card too, as it allows EXTENSIVE tweaking of the incoming video signal (including phase and PLL). Both horizontal and vertical (up to 85hz) video timings can be configured along with front/back porch. Mode switching is supported with re-scaling, although the card does take a second or two to re-sync. Oh, and it supports full RGB capture too, no need to worry about YUV conversion.

[FinalBaton]

Following the discussion we had on this topic I'm indeed as well interressed to know if there's a way to have 4:2:2 encoding properly handled by Youtube. If the USB3HDCAP produce better results than the Elgato on this matter maybe it would be a way to solve my scanline issue.

Just saw this post, sorry for being late.

But if you want to check how Youtube handles a 4:2:2 vid captured by the USB3HDCAP, here's an example :
https://www.youtube.com/watch?v=ET5mINgvDZs

[Fudoh]

But if you want to check how Youtube handles a 4:2:2 vid captured by the USB3HDCAP, here's an example :

as in "they don't" ? 4:2:2 uploads get converted to 4:2:0, don't they ?

[Pasky]

Yes, Youtube resamples the video at 4:2:0 unfortunately.

[FinalBaton]

But if you want to check how Youtube handles a 4:2:2 vid captured by the USB3HDCAP, here's an example :

as in "they don't" ? 4:2:2 uploads get converted to 4:2:0, don't they ?

"handles" is the key word in my post. It means "treats". as in "converts to 4:2:0".

Of course I know this. It was discussed on the previous page, where I took part of the discussion. Why wouldn't I know this?

The poster I quoted wanted to know how 4:2:2 videos captured from the USB3HDCAP looked on Youtube (where they are OBVIOUSLY resampled to 4:2:0), versus how a 4:2:2 vid captured by his own card look once uploaded on YT.

[Fudoh]

I might have phrased that poorly - my apologies.