- Cin - Cinelerra-GG Mailing Lists

Analog DV Capture
by Andrea paz 03 Jan '22

03 Jan '22

@Andrew-R @Terje Found this discussion on an Italian NewsGroup; no idea if it can be useful... > 1) How to capture on Hard Disk video-films recorded on magnetic cassette tapes "Mini Dv" without losing the date and time of the original video recording on the magnetic tape? > 2) And without losing the best quality obtainable by downloading with cable and DV sockets (with digital signals; e.g. with i.Link, IEEE.1394 standard) The two things coincide: date/time data and other information (timecode, aspect-ratio, color/BN, DV type [DV25, DV50, DVCPROHD_1080i, DVCPROHD_720p], PAL/NTSC, interlaced/progressive, audio locked/ unlocked, aperture, frame rate, etc. unlocked, aperture, gain, shutter) are contained in VAUX blocks of each frame. VAUX blocks of in each DV frame (to be exact, they could be contained in each contained in each DIF block, 12000 bytes, and each frame in PAL is composed of composed of 12 DIF blocks, 144000 bytes, but usually they are put only on the first DIF block of the frame), then downloading on PC the digital data of the digital data of the MiniDV cassette you also make a backup of the information about date/time information. Similarly for HDV (MPEG-2 Transport Stream) data stored on the MiniDV cassette: all this information is contained in packets. MiniDV cassette: all this information is contained in Private Stream A1 packages (commonly called Sony A1). > 3) And perhaps by having such data captured in the "detail-properties" of the video files that are created, as is normally the case with today's cameras, instead of seeing them cameras of today, instead of seeing them appear inside the image of the video when of the image of the video when you watch it on the monitor? This one is a tad more complicated.... While cameras enter this information once into the EXIF/XMP/ IPTC sections of the JPG/RAW[TIFF] file, for DV video this information is relative to each frame (or inserted on each frame of type I or P for HDV videos, i.e. every 3 frames), and so it is a little bit difficult to show you all the information. You could show the information of the first frame, but if, for example, a for example, a file was composed by more recordings, that information would be wrong for the recordings would be wrong for the recordings following the first one, not to mention that diaphragm/gain/shutter could change frame by frame. frame by frame. Back in the day (2010, so a bit after 2004...) I had made available a small program to extract data in text format: https://video.liberdomus.org/software/extract_dvaux.zip Just run the program from DOS prompt (or shell unix, they are also compiled for Linux/64bit): extract_dvaux.exe filedv > info.txt The "filedv" can be any file format (AVI, MOV, RAW DV) that contains DV packets (also compatible with the Canopus-DV codec): a line is written every time some parameter changes. At the end a short report is also written about how many frames/blocks have been analyzed and if the audio is "locked" or not.

2 1

offtop: wine/X under Haiku os
by Andrew Randrianasulu 01 Jan '22

01 Jan '22

Some time ago we wondered if Haiku os will run X applications. At that time answer looked like no, but now some great progress was made, so may be at least basic x11 version of CinGG will be possible. https://discuss.haiku-os.org/t/my-progress-in-porting-wine/11741

1 0

Blur plugin: Alpha determines radius
by Igor BEGHETTO 31 Dec '21

31 Dec '21

Hi! In Blur plugin there is the "Alpha determines radius" option. I think it doesn't work but I can wrong. Can someone explain to me how it works, please? Thanks! IgorBeg

4 32

our ffv1.mkv profile
by Andrew Randrianasulu 29 Dec '21

29 Dec '21

seems to miss level=3 setting $ cat bin/ffmpeg/video/ffv1.avi avi ffv1 $ cat bin/ffmpeg/video/ffv1.mkv matroska ffv1 threads=8 context=1 slices=30 $ cat bin/ffmpeg/video/ffv1.mov mov ffv1 #coder=0 context=1 g=1 level=3 threads=16 slices=16 slicecrc=1 #pass=2 $ not sure if we should modify our avi/mkv profikes or add new (may be with _v3 name) ones?

3 9

Uncompressed video to lossless compression FFV1/MKV
by Terje J. Hanssen 25 Dec '21

25 Dec '21

