- Cin - Cinelerra-GG Mailing Lists

CinGG AppImage
by Andrea paz 02 Mar '21

02 Mar '21

Hi, I was wondering if it's time to put appimage as the main installation method of CinGG, highlighting it in the website and the manual. The binaries remain working but not updated. What do you guys think?

5 10

bcast
by Andrea paz 28 Feb '21

28 Feb '21

I installed CinGG from git with a .bcast5 put in /home/paz/.bcast5 on internal NVME; plus I have the appimage I set as /home/store/.bcast6 on internal SSD. But it doesn't work: the two instances take the same .bcastX. If I set the built CinGG's .bcast5 the appimage also sees that .bcast5; if I set .bcast6 for the appimage the built also switches to that. Does this happen to you as well?

2 2

Server maintenance
by Sam 27 Feb '21

27 Feb '21

To our visitors, friends and supporters, This weekend some maintenance work will be done on the server, for this reason there may be some temporary interruptions on the website. Sam

2 4

Interlace driving me mad .....
by Andrew Randrianasulu 21 Feb '21

21 Feb '21

So, I grep'ed ffmpeg-4.3 sources and apparently thise falgs consumed by few encoders outside of mpeg2/4: guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ grep 'AV_CODEC_FLAG_INTERLACED_DCT' ../thirdparty/ffmpeg-4.3/libav libavcodec/ libavdevice/ libavfilter/ libavformat/ libavresample/ libavutil/ guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ grep 'AV_CODEC_FLAG_INTERLACED_DCT' ../thirdparty/ffmpeg-4.3/libavcodec/*.c ../thirdparty/ffmpeg-4.3/libavcodec/cuviddec.c: avctx->flags |= AV_CODEC_FLAG_INTERLACED_DCT; ../thirdparty/ffmpeg-4.3/libavcodec/cuviddec.c: avctx->flags &= ~AV_CODEC_FLAG_INTERLACED_DCT; ../thirdparty/ffmpeg-4.3/libavcodec/dnxhddata.c: interlaced == !!(avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) && ../thirdparty/ffmpeg-4.3/libavcodec/dnxhdenc.c: if (avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/dvenc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/libx264.c: x4->params.b_interlaced = avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT; ../thirdparty/ffmpeg-4.3/libavcodec/libxavs.c: x4->params.b_interlaced = avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT; ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if ((s->avctx->flags & (AV_CODEC_FLAG_INTERLACED_DCT | AV_CODEC_FLAG_INTERLACED_ME)) && ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: s->progressive_sequence = !(avctx->flags & (AV_CODEC_FLAG_INTERLACED_DCT | ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/nvenc.c: if (ret < 1 && avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/nvenc.c: if (avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/nvenc.c: if (avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { ../thirdparty/ffmpeg-4.3/libavcodec/pngenc.c: s->is_progressive = !!(avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT); ../thirdparty/ffmpeg-4.3/libavcodec/proresenc_anatoliy.c: ctx->is_interlaced = !!(avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT); ../thirdparty/ffmpeg-4.3/libavcodec/proresenc_kostya.c: if (avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) ../thirdparty/ffmpeg-4.3/libavcodec/proresenc_kostya.c: int interlaced = !!(avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT); ../thirdparty/ffmpeg-4.3/libavcodec/qsvenc.c: if (avctx->flags & AV_CODEC_FLAG_INTERLACED_DCT) { guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ grep 'AV_CODEC_FLAG_INTERLACED_ME' ../thirdparty/ffmpeg-4.3/libavcodec/*.c ../thirdparty/ffmpeg-4.3/libavcodec/huffyuvenc.c: s->interlaced = avctx->flags & AV_CODEC_FLAG_INTERLACED_ME ? 1 : 0; ../thirdparty/ffmpeg-4.3/libavcodec/motion_est.c: if ((s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) ../thirdparty/ffmpeg-4.3/libavcodec/motion_est.c: if ((s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) ../thirdparty/ffmpeg-4.3/libavcodec/motion_est.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) { ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo.c: (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME)) { ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if ((s->avctx->flags & (AV_CODEC_FLAG_INTERLACED_DCT | AV_CODEC_FLAG_INTERLACED_ME)) && ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: AV_CODEC_FLAG_INTERLACED_ME) || ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) { ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) { ../thirdparty/ffmpeg-4.3/libavcodec/mpegvideo_enc.c: if (s->avctx->flags & AV_CODEC_FLAG_INTERLACED_ME) { So, reworked this section again ... basically only excluding mjpeg codec case from setting those flags, instead of whilelisting mpeg2/4 only Strangely ffv1/avi shows interlace (with my patch) if source was Top Field First and not showing it if source was Bottom Field First ..:/ dv file re-encoded as dv_ntsc.avi shows bff correctly, it seems. mp4 container with h264 also gets it right now .... mpeg2 works (but not sure if field order correct or now ..I'm confused by ffmpeg source :/) mkv seems to work (but it was working before) https://cloud.mail.ru/public/5AM1/275yC576u How to test those 'tb/bb/tt/bt' cases? There must be some artificial picture clearly showing if I did it wrong ..Not found it yet.

