September 2021 - Cin - Cinelerra-GG Mailing Lists

FranceBB's LUT collection
by Andrew Randrianasulu 16 May '25

16 May '25

forum https://forum.doom9.org/showthread.php?t=176091 it says those LUTs should be usable for ffmpeg's lut3d and therefore for CinGG? github (each *.cube can be several mb's big) https://github.com/FranceBB/LinearTransformation author says they were verified on professional equipment... list includes PAL and NTSC variants for rec. 601....

3 6

I tried to add AVC-Intra 100 output profiles
by Andrew Randrianasulu 08 May '25

08 May '25

But not sure if I did this correctly. https://en.wikipedia.org/wiki/AVC-Intra says for AVC-Intra 100: AVC-Intra 100: nominally 100 Mbit/s, size of each frame is fixed CAVLC entropy coding only. All formats are High 4:2:2 Intra Profile, Level 4.1 4:2:2 chrominance sampling frames are not scaled and yeah, this French-language pdf actually says the same: https://web.archive.org/web/20110720215759/http://www.ficam.fr/upload/docum… 50M 100M Standard MPEG-4 part10 AVC/H.264 Profile High 10 Intra High 4:2:2 Intra Level Level 3.2/4.0 Level 4.1 Resolution 1440x1080 / 960x720 1920x1080 / 1280x720 Sampling 4:2:0 4:2:2 Bit rate 54Mbps 111Mbps Block size Y: 8x8, C: 4x4 Intra Prediction Y: 9mode, C: 4mode MBAFF Yes De-block filter No Slice/frame 10 Entropy coding CABAC CAVLC so, I looked up ffmpeg cmd line https://trac.ffmpeg.org/ticket/3597 ffmpeg -v info -i /mnt-data/backup4/vol0/export/CUHK\ 2014-1/V017b.mov -vcodec libx264 -intra -pix_fmt yuv422p10le -vb 100M -x264opts avcintra-class=100 -x264opts colorprim=bt709 -x264opts transfer=bt709 -x264opts colormatrix=bt709 -threads 4 -acodec copy V017b-ffmpeg-git-avcintra100.mov Huh, said I and entered those params in opts file, actually in two files (mp4 and mov containers) mov libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 mp4 libx264 cin_pix_fmt=yuv422p10le flags -global_header keyint_min=0 x264-params=keyint=0:colorprim=bt709:transfer=bt709:colormatrix=bt709 avcintra-class=100 bufsize=100000000 level=4.1 both for progressive content, for interlace you must add some more flags: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-January/035049.html -flags +ildct+ilme -x264opts interlaced=1 Also, there is still lack of (GUI) user notification if file writing failed due to NO SPACE on device :} FFStream::write_packet: write packet failed. file:/dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::encode_frame: encode failed. file: /dev/shm/avci_new.mp4 err: На устройстве не осталось свободного места FFStream::flush failed :file:/dev/shm/avci_new.mp4 err: Операция не позволена Render::render_single: Session finished. ** rendered 273 frames in 85.585 secs, 3.190 fps Render::render_single: Session finished. ** rendered 273 frames in 85.485 secs, 3.194 fps Render::render_single: Session finished. ** rendered 273 frames in 82.176 secs, 3.322 fps Profile sort of assumes you set project to some supported resolution, framerate, etc, otherwise libx264 will fail with console error message..... I found some talk about AVC-Ultra, there even was patch for x264, but it was not merged: https://mailman.videolan.org/pipermail/x264-devel/2015-September/011412.html Also, I think sound must be uncompressed, but I'm not sure.

2 5

Use MAXCHANNELS define in mwindow.C
by Andrew Randrianasulu 25 Jan '24

25 Jan '24