Background: Digital video produces vast amounts of data. Take PAL-SD material (only image, no audio), stored as YUV422 with 8-bits per component (=16-bits per pixel) and a resolution of 720x576 pixels, for example. http://download.das-werkstatt.com/pb/mthk/info/video/comparison_video_codec… * Applying no compression at all (=uncompressed <http://download.das-werkstatt.com/pb/mthk/info/video/comparison_video_codec…>) results in: * 720 x 576 x 16 bits x 25 frames ≥ 1.159 GiB/Minute * * For YUV422, 10 bpc (10+5+5 = 20 bits per pixel), this would be: * 720 x 576 x 20 bits x 25 frames ≥ 1.448 GiB/Minute So you would fit no more than 4 minutes of video on a whole 4.7 GiB DVD. Since these values are already uncomfortable (even for 422-subsampled PAL), imagine HD and beyond. Therefore, you will hardly find uncompressed video in the wild, except for temporary editing use cases. ----------- The examples below show the differences in storage space required for uncompressed, lossless and lossy video codecs: https://www.scart.be/?q=en/content/short-guide-choosing-digital-format-vide… * uncompressed (e.g., v210) 10-bit -> approx. 100GB per hour of video; * lossless compression (FFV1 and JPEG 2000) 10-bit -> approx. 45-50 GB per hour of video; * lossy compression; * MPEG 2/DV50/IMX50 (50 Mbps) -> approx. 25 GB per hour of video; * to compare with * DV (DV25) -> approx. 12 GB per hour of video; * MPEG 2 (DVD quality) -> approx. 3.6 GB per hour of video. ------------- That is, if we manage to capture 422 uncompressed video via either an internal capture card or via an external SSD recorder, there is a need for * mathematical lossless compression with typical intraframe FFV1/MKV for preservation (archive masters) * and/or possibly "visually lossless" compression to a lossy intraframe intermediate/mezzanine format I had no uncompressed test file available, but tried this guide to generate a simple video (only) file: Compressing and uncompressing a preservation master video file https://bits.ashleyblewer.com/blog/2018/11/08/compressing-and-uncompressing… ffmpeg -f lavfi -i mandelbrot=size=640x480:rate=25 -c:v v210 -t 5 uncompressed.mov and next to turn it to a FFV1/MKV lossless compressed file ffmpeg -i uncompressed.mov -map 0 -dn -c:v ffv1 -level 3 -g 1 -slicecrc 1 -slices 16 -c:a copy ffv1.mkv and if required a test to uncompress the FFV1/MKV file to uncompressed 10bit file again: ffmpeg -i ffv1.mkv -c:v v210 uncompressed-again.mov du -s * 105004 uncompressed.mov 22844 ffv1.mkv 105004 uncompressed-again.mov In this simple case the lossless compressed ffv1.mkv size is schrinked to 22% of the uncompressed.mov file. In other practical tests I read the FFV1 file size was schrinked to 1/3 to 46% of the uncompressed video. (I tested for fun to transcode a "visual lossless" compressed ProResHQ.mov file to FFV1/MKV, but that extented the file size to 180% ) I loaded the simple generated ffv1.mkv in Cinelerra, but also read about a problem in a previous thread [Cin] Single-frame step fwd/bak in viewer delayed? https://www.mail-archive.com/[email protected]/msg01799.html Is this problem solved? And will the lossless compressed (preservation) format FFV1.MKV work as a editing format, or will there be a need beside to have another intermediate format MPEG 2/DV50/IMX50 (50 Mbps) for editing? ---------- Terje J. H

2 2