5 14

Cinelerra GG bugtracker does not allow new reports
by Stefan de Konink 18 Feb '21

18 Feb '21

Hi, I have tried to report something new on the bugtracker. I notice that when pressing report issue (both buttons) the page gets white page which then redirects back to the overview. -- Stefan

6 8

Backup in CinGG
by Andrea paz 11 Feb '21

11 Feb '21

I was thinking of adding a section in the manual about how backup works in CinGG. Please correct me if I am wrong: if I don't enable the new option (default), a backup is created at each editing action (see below the list of actions suggested by Andràs) but this overwrites the previous backup.prev so in .bcast5 there will be only one backup file (plus backup.xml whose function I don't understand). The same when we manually create a backup via File --> save backup. When we make a File --> Load backup, in addition to bring on the timeline the backup.prev we also create a new backup.prev. If I enable "Autosaves continuous backups" the backup.prev file is not overwritten, but a new backup.prev_xxxxxxxx_xxxxxx (with data and clock time) is created. These are small files so their number is not a problem. In any case when you exit CinGG the various backups are deleted except for the last 50, which will still be available at the next restart. The new option is put in Settings --> Preferences --> Appearance Tab under the Dangerous section because if you have a crash or anyway you don't exit CinGG correctly, the delete phase doesn't happen and the risk is the increase of the backup files inside .bcast5 but, as said, their size is very small and so not a big problem. With this option enabled, how does File --> save/load backup work? Is there anything I didn't understand? Is there anything to add? There are a few parts where save_backup() is called (Reuss Andràs): cinelerra/cwindowgui.C:2 cinelerra/swindow.C:1 cinelerra/keyframepopup.C:2 cinelerra/pluginpopup.C:1 cinelerra/mwindowedit.C:87 cinelerra/presetsgui.C.sav1:1 cinelerra/assetpopup.C:1 cinelerra/cwindowtool.C:1 cinelerra/render.C:1 cinelerra/setformat.C:1 cinelerra/mwindow.C:9 cinelerra/keyframegui.C:2 cinelerra/mwindowgui.C:1 cinelerra/mainmenu.C:1 cinelerra/loadfile.C:2 cinelerra/savefile.C:2 cinelerra/menueffects.C:1 cinelerra/main.C:1 cinelerra/presetsgui.C.sav:1 cinelerra/record.C:1 cinelerra/plugindialog.C:1

3 4

AppImage for CinelerraGG testing
by Phyllis Smith 11 Feb '21

11 Feb '21

MatN has provided all of the ground work to make an AppImage for CinelerraGG. I have followed the instructions he provided and there are now 2 versions for testing. I only did very minimal testing to load a file. Files are at: https://cinelerra-gg.org/download/testing/ cin_for_older_distros.AppImage - built on Ubuntu 16 (kernel 4.4, I think) cin_for_newer_distros.AppImage - built on Fedora 32 (kernel 5.8, I think) After downloading you will have to change the mode for execution (chmod +x cin_for_older_distros.AppImage) For appimage, the build is supposed to be done on the lowest version distro because otherwise newer libraries might be missing. For example, I tried running cin_for_newer_distros.AppImage on ubuntu 16 and GLIBC version xxx.xxx was not available.

5 8

automatic save of
by Reuss András 08 Feb '21

08 Feb '21

Hi I read sometimes cinelerra mail list (not very carefully) and someone once asked for an automatic backup with timestamp or something like that. I created a small patch that would provide this: on save_backup() call, a new version with timestamp is created from backup.prev. I don't know if it is useful at all. It compiles at least, but I cannot test it because cinelerra stops at start due to some missing theme plugin, did not investigate it. Thanks for your attention. Br Andras

5 14

Openjpeg update ....
by Andrew Randrianasulu 06 Feb '21

06 Feb '21

