January 2020 - Cin - Cinelerra-GG Mailing Lists

Re: [Cin] cinelerra-gg on ppc64el
by Daniel Reurich 02 Apr '22

02 Apr '22

Hi I've made some significant progress in getting the build going - and will have some patches to drop that solve some issues for builds using system libs and non x86 based archs. The current issue I'm stumbling on is that configure doesn't detect the systems liba52 and a52dec/a52.h header files as installed. This results in a linking failure during the build of libzmpeg Any thoughts on how I might overcome that? Thanks, Daniel. -- Daniel Reurich Centurion Computer Technology (2005) Ltd. 021 797 722

3 5

Blu-ray encoding again
by Andrew Randrianasulu 16 Oct '20

16 Oct '20

Hi! With Marton's patches from git clone -b mpegts https://github.com/cus/ffmpeg/ and CinGG compiled with ffmpg.git I _nearly_ got some rendering. But option files still needed some modification For example I was running into x264 errors. cin Cinelerra Infinity - built: Nov 14 2019 14:17:05 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams (c) 2007-2019 cin5 derivative by W.P. Morrow aka goodguy Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra. Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl Device type none is not supported. Available device types: vdpau cuda vaapi opencl [libx264 @ 0xe9a3c4c0] interlace + weightp is not implemented [libx264 @ 0xe9a3c4c0] using mv_range_thread = 88 [libx264 @ 0xe9a3c4c0] NAL HRD parameters require VBV parameters [libx264 @ 0xe9a3c4c0] using SAR=1/1 [libx264 @ 0xe9a3c4c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1 [libx264 @ 0xe9a3c4c0] profile High, level 4.1 Device type none is not supported. Available device types: vdpau cuda vaapi opencl FFMPEG::encode_activate: write header failed /dev/shm//bd_20191114-163217/bd.m2ts err: Недопустимый аргумент Render::render_single: Session finished. Device type none is not supported. Available device types: vdpau cuda vaapi opencl some of them were fixed by applying parameters from http://www.x264bluray.com/home/1080i-p [libx264 @ 0xe0609640] using mv_range_thread = 88 [libx264 @ 0xe0609640] using SAR=1/1 [libx264 @ 0xe0609640] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1 [libx264 @ 0xe0609640] HRD bitrate: 40000000 bits/sec [libx264 @ 0xe0609640] CPB size: 30000000 bits [libx264 @ 0xe0609640] profile High, level 4.1 [SWR @ 0xcfba81c0] Using fltp internally between filters Device type none is not supported. Available device types: vdpau cuda vaapi opencl Render::render_single: Session finished. but there still warning at ffmpeg site about deprecation of x264opts: https://trac.ffmpeg.org/wiki/Encode/H.264 Warning: Do not use the option x264opts, as it will eventually be removed. Use x264-params instead. --- /usr/share/cin/ffmpeg/video/bluray.m2ts 417/417 100% bluray libx264 bluray-compat=1 id=0x1011 level=41 bf=2 fake-interlaced=1 bitrate=40000 slices=4 sar=1:1 # vbv-maxrate=40000 # vbv-bufsize=30000 refs=3 cin_pix_fmt=yuv420p color_range=mpeg colorspace=bt709 color_trc=bt709 color_primaries=bt709 profile=high preset=medium flags=+cgop # must be last for bdcreate.C x264opts keyint=25:min-keyint=4:qpmin=3:qpmax=33:qp_step=4:merange=8:vbv-maxrate=40000:vbv-bufsize=30000 --- /usr/share/cin/ffmpeg/format/bluray 129/129 100% mpegts mpegts_m2ts_mode=1 mpegts_start_pid=1024 mpegts_pmt_start_pid=256 muxrate 1 #sdt_period=-1 packetsize 2048 preload 500000 But please note some x264 params actually should vary for interlaced or progressive, 25 vs 30 fps: 1080p Primary and Secondary Streams 1080p23.976 / 1080p24 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file NB: the following two streams are encoded using fake-interlaced mode. This allows the stream to be encoded progressively yet flagged as interlaced. 1080p25 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080p29.97 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080i Primary and Secondary Streams (assumes top field first) 1080i25 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 25 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file 1080i29.97 / 1080i30 x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out.264 input.file x264 --bitrate XXXXX --preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 30 --open-gop --slices 4 --tff --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out.264 input.file so, keyint must be dynamically-selected, depending on profile you (user) choose, and fake_interlaced must be present for progressive encodings More on those constrains, refering same page: https://av.community/guides/encoding-video-for-blu-ray-using-h264-avc/ "8-bit (4:2:0) Colorspace is only allowed Main and High profiles are allowed Maximum 3 B-Frames is allowed NAL-HRD Type 2 capable encoder is needed" note, according to some comments around vbv-bufsize you can mux to DVD, so test this, too? "vbv-maxrate Maximum allowed bitrate. Depend of destination media, for normal BD Media, maximum settings is allowed (40000), while for DVD Media (eg BD-5 or BD-9) there is no maximum per Blu-Ray specification, but is strongly recommended that use less or equal to 15000, since DVD reading is slower."