Rest of CinGG seems to use it: guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ grep 'MAXCHANNELS' *.C arender.C: for( int i=0; i<MAXCHANNELS; ++i ) { arender.C: for( int i=0; i<MAXCHANNELS; ++i ) delete buffer[i]; arender.C: meter_history->init(MAXCHANNELS, calculate_history_size()); arender.C: for( int i=0; i<MAXCHANNELS; ++i ) { arender.C: for( int i=0; i<MAXCHANNELS; ++i ) { arender.C: for(int i = 0; i < MAXCHANNELS; i++) arender.C: for(int i = 0; i < MAXCHANNELS; i++) assetedit.C: (int)MAXCHANNELS, x, y, xS(50)) audioconfig.C: CLAMP(oss_in_channels, 1, MAXCHANNELS); audioconfig.C: CLAMP(oss_duplex_channels, 1, MAXCHANNELS); convert.C: for( int i=0; i < MAXCHANNELS; ++i ) pan_auto->values[i] = 0; convert.C: if( atrack >= MAXCHANNELS ) atrack = 0; dcoffset.C: for(int i = 0; i < MAXCHANNELS; i++) dc_offset[i] = 0; edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) { edlsession.C: for( int i=0; i<MAXCHANNELS; ++i ) { edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) { edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) { edlsession.C: Workarounds::clamp(audio_channels, 0, MAXCHANNELS - 1); edlsession.C: Workarounds::clamp(video_channels, 1, MAXCHANNELS - 1); edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) edlsession.C: for(int i = 0; i < MAXCHANNELS; i++) { fileformat.C: : BC_TumbleTextBox(fwindow, (int)atol(text), (int)1, (int)MAXCHANNELS, x, y, 50) mwindowedit.C: for( int i=0; i < MAXCHANNELS; ++i ) { panauto.C: bzero(values, MAXCHANNELS * sizeof(float)); panauto.C: bzero(values, MAXCHANNELS * sizeof(float)); panauto.C: memcpy(this->values, pan_auto->values, MAXCHANNELS * sizeof(float)); preferences.C: while( channels < MAXCHANNELS ) { preferences.C: for( int i=0; i<MAXCHANNELS; ++i ) { preferences.C: for( int i = 0; i < MAXCHANNELS; i++ ) { record.C: for( int i=0; i<MAXCHANNELS; ++i ) { record.C: for( int i=0; i<MAXCHANNELS; ++i ) { recordgui.C: for( int i=0; i<MAXCHANNELS; ++i ) { renderengine.C: for( int i=0; i<MAXCHANNELS; ++i ) { resourcethread.C: for(int i = 0; i < MAXCHANNELS; i++) resourcethread.C: for(int i = 0; i < MAXCHANNELS; i++) resourcethread.C: for( int i=0; i<MAXCHANNELS; ++i ) { setformat.C: CLAMP(new_channels, 1, MAXCHANNELS); setformat.C: add_subwindow(new BC_ITumbler(channels, 0, MAXCHANNELS, setformat.C: int new_channels = CLIP(atoi(get_text()), 0, MAXCHANNELS); tracking.C: double output_levels[MAXCHANNELS]; virtualanode.C: for(int i = 0; i < MAXCHANNELS; i++) vtracking.C: double output_levels[MAXCHANNELS]; vwindowgui.C: Samples *samples[MAXCHANNELS]; vwindowgui.C: while( ch < MAXCHANNELS ) samples[ch++] = 0; guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ grep 'MAXCHANNELS' *.h arender.h: Samples *audio_out[MAXCHANNELS]; arender.h: Samples *buffer[MAXCHANNELS]; arender.h: int buffer_allocated[MAXCHANNELS]; dcoffset.h: int dc_offset[MAXCHANNELS], dc_offset_total[MAXCHANNELS], dc_offset_count; edlsession.h: int achannel_positions[MAXCHANNELS]; edlsession.h: int vchannel_x[MAXCHANNELS]; edlsession.h: int vchannel_y[MAXCHANNELS]; maxchannels.h:#ifndef MAXCHANNELS maxchannels.h:#define MAXCHANNELS 32 panauto.h: float values[MAXCHANNELS]; preferences.h: int channel_positions[MAXCHANNELS][MAXCHANNELS]; record.h: int64_t dc_offset[MAXCHANNELS]; recordgui.h: RecordGUIDCOffsetText *dc_offset_text[MAXCHANNELS]; recordgui.h: BC_Meter *meter[MAXCHANNELS]; virtualanode.h: Auto *pan_before[MAXCHANNELS], *pan_after[MAXCHANNELS]; so I used it for max number of channels for auto-created project (was just 6): diff --git a/cinelerra-5.1/cinelerra/mwindow.C b/cinelerra-5.1/cinelerra/mwindow.C index f245018a..690c7ef8 100644 --- a/cinelerra-5.1/cinelerra/mwindow.C +++ b/cinelerra-5.1/cinelerra/mwindow.C @@ -5088,7 +5107,7 @@ int MWindow::select_asset(Asset *asset, int vstream, int astream, int delete_tra int channels = 0; for( uint64_t mask=channel_mask; mask!=0; mask>>=1 ) channels += mask & 1; if( channels < 1 ) channels = 1; - if( channels > 6 ) channels = 6; + if( channels > MAXCHANNELS ) channels = MAXCHANNELS; session->audio_tracks = session->audio_channels = channels; int *achannel_positions = preferences->channel_positions[session->audio_channels-1]; =====

5 13

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

Cinelerra context help - a complete implementation
by Georgy Salnikov 24 Mar '22

24 Mar '22

Hi all, This new implementation of Cinelerra context help can be requested from almost any Cinelerra window or subwindow by pointing with the mouse cursor on the GUI element of interest and pressing Alt/h. That HTML manual page will be shown via the configured web browser, which is assumed as most relevant to the GUI element being currently under the mouse pointer. For more information see issue 568 on the bugtracker: https://www.cinelerra-gg.org/bugtracker/view.php?id=568 How to install, configure and demonstrate the new functionality --------------------------------------------------------------- 1. Apply the patch (see BT568) to the CinGG source tree: https://www.cinelerra-gg.org/bugtracker/file_download.php?file_id=775&type=… 2. After patching one new file appears: doc/ContextManual.pl. This is a perl script. It must be given exetutable permissions. 3. Build and install CinGG as usual. 4. The prerequisite for context help is CinelerraGG HTML manual. After installation of CinGG itself, place the complete unchanged directory CinelerraGG_Manual, as it was produced by latex2html from the manual package, into the 'doc' directory of the installed Cinelerra package. This will be the directory bin/doc/CinelerraGG_Manual if CinGG was built --with-single-user. The script ContextManual.pl should appear after installation also here, in bin/doc. 5. In principle, this is sufficient. Nevertheless, the bin/doc/ContextManual.pl script can be configured further. Look in the script text. You can define your preferable web browser, or redefine it to 'echo' for debug purposes. There are also some predefined HTML pages for Contents and Index, and several explicitly rewritten keyphrases. However, there can be hardly a need to redefine anything except the name of the browser executable. 6. Start Cinelerra and open a project with some assets, effects, keyframes, etc. May be, open some additional Cinelerra dialog windows, plugin settings, etc. Try to point with the mouse on different GUI elements or on empty spaces in different windows and press Alt/h. You should get different manual pages in the browser (if browser was not yet started, it should start automatically). How it works, from the user's point of view ------------------------------------------- The hotkey to request context help is Alt/h. Why? A simple 'h' does not fit: in text fields it has to input the letter 'h'. So is Shift/h: it would mean the capital letter 'H'. Ctrl/h and Ctrl/Shift/h are also not suitable: it is <Backspace>. Something like <F1> would be also not good, <Fn> are already utilized in Compositor. Unlike these all, Alt/h seems to be a good hotkey and, to the best of my knowledge, it is not assigned to anything else throughout the whole Cinelerra code. What particular help page is shown, depends on the mouse cursor location while Alt/h is pressed. Usually, when the mouse is located in some window or dialog, the help page related to the functionality of this window or dialog is shown. In this case the mouse can point either on some widget, or on an empty area in the window. In Cinelerra GUI there are several rich loaded windows, Timeline and Compositor for example. In such a case different help pages can be requested depending on the particular GUI element under the mouse. For example, pressing Alt/h while pointing on the Autos curve in a track would show help on automation keyframes, pointing on the Overlay mode button in the patchbay would show help on overlays, pointing on the camera control in Compositor would show help on camera and projector. If no context dependent help page is found, the manual page of Contents itself is shown. Most probably it means, that either the meaning of this window is obvious (so is the 'Tip of the day' window, for example), or it is not (yet) documented. Requesting context help for plugins ----------------------------------- There are following possibilities to request help page for the particular plugin of interest. 1) Pressing Alt/h with mouse in the dialog window of plugin settings 2) Pressing Alt/h while pointing with the mouse on the plugin bar in a track (or transition bar, or transition icon) 3) Pressing Alt/h while pointing on the plugin name (icon) in the Resources window. If plugin tooltips are on, help for the highlighted (plugin under mouse) is shown. If plugin tooltips are off, help for the selected plugin is shown (it is made so, because in the latter case it would be difficult to figure out, without a visual feedback, which particular item is currently under mouse). 4) Pressing Alt/h while pointing on the plugin name in the Attach Effect dialog Requesting context help on Contour Shuttle ------------------------------------------ Contour Shuttle has no Alt/h, yeh. Nevertheless, its help page can be requested by simultaneous pressing both Alt keys (left and right) on the keyboard followed by pressing any button on the Contour Shuttle. Here, pressing both Alt keys is necessary due to the way of X11 to track the status of modifiers. To cancel this mode, press any single modifier key (Alt, Ctrl or Shift) once. _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email sge(a)nmr.nioch.nsc.ru _______________________________________________________________________________

7 43

Fwd: Webpage Translation into Spanish
by Rafa Mar Multimedia en Gnu\Linux 28 Jan '22

28 Jan '22

Hi dear Phyllis Spanish translation of the terms of the appearance tab of the configuration: Autosave continous backups = *Copia de seguridad continua* The tip in Spanish = *Cuando cierre Cinelerra se guardarán unicamente las últimas 50 copias de seguridad. Si trabaja durante mucho tiempo sin reiniciar Cinelerra, corre el riesgo de ocupar mucho espacio con las continuas copias de seguridad.* Greetings!!

4 7

offtopic: Digitize and record Video with A/D USB adapters
by Terje J. Hanssen 14 Oct '21

14 Oct '21

Although I have and have used some Black Magic external tools for this, I'm also interested in simple and low cost options for Linux workstations. In a recent article the Augustin VGB100 usb2.0 video adaper and VLC was used to record video https://www.arsouyes.org/en/blog/2021/2021-05-17_Numerisation_VHS Any experience here with similar A/D video adapters, quality and applications for recording on Linux?. Second I wonder if some lossless, compressed master video format is available for better quality before final converting with typical ffmeg? And third, maybe a stupid question: Is it possible to record just Audio with an A/D Video adapter, which audio record format and what quality, compared with a pure Audio adapter? And if so, can audio record applications like Audiacity be used? Terje

7 28

libaom 3.1.1 patch for Ubuntu 16.04.7
by Andrew Randrianasulu 10 Oct '21

10 Oct '21

It seems Cmake version bump in libaom 3.1.x was mostly cosmetic - it builds with attached patch (put in thirdparty/src) right now this new (CinelerraGG/ffmpeg-4.4/libaom-3.1.1) build completes - so not tested yet.

4 5

Re: [Cin] offtopic: Digitize and record Audio via Line-In Jack or via USB adapter?
by mat 04 Oct '21

04 Oct '21

Your MSI Z170-A PRO motherboard has according to specs a Realtec AL892 audio chip. The input converters should have 90 dB S/N (signal-to- noise) ratio (A-weighted), but of course the motherboard might make it a little worse. However, from you record player of tape you will be very lucky to get better than 65 dB S/N. So if an A-D converter has a S/N of 70 dB or better, it is more than good enough for this. Regarding your PC input channels, on current desktop motherboards I usually see three 3.5 mm mini-jacks. Their recording quality for line- in is close to 90 dB S/N or even above 100 on the better ones. In pavucontrol (audio mixer), first check the configuration tab, to see if the Built-in Audio is set up correctly. "Analog stereo duplex" is probably right. Then, on the "Input devices" tab, at the bottom set it to show "Hardware Input Devices", then check that the Port is set to the correct port. For me, "Line In" shows correctly if something is plugged in or not. Make also sure the gain is set to 100%. That said, I sometimes have problems recording LineIn with Audacity, even though all seems OK. have not yet determined what the cause is. External USB sound cards can be quite good, if you stay away from the very cheap ones that are mic/phone only. I have a Behringer UCA-202 which is good enough for this, but there are much better ones (at a price), look at music-oriented webshops. I presume to have an RIAA pre- amp for you record player, these are usually set up for less output that typical PC or usb-audio input, which expect 1 Volt. Drivers are not needed, and disregard any reviews that don't show measurements. MatN

3 7

New AppImage release for Sept. 30 now available
by Phyllis Smith 30 Sep '21

30 Sep '21

The latest releases are at: 1=newer kernel O/S 2=older kernel O/S; even for newly installed O/S, this may be needed because of older kernel 3=32bit system of older variety 4=newer kernel O/S that handles 10 and 12 bit as well as 8 bit 1. https://cinelerra-gg.org/download/images/CinGG-20210930-x86_64.AppImage 2. https://cinelerra-gg.org/download/images/CinGG-20210930-x86_64-older_distro… 3. https://cinelerra-gg.org/download/images/CinGG-20210930-i386.AppImage 4. https://cinelerra-gg.org/download/images/CinGG-20210930-multibit.AppImage Both PDF and HTML versions of the Manual have been updated on the website as well as the releasenotes. *********************************** Copy of latest ReleaseNotes items The *LV2 plugins* related source code has been improved by *MatN*, making it more robust and better able to prevent crashes at startup for new Operating Systems and LV2 plugins. In addition he has updated the blacklist for the plugins. Problem was reported by Fary54 when he upgraded Debian and new Ardour plugins became available – he assisted in reporting and testing the *BT #586* issue. - Note bootstrap.c System Command was increased from 1024 to 2100 to ameliorate some warnings. - The LV2 plugin path is now being printed to the CinGG startup window; same as other plugins. A *libaom patch* was provided by *AndrewR* for allowing libaom to be updated on Ubuntu 16 due to cmake version. The Motion51 plugin with Dissolve transition problem has been fixed by a Freelancer. *BT #564* was reported and documented by Skinkie. New Icons for the 9 missing ones have been added for viewing in the Resources window. These are alpha, boxblur, colorspace, foreground, posterize, sketcher, timeblur, timelapsehelper, and tracer.

1 0