Fwd: mesa | VCE encoding slow when GPU is not stressed (HD 7970M) (#1235)
by Andrew Randrianasulu 25 Dec '21

25 Dec '21

patchset probably for 4.5 git... ---------- Forwarded message ---------- From: *Ed Martin (@edman007)* <gitlab(a)gitlab.freedesktop.org> Date: Saturday, December 25, 2021 Subject: Re: mesa | VCE encoding slow when GPU is not stressed (HD 7970M) (#1235) To: randrianasulu(a)gmail.com Ed Martin <https://gitlab.freedesktop.org/edman007> commented <https://gitlab.freedesktop.org/mesa/mesa/-/issues/1235#note_1200931>: I can confirm that this FFMPeg patchset seems to solve the issue for me, it implements async calls https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=5148 — View it on GitLab <https://gitlab.freedesktop.org/mesa/mesa/-/issues/1235#note_1200931>. You're receiving this email because of your account on gitlab.freedesktop.org. If you'd like to receive fewer emails, you can unsubscribe <https://gitlab.freedesktop.org/-/sent_notifications/ffa648dea16b62e78f3a3ca…> from this thread or adjust your notification settings.

1 0

Fwd: mesa | VAAPI H.264 encoding is slow on Polaris vs. HEVC and Windows AMF (#3540)
by Andrew Randrianasulu 25 Dec '21

25 Dec '21

if you have similar card and experience slow h264 encoding... also see next mail for ffmoeg patch serues (not sure if Cingg can benefit from ffmpeg patches...) ---------- Forwarded message ---------- From: *Nicholas Rush (@NicholasRush)* <gitlab(a)gitlab.freedesktop.org> Date: Saturday, December 25, 2021 Subject: Re: mesa | VAAPI H.264 encoding is slow on Polaris vs. HEVC and Windows AMF (#3540) To: randrianasulu(a)gmail.com Nicholas Rush <https://gitlab.freedesktop.org/NicholasRush> commented on a discussion <https://gitlab.freedesktop.org/mesa/mesa/-/issues/3540#note_1201025>: Wow, everything works as intended now, thank you! 1080p60 now works(tested in obs with 10,000 bitrate) on rx580. I have applied patch to mesa-git AUR package. This is how i made it: 1. yay -S mesa-git --editmenu 2. Edit pkgbuild: add patch --directory=mesa --forward --strip=1 --input="[PATH TO THIS PATCH]" to the end of prepare() func 3. Compile — View it on GitLab <https://gitlab.freedesktop.org/mesa/mesa/-/issues/3540#note_1201025>. You're receiving this email because of your account on gitlab.freedesktop.org. If you'd like to receive fewer emails, you can unsubscribe <https://gitlab.freedesktop.org/-/sent_notifications/ece8eb507e8e86693b7874b…> from this thread or adjust your notification settings.

1 0

Three PCIe capture cards with analog video capabilities and Linux support
by Terje J. Hanssen 24 Dec '21

24 Dec '21

Just my quick preview evaluation and ranking - not every detail has been found or verified .... 1) Blackmagic Design Intensity Pro 4K 10 bit color precision, 4:2:2 subsampling , SD analog and HDMI input, prop-driver, "best priced" https://www.blackmagicdesign.com/no/products/intensitypro4k https://www.blackmagicdesign.com/no/products/intensitypro4k/techspecs/W-INT… https://blog.za3k.com/capturing-video-on-debian-linux-with-the-blackmagic-i… 2) AVerMedia CL311-M2 8 bit color precision, 4:2:2 subsampling , SD analog and HDMI input, v4L2, medium priced https://www.avermedia.com/professional/product/cl311_m2/overview https://www.avermedia.com/professional/product/cl311_m2/spec https://www.avermedia.com/professional/download/cl311_m2#ans_part 3) Osprey 260e 10 bit? color precision, 4:2:2 subsampling , SD analog input only, v4L2, high priced https://www.ospreyvideo.com/analog https://docs.google.com/viewer?url=https%3A%2F%2Fdf44571b-9d7f-4226-9ca4-72… https://www.kernellabs.com/blog/?p=1801

4 4

Re: [Cin] decklink/blackmagic licence, driver?
by Andrew Randrianasulu 22 Dec '21

22 Dec '21

On Sunday, December 19, 2021, Andrew Randrianasulu <randrianasulu(a)gmail.com> wrote: > It seems there is some uncertanity about what users/distributors can do > with sdk required for working with their hardware? > > https://patchwork.ffmpeg.org/project/ffmpeg/patch/ > 201704010120.37843.cehoyos(a)ag.or.at/#10354 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839941 > > {this is related to HD capture hw we discuss with Terje} > > Should someone explicitly mail blackmagic's support about this? > found some more links https://hackweek.opensuse.org/20/projects/write-an-open-source-driver-for-t… {but was it even started? cc originator} https://inogeni.com/product/converters-comparison-table-7/ claims to support Linux (but usb3)

3 4

another patch series
by Andrew Randrianasulu 22 Dec '21

22 Dec '21

basically my lpcm + truehd ffmpeg patches, autoreconf for thirdoarty libs, fix for thirdparty/Makefile, less build in openexr, ah and filegif crash fix

3 17