It seems to work, at least I observed up to 300+% cpu load on encoding I made simple openjpeg.mov to put in /usr/share/cin/ffmpeg/video I can encode into rgba64 lossless, but it takes like 5 minutes for 47 seconds long 700x400 file (but with background render set to EXR/DWAA, and project set to RGBA-float, and vf_pseudocolor and some fader ...) playing this file with mplayer in realtime apparently impossible on my machine :} mplayer -vo x11 /dev/shm/OPENJPEG.mov MPlayer SVN-r38247-10.0.1 (C) 2000-2021 MPlayer Team parse error at line 423 do_connect: could not connect to socket connect: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing /dev/shm/OPENJPEG.mov. libavformat version 58.65.101 (internal) libavformat file format detected. [mov,mp4,m4a,3gp,3g2,mj2 @ 0x574c054c]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol [lavf] stream 0: video (jpeg2000), -vid 0 [lavf] stream 1: audio (aac), -aid 0, -alang rus VIDEO: [mjp2] 704x400 24bpp 25.000 fps 143587.3 kbps (17527.7 kbyte/s) ========================================================================== Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family libavcodec version 58.119.100 (internal) [libopenjpeg @ 0x57601cf4]Requested frame threading with a custom get_buffer2() implementation which is not marked as thread safe. This is not supported anymore, make your callback thread-safe. Selected video codec: [fflibopenjpeg] vfm: ffmpeg (OpenJPEG MJPEG2000) ========================================================================== Clip info: major_brand: qt minor_version: 512 compatible_brands: qt encoder: Lavf58.65.101 Load subtitles in /dev/shm/ ========================================================================== Forced audio codec: mad Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders [aac @ 0x57601cf4]Multiple frames in a packet. AUDIO: 48000 Hz, 2 ch, floatle, 118.0 kbit/3.84% (ratio: 14754->384000) Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio)) ========================================================================== AO: [alsa] 48000Hz 2ch floatle (4 bytes per sample) Starting playback... [aac @ 0x57601cf4]channel element 0.0 is not allocated Could not find matching colorspace - retrying with -vf scale... Opening video filter: [scale] Movie-Aspect is 1.76:1 - prescaling to correct movie aspect. [swscaler @ 0x5773aa54]bicubic scaler, from rgba64le to bgra using MMXEXT VO: [x11] 704x400 => 704x400 BGRA [VD_FFMPEG] DRI failure. Movie-Aspect is 1.76:1 - prescaling to correct movie aspect. VO: [x11] 704x400 => 704x400 BGRA A: 0.0 V: 0.0 A-V: 0.000 ct: 0.000 0/ 0 ??% ??% ??,?% 0 0 [VD_FFMPEG] DRI failure. A: 8.7 V: 6.6 A-V: 2.013 ct: -0.019 0/ 0 46% 38% 4.9% 50 0 ************************************************ **** Your system is too SLOW to play this! **** ************************************************ Possible reasons, problems, workarounds: - Most common: broken/buggy _audio_ driver - Try -ao sdl or use the OSS emulation of ALSA. - Experiment with different values for -autosync, 30 is a good start. - Slow video output - Try a different -vo driver (-vo help for a list) or try -framedrop! - Slow CPU - Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts, e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all. - Broken file - Try various combinations of -nobps -ni -forceidx -mc 0. - Slow media (NFS/SMB mounts, DVD, VCD etc) - Try -cache 8192. - Are you using -cache to play a non-interleaved AVI file? - Try -nocache. Read DOCS/HTML/en/video.html for tuning/speedup tips. If none of this helps you, read DOCS/HTML/en/bugreports.html. A: 9.1 V: 6.8 A-V: 2.269 ct: -0.019 0/ 0 51% 38% 5.1% 55 0 file is like 810 mb big :} Additional patches attached .... I can't say OpenEXR-2.5-opt.diff help much (this was optimization they talked about in OpenEXR 2.5.x) but apparently it still applicaple to 2.4.1, just rename it and put in thirdparty/src if you want to test FORMAT_brender_exr_added.diff is basically not very useful (apart from testing?) addition of OpenEXR as background render choice openjpeg-24.patch Basically you should put Openjpeg-2.4.0 tarball into thirdparty/src instead of 2.3.1 and apply this patch for testing ... internal ffmpeg should be build with this version of openjpeg

4 10

Resolution for "help - ?" key in Batch Render Menu
by Phyllis Smith 04 Feb '21

04 Feb '21

(Rather than continuing old discussions over different emails, starting a new thread of moderation). GIT checkin of the "help" key addition to the BatchRender menu is complete with 10 language translations for the Quick Start by RafaMar. I had to do a lot of testing today to try to make sure there are no hangs, but I could have missed something so hopefully there are no problems. Some notes follow: 1) Most likely only new or occasional users will need to take advantage of the help so there is no impact to the majority of people. Especially since with the fast computers these days, Batch Render is considered to be more of an advanced feature. 2) The majority of people using the help key will already have a browser up in another window. But* if no browser is already up*: a) the following message: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost may come up in a terminal window as an informational message as you "browse" around, but should have no effect on Cinelerra. b) the following message: [Child 8939, MediaDecoderStateMachine #2] WARNING: Decoder=7f2eba25cc00 Decode error: NS_ERROR_DOM_MEDIA_*FATAL*_ERR (0x806e0005): file /builddir/build/BUILD/firefox-81.0.2/dom/media/MediaDecoderStateMachine.cpp, line 3470 may come up in a terminal window as an informational message as you "browse" around, but should have no effect on Cinelerra. I tracked this down in my situation to YouTube videos using newer plugins that I did not have hooked up to my browser which would not play and instead just said "Something went wrong". So basically, error messages that were probably there all along but you just did not see, might now be visible. To clear up and get no more of these messages, you can quit out of Cinelerra and then take the browser down and bring it back up as you normally would -- at least this is what worked for me. -------------------------------------- Note to *Andrea*: if you have a chance to confirm the above, that would be highly appreciated. Note to *Walter*: there really is the possibility of a hang in Cinelerra where the user could lose work so xdg-open instead of the environment variable had to be used. This was true of firefox which is the only browser I tested. All of the Shell Commands continue to use CIN_BROWSER and I could not get any hang with the same usage there. Most likely you will not need to use the Batch Render help key anyway. ------------------------------------- I am moving back to test "multiple backups" as provided by Andras and Andrew. Then hopefully the library upgrade as Andrew wrote about a few days ago.

3 2