Differences

This shows you the differences between two versions of the page.

--- docs:vidcap [2022/05/17 15:02] – [Y/C - S-Video] root
+++ docs:vidcap [2022/05/19 06:16] (current) – [Composite] root
@@ Line 16: / Line 16: @@
 TODO
+[[https://superuser.com/questions/1677633/simultaneous-capture-and-monitor-with-ffmpeg]]
 ==== Y/C - S-Video ====
 FIXME
@@ Line 28: / Line 29: @@
   * If your video path from source to acquisition goes through processing equipment, so that losses induced by comb filters is minimized.
 ==== RGBHV ====
-TODO
+Best solution if you don't have access to Components video, when it comes to signal accuracy.
+Capture hardware is scarce and expensive.
+  * [[http://www.micomsoft.co.jp/xcapture-1.htm|Micomsoft XCapture-1]]
+  * [[https://junkerhq.net/xrgb/index.php/XRGB-mini_FRAMEMEISTER|XRGB Framemeister]]
 ==== Component - YPbPr ====
 TODO
 The only way to get analog progressive scan content. The other peculiarity is you can transport HDTV content with it (up to 1080i/p).
+Capture cards I've found:
+  * Osprey 260e with a suitable cable. Apparently supported by Linux, according to a quick search.
+Alternatively, you can use a components to HDMI converter, then a digital acquisition card to process those signals.
 ==== MUSE - Hi-Vision ====
 Best way to deal with it is getting through a MUSE decoder, then capturing the components.
@@ Line 39: / Line 49: @@
 ===== Capture cards =====
+==== August VGB100 ====
+^ Input ^ Works? ^
+| Composite | Yes, OOB, (input=0) |
+| S-Video | Yes, black and white only on Linux (input=1) |
+| Audio | Yes, OOB |
+Remarks:
+  * ''VIDIOC_S_PARM'' ioctl natively supported.
+  * I suspect there is a signal integrity issue with this device, since I've had frequent video glitches that are unrelated to the video source (cross-tested with an Easycap DC60).
 ==== Easy Cap DC60 ====