- Cin - Cinelerra-GG Mailing Lists

Domesday Duplicator
by Andrew Randrianasulu 11 Feb '23

11 Feb '23

I think this detailed description reflect nicely how high-speed non-uvc data capture work https://github.com/simoninns/DomesdayDuplicator/wiki/Hardware-Guide for better or worse you can't just connect usual analog output to it. Somewhat related: https://www.windytan.com/2019/08/capturing-pal-video-with-sdr-and-few.html?… (no code). older fx2 experiments, there by now seems to be whole library of programs for those older devices in digital instrumentation sector http://www.triplespark.net/elec/periph/USB-FX2/ Some documentation on earlier sgi board called Sirius, you can see board was 10-bit internally but small font around analog inputs said they are 8bit really! http://www.sgistuff.net/hardware/video/documents/007-2238-003-siriusvideo.p…

4 3

10-bit 422 Video capture not part of the UVC spec?
by Terje J. Hanssen 11 Feb '23

11 Feb '23

We have some threads this month discussing the performance of UVC HDMI-USB3 Vide Capture stics/dongles or devices. If technical specs are available, sadly often deficient, they may manage 422 chroma subsampling, but limited to 8-bit "Deep color" (4KVC00) or "YUY2" (ms2130) 1. To repeate the illustrative article 8-Bit vs 10-Bit Video Color Explained (millions/banding vs billion shades): https://fujifilm-x.com/en-us/series/the-filmmakers-handbook/8-bit-or-10-bit… 2. In a couple of learn.microsoft articles, 10- and 16-bit YUV Video Formats are recommended for capturing, processing, and displaying video, while 8-bit YUV color formats that are recommended for video rendering. To extract and learn the most relevant YUV formats in this context from the table https://learn.microsoft.com/en-us/windows/win32/medfound/10-bit-and-16-bit-… YUY2 4:2:2 Packed 8 bits pr channel Y210 4:2:2 Packed 10 NV12 4:2:0 Planar 8 P010 4:2:0 Planar 10 3. So I found an interesting discussion on the Digital Photography Review forum: Cheapest (and decent) way to record 10 bits HDMI on Windows? https://www.dpreview.com/forums/thread/4562209 Extract here an interesting section from the first reply of Mar 19, 2021: It almost looks like 10-bit may not be part of the UVC specs unless the device does hardware H.264 or HEVC decoding, there are no 10-bit color formats that appear in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drive… such as p010, and I would expect that if the UVC spec supported p010 video it would have appeared in the Linux kernel by now. If someone can confirm this is the case also today, we don't need to search for cheap or inexpensive HDMI-USB3 Video capture stick/dongles with 10-bit 422 output support. Down In the same thread also some high-priced UVC compliant devices are mentioned, but they tend to support 10-bit on HDMI input and so downscale it to 8-bit on USB3 output.

2 4

Re: [Cin] 10-bit 422 Video capture not part of the UVC spec?
by Andrew Randrianasulu 10 Feb '23

10 Feb '23

