Differences

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

--- docs:vidcap [2022/05/17 12:46] – [Capture cards] root
+++ docs:vidcap [2022/05/19 06:16] (current) – [Composite] root
@@ Line 3: / Line 3: @@
 The following guide is specifically targeted to capture analog video signals.
+Checklist:
+  * Capturing Video+Audio FIXME
+  * Capturing Subtitle with VBI TODO
+  * Authoring subtitles TODO
+  * Authoring chapters TODO
+  * Lossless content encoding TODO
+  * Lossy content encoding FIXME
 ===== Video path types =====
@@ Line 8: / Line 16: @@
 TODO
+[[https://superuser.com/questions/1677633/simultaneous-capture-and-monitor-with-ffmpeg]]
 ==== Y/C - S-Video ====
-TODO
+FIXME
+Luma and Chroma are transported on distinct wire pairs.
+Recommended over Composite if your A/V equipment has no better signal to offer, especially if Digital->Analog conversion is performed onboard (e.g. LaserDisc player with digital framebuffer, D-VHS w/o Components, etc).
+It's also recommended
+  * If your capture card has a poor comb filter (your mileage may vary, make an A/B test with your specific setup). Typical artefacts of a poor comb filter is a blurry luma, and a smudged chroma, especially if you have an OSD.
+  * 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 22: / 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 ====
@@ Line 53: / Line 91: @@
 ===== Capturing video signal =====
-Checklist:
+Unless you have a decent machine, it is recommended to first save an uncompressed capture that you will process in a second time, then compress (either losslessly for mastering/archival, or lossily for final consumption).
-  * Capturing Video+Audio FIXME
+===== Authoring chapters =====
-  * Capturing Subtitle with VBI TODO
-  * Authoring subtitles TODO
-  * Authoring chapters TODO
-  * Lossless content encoding TODO
-  * Lossy content encoding FIXME
-Unless you have a decent machine, it is recommended to first save an uncompressed capture that you will process in a second time, then compress (either losslessly for mastering/archival, or lossily for final consumption).
+This can be performed using a ''ffmetadata'' file. Add the following options to insert an external metadata file:
+<code>-i example.ini -map_metadata 1</code>
+File example:
+<code ini example.ini>;FFMETADATA1
+title=bike\\shed
+;this is a comment
+artist=FFmpeg troll team
+[CHAPTER]
+TIMEBASE=1/1000
+START=0
+#chapter ends at 0:01:00
+END=60000
+title=chapter \#1
+[STREAM]
+title=multi\
+line
+</code>
+Doc for more info: [[https://ffmpeg.org/ffmpeg-formats.html#Metadata-1]]
-==== Lossy content encoding ====
+===== Lossy content encoding =====
   * Transparent, x264