3 3

Windows 10 with Cygwin for Cinelerra limited
by Phyllis Smith 28 Jan '20

28 Jan '20

There is now available a Microsoft Windows 10 *limited* Cinelerra version which *requires Cygwin* installation on your windows system. It has only been minimally tested and the attached pdf file may have errors on how to load and run it. If there is any real interest in it, there could possibly be future improvements. GG/phyllis

1 0

Chapter Plugins on Manual
by Andrea paz 26 Jan '20

26 Jan '20

About the chapter on plugins in the manual I would like to ask some questions: In Resource --> Info, the entries about automatic de-interlacing had been removed because they were not working. Do you remember the discussion where it was discussed? I can't find it. The Gradient Plugin was reworked; but the modifications were hidden, weren't they? Hasn't the configuration window changed? Are there any other plugins (except Sketcher and Tracer) that have changed?

2 6

Nested clip and proxy
by Igor BEGHETTO 26 Jan '20

26 Jan '20

I was reading the manual "CinelerraGG_manual.pdf" (created March 31 2019) and the manual "CinelerraGG_manual_WIP.pdf" (dated 20190826) by LaTex about Nested Clips. (really good job, guys. And I could print it on the paper in a A5 size) I noticed... - "CinelerraGG_manual.pdf", pg.116, Nested Clips - "CinelerraGG_manual_WIP.pdf", pg.122, Nested Clips The final sentence: "...compositions. They can not be proxied" By my tests/works, you CAN create proxies for Nested clips. Proxies are created in Cinelerra folder (where there is "cin" file) instead of the clip folder as usual (with Cin TAR version. With Package version I don't know). Before saving your project, pay attention to disable Proxy feature. You MUST SAVE your PROJECT with PROXY DISABLED otherwise you lose the link to the clips (more or less). Is it right that proxies are created in Cinelerra folder? Is there any reasons they are not created in the clip folder? Thanks. IgorBeg

3 19

Crash when using DenoiseFFT
by David Given 22 Jan '20

22 Jan '20

Hello, I have a sort-of-completely-reliable crash when using the DenoiseFFT plugin: when the plugin is enabled, everything is fine; when disabled, then it dies within about a second on either playback or rendering. The reason for saying sort-of-completely-reliable is because it only crashes with one specific project. I spent a while working on it, with DenoiseFFT enabled, and then it started falling over, so it's clearly something in my project which is doing this. But I don't know what (I needed to get things done so after I figured out it was DenoiseFFT's fault I just disabled it and continued). Attached is the full crash dump and video.xml file. The crash still manifests without the assets being available so it should be easy to reproduce. I hope this is useful... -- ┌─── http://www.cowlark.com ─── │ "I have always wished for my computer to be as easy to use as my │ telephone; my wish has come true because I can no longer figure out │ how to use my telephone." --- Bjarne Stroustrup

2 2

Crash
by Andrea paz 22 Jan '20

22 Jan '20

With the last release (20/01/20) I have quite frequent crash problems. Maybe the problem is a loaded .png; maybe it's my PC that with an AMD navi 10 graphics card gives me continuous problems. I got the dump only without being root. Starting from root I didn't crash! >From console: FFMPEG::open_decoder: some stream have bad times: /home/paz/video_editing/prova/1080/ocra.png FFMPEG::open_decoder: some stream have bad times: /home/paz/video_editing/prova/1080/ocra.png audio0 pad 32 0 (32) FFMPEG::open_decoder: some stream have bad times: /home/paz/video_editing/prova/1080/ocra.png audio0 pad 8 0 (8) audio0 pad 4 0 (4) FFMPEG::open_decoder: some stream have bad times: /home/paz/video_editing/prova/1080/ocra.png audio0 pad 8 0 (8) audio0 pad 32 0 (32) audio0 pad 32 0 (32) audio0 pad 32 0 (32) audio0 pad 16 0 (16) ** segv at (nil) in pid 162210, tid 163161 writing debug data to /tmp/cinelerra_162210.dmp lock_items: 17 lock_frees: 16 ** dump complete Advice: «/bin/sh» crashed. PS: the data provided are few. Don't waste too much time on it because it's probably my system.

2 4

Translate CinelerraGG in spanish
by Rafa Mar Multimedia en Gnu\Linux 21 Jan '20

21 Jan '20

I'm Spanish and I've been trying Cinelerra GG for a few days and I liked it so much that I decided to write a series of tutorials about the application. I have noticed many errors and misspellings in the Spanish translation, how can I help to correct and improve the translation? I am an audiovisual technician and my programming knowledge is very low. If you tell me the steps to follow I can help.

2 1

Something to think about for the future -- Candidate release
by Phyllis Smith 19 Jan '20

19 Jan '20

Recently in another email, IgorB had the following input/suggestion and I wanted to respond in a new thread. > It is very time consuming to learn a workflow and then to change it again. > Every time GG make a change in software it is a great time consuming > also for who have to update the Manual, I think. ... > I would like a release where users have more time to test in depth; > usually this pre-release is called candidate release (all of you know). > So the Manual,and the video tutorial, has a few of time to reflect the > software. > Of course, even though a "stable" release is out, there would always be > the rolling release (month release). Maybe eventually we could get to a "candidate" release thus relieving the burden of testing if more programmers become available. What I see as the major problem at this time is the fact that many of the Issue Tracker BTs have feature requests that are not obvious to us (as mentioned many a time, we are not artists). Consequently, as gg programs something, it is almost imperative to get immediate test feedback before it goes into the monthly builds because then it is really hard to change it. If instead a "candidate" release were used for 7 days before the builds, it might not be enough time to change things mostly because gg's brain gets loaded up working on a feature and then loaded with something entirely different. A lot of time is wasted re-visiting program code that was wiped out of his brain while working on a different section of code..

1 0

Just FYI, LaTex PDF Manual is now available...
by Phyllis Smith 15 Jan '20

15 Jan '20

I added a News post to the cinelerra-gg.org website that now points to the newly converted LaTeX version PDF manual. As before with the odt version, it is pointed to under Download, Documentation, User Manual. The News post says it all except the most important parts: !! *Andrey* (Einhander) setting this all up with all of the necessary configuration for the Github and for LaTeX was a HUGE amount of work. Without this, the manual have floundered. !! *Andrea* converting just about all of the .odt's to .tex's was a HUGE amount of work which included adding some pretty fancy tables, new more readable/relevant png's, and more that I am unaware of. And *MatN* swung in to help convert most of the Appendix (probably after about 10 hours of learning how to use LaTeX). Much thanks to them and to all assistance and feedback from others along the way. But it is not over yet - more work, rewrite, additions, cleanup, and FUN to follow. GG/Phyllis

3 3