пт, 10 февр. 2023 г., 13:12 Laurent Pinchart < laurent.pinchart(a)ideasonboard.com>: > Hello Andrew, > > (CC'ing the linux-media mailing list, as the discussion you've forwarded > already occured on a public list I assume that's not an issue) > sure. (adding our list + Terje who actually look for card or other way to input analog video with max. quality) > пт, 10 февр. 2023 г., 06:03, Andrew Randrianasulu: > > пт, 10 февр. 2023 г., 04:37 Terje J. Hanssen via Cin < > cin(a)lists.cinelerra-gg.org>: > > > > > We have some threads this month discussing the performance of UVC > > > HDMI-USB3 Vide Capture stics/dongles or devices. > > > If technical specs are available, sadly often deficient, they may > manage > > > 422 chroma subsampling, but limited to 8-bit "Deep color" (4KVC00) or > > > "YUY2" (ms2130) > > > > > > 1. To repeate the illustrative article 8-Bit vs 10-Bit Video Color > > > Explained (millions/banding vs billion shades): > > > > > > > https://fujifilm-x.com/en-us/series/the-filmmakers-handbook/8-bit-or-10-bit… > > > > > > > > > 2. In a couple of learn.microsoft articles, 10- and 16-bit YUV Video > > > Formats are recommended for capturing, processing, and displaying > video, > > > while 8-bit YUV color formats that are recommended for video > rendering. To > > > extract and learn the most relevant YUV formats in this context from > the > > > table > > > > > > > https://learn.microsoft.com/en-us/windows/win32/medfound/10-bit-and-16-bit-… > > > > > > YUY2 4:2:2 Packed 8 bits pr channel > > > Y210 4:2:2 Packed 10 > > > NV12 4:2:0 Planar 8 > > > P010 4:2:0 Planar 10 > > > > > > 3. So I found an interesting discussion on the Digital Photography > Review > > > forum: > > > Cheapest (and decent) way to record 10 bits HDMI on Windows? > > > https://www.dpreview.com/forums/thread/4562209 > > > > > > Extract here an interesting section from the first reply of Mar 19, > 2021: > > > > > > It almost looks like 10-bit may not be part of the UVC specs unless the > > > device does hardware H.264 or HEVC decoding, there are no 10-bit color > > > formats that appear in > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drive… > > > such as p010, and I would expect that if the UVC spec supported p010 > video > > > it would have appeared in the Linux kernel by now. > > > > Isn't such question more for Maintainer? > > > > "USB VIDEO CLASS > > > > M: Laurent Pinchart <laurent.pinchart(a)ideasonboard.com> > > L: linux-media(a)vger.kernel.org > > S: Maintained > > W: http://www.ideasonboard.org/uvc/ > > T: git git://linuxtv.org/media_tree.git > > F: drivers/media/usb/uvc/ > > F: include/uapi/linux/uvcvideo.h > > > > " > > > > from > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/MAINT… > > > > I looked at (hopefully) uvc spec, but mostly for interlace info > > > > > https://www.spinelelectronics.com/pdf/UVC%25201.5%2520Class%2520specificati… > > > > I'll look for guid info some more.. > > The UVC specification standardizes very few pixel formats, but allows > for devices to expose additional frame-based formats. In practice > devices use the same GUIDs as Windows in that case, and the uvcvideo > driver supports many of those already. See include/media/v4l2-uvc.h in > the latest mainline kernel for a list. This could easily be extended > with 10-bit YUV formats. > I think I found other reference to similar problem https://lists.cinelerra-gg.org/pipermail/cin/2023-February/006312.html thing is, I personally do not have any fancy card, so I personally can't test this specific aspect. But thanks for answer, if we ever put our collective hands on some strange usb device we surely will try to make it work (in 10 bit, if hw support this) as outlined in 2019 thread. I think cheap sticks based on ms2109/2130 can't do 10-bit at usb end ... > > > If someone can confirm this is the case also today, we don't need to > search > > > for cheap or inexpensive HDMI-USB3 Video capture stick/dongles with > 10-bit > > > 422 output support. > > > Down In the same thread also some high-priced UVC compliant devices are > > > mentioned, but they tend to support 10-bit on HDMI input and so > downscale > > > it to 8-bit on USB3 output. > > > > Apparently hacked Cx driver can output 16 bits as ADC, but then we have > > question of feeding it with good enough signal (vhs-decode just vampires > > into VCR guts.) > > > > Is any real external vhs (ish) sources worth 10 bits path? > > > > https://github.com/happycube/cxadc-linux3 > > > > === > > > > cxadc is an alternative Linux driver for the Conexant CX2388x series of > > video decoder/encoder chips used on many PCI TV tuner and capture cards. > > > > *Note!* cx23885 and cx23888 are incompatible chips. > > > > The new driver configures the CX2388x to capture in its raw output mode > in > > 8-bit or 16-bit unsigned samples from the video input ports, allowing > these > > cards to be used as a low-cost 28-54Mhz 10bit ADC for SDR and similar > > applications. > > > > ==== > > > > vhs-decode wiki has some ffmpeg command encoding raw captures into > prores > > 10bit file > > > > https://github.com/oyvindln/vhs-decode > > > > === > > > > VHS-Decode produces two timebase corrected 16-bit GREY16 headerless files > > separated into chroma/luma composite video signals in the .tbc format > > alongside .json and .log files, usable with the LD-Decode family of tools > > ld-analyse, ld-process-vbi, ld-process-vits and ld-dropout-correct. > > > > The gen chroma scrips will use decoded .tbc files and generate standard > > video files by default a lossless, interlaced top field first and > > high-bitrate (roughly 70-100 Mb/s) FFV1 codec video which, which although > > ideal for archival and further processing. > > > > > > For editing due to lack of support of FFV1 and sharing online without > > de-interlacing is not supported properly, as such the two commands are > > provided below to make suitable files for this use. > > > > Both commands will automatically use the last file generated as the > input. > > > > For editors this transcodes an FFV1/V210 output to a "*near complient*" > > interlaced ProRes HQ file: > > > > ffmpeg -hide_banner -i "$1.mkv" -vf setfield=tff -flags +ilme+ildct > > -c:v prores -profile:v 3 -vendor apl0 -bits_per_mb 8000 -quant_mat hq > > -mbs_per_slice 8 -pixel_format yuv422p10lep -color_range tv > > -color_primaries bt709 -color_trc bt709 -colorspace bt709 -c:a s24le > > -vf setdar=4/3,setfield=tff "$1_ProResHQ.mov" > > > > For basic online sharing you can use this command to convert the FFV1 > > output to a de-interlaced lossy upscaled MP4: > > > > ffmpeg -hide_banner -i "$1.mkv" -vf > > scale=in_color_matrix=bt601:out_color_matrix=bt709:1440x1080,bwdif=1:0:0 > > -c:v libx264 -preset veryslow -b:v 15M -maxrate 15M -bufsize 8M > > -pixel_format yuv420p -color_primaries bt709 -color_trc bt709 > > -colorspace bt709 -aspect 4:3 -c:a libopus -b:a 192k -strict -2 > > -movflags +faststart -y "$1_1440x1080_lossy.mp4" > > > > ==== > > > > Maaay be we still can use pci-e capture card with normal inputs, just > > process raw captures to see if there any difference between 8 and 10 bit? > > -- > Regards, > > Laurent Pinchart >

1 0

Fwd: [oyvindln/vhs-decode] Readme.md need more editing? (Issue #73)
by Andrew Randrianasulu 10 Feb '23

10 Feb '23

---------- Forwarded message --------- От: Harry Munday <notifications(a)github.com> Date: пт, 10 февр. 2023 г., 06:58 Subject: Re: [oyvindln/vhs-decode] Readme.md need more editing? (Issue #73) To: oyvindln/vhs-decode <vhs-decode(a)noreply.github.com> Cc: Andrew Randrianasulu <randrianasulu(a)gmail.com>, Mention < mention(a)noreply.github.com> @Randrianasulu <https://github.com/Randrianasulu> For analogue tapes, FM RF capture and software decoding is the best way to go for correction and preservation. For CVBS sources you can use CVBS-Decode <https://github.com/oyvindln/vhs-decode/wiki/CVBS-Composite-Decode> but it's not going to give anywhere near the results of VHS-Decode this is only ideal for live sources like cameras or digital formats, or analogue ones that have already been through a hardware TBC of some forum (so the whole point of the powerful software TBC in vhs-decode is lost) FFV1 is *not supported by Avid Pro Tools/DaVinchi Resolve/Adobe Suite/Final Cut* hence why it's pretty much disregarded for editing and re-muxing to V210/ProRes HQ (and setting the CLAP/Colr Atom data in amcdx-video-patcher properly after the fact) it meant more so for tossing into StaxRip etc and using a deinterlacer like QTGMC on then tossing into an NLE directly. The issue is also the output from the gen_chroma_vid.sh script is not flagged for interlacing properly this is a limit of FFmpeg but re-muxing fixes this issue. (It is supported in Lossless Cut but at potato render quality.) The wiki is pretty extensive but post-processing docs are being worked on. — Reply to this email directly, view it on GitHub <https://github.com/oyvindln/vhs-decode/issues/73#issuecomment-1425140053>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJSS7TIUWNUQMTH7MABF5D3WW…> . You are receiving this because you were mentioned.Message ID: <oyvindln/vhs-decode/issues/73/1425140053(a)github.com>

1 0

p010 vs all
by Andrew Randrianasulu 10 Feb '23

10 Feb '23

So I found another email thread - sadly it seems patch for even just 10 bit 4:2:0 subsampled signal was not merged yet? but at least we know capture device name .... https://www.mail-archive.com/[email protected]/msg142506.html Avermedia Live Gamer ULTRA GC553 Someone also apparently was able to send 10bit data as as greyscale planes, just assembling them back was not easy! https://stackoverflow.com/questions/71500311/how-to-process-a-raw-10-bit-vi… usb videoclass stuff https://www.usb.org/document-library/video-class-v15-document-set I looked at uncompressed ... it confusing a bit, apparently vendors can augment it?

1 0

also on ffmpeg capture
by Andrew Randrianasulu 08 Feb '23

08 Feb '23

may be try yuyv422 ? https://trac.ffmpeg.org/ticket/1387

1 0

possible fix for BT 631
by Andrew Randrianasulu 08 Feb '23

08 Feb '23

on termux to clip from viewer -> then OpenEDL on popup menu on resulted clip result in normally viewable on timeline edit. please test this instead of sigfpe patch

2 1

aw, we apparently missed more honest capture device
by Andrew Randrianasulu 08 Feb '23

08 Feb '23

https://www.amazon.com/gp/aw/d/B08MPPKZ55/ref=cm_cr_srp_mb_bdcrb_top?ie=UTF8 ‎4KVC00 from "V AV access" in reviews ==== A true YUY2, USB 3.0 capture card capable of 1080p 60fps! Reviewed in the United States on June 7, 2021 For the price, this thing is awesome. It's actually USB 3.0 (instead of just a fake blue connector) and is capable of delivering raw 1080p60 video for capture! I've been looking around for a good 1080p60 capture card for my Nintendo Switch, and this fits the bill quite nicely, as the loop-out keeps the gaming 'competitive' while the capture looks great. Pros: - Really captures at 1080p 60fps, and delivers sharp images (instead of blurrier 30fps ones you'll find on cheap USB 2.0 MJPEG-based capture cards). YUY2 (the video format) is chroma subsampled though, which means that really small text may have a bit of discoloration, but for games it's not really an issue. - Low latency capture (at least from what I can tell in OBS preview) - Loop out (yay) - Works with Linux as a simple V4L2 capture device - Sound is nicely in sync - Price (I got it for like ~$40 or so, and haven't found anything this good at this price point - heck, it outclasses my AverMedia Live Gamer Mini I bought used at $60) ==== aja and other stuff cost ... *much* more. https://www.aja.com/products/u-tap-hdmi 439$ https://www.amx.com/en/products/uvc1-4k even costlier, 800+! Anyway, in all cases cable (usb) might be limiting factor, too? I really hope this HAMA device actually just was plugged in wrong port or via wrong cable, otherwise I think it will be wise to replace it with something else (sadly cheap-end devices may change their guts without changing appearance, so ...russian roulette!)

2 3

Another pretty interesting bug: referenced EDL is actually mono
by Stefan de Konink 08 Feb '23

08 Feb '23

What about this one. 1. Create a project where you put in a nice stereo audio track 2. Put it on the time line. 3. Save the project "stereo track" 4. Create new project (obviously stereo) 5. Load the project "stereotrack" as "Reference EDL" 6. Drag it into the timeline 7. Play; notice that is actually mono audio on two stereo tracks. -- Stefan

3 4

gnu debuglink
by Andrew Randrianasulu 04 Feb '23

04 Feb '23

According to https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html you should add another objcopy command objcopy --add-gnu-debuglink=foo.debug foo for debuglink method. While it also says some versions of strip command also can do this part automatically I think we can try first method just for seeing now it works (I suspect fedora debug packages not showing all info actually related to this missing command). build-tested on termux only.

1 0