- Cin - Cinelerra-GG Mailing Lists

Partial patch for detecting SAR/DAR and interlace.
by Andrew Randrianasulu 14 Nov '20

14 Nov '20

Aspect ratio detection still doesn't work, but interlace detection seems to work for mpeg2 files (but not for dv in avi) it prints SAR/DAR to terminal At The Moment: sample_aspect_ratio, 1.333333 display_aspect_ratio, 1.777778 interlace: 2 for HDV 1080i file and interlace: 1 sample_aspect_ratio, 1.000000 display_aspect_ratio, 1.777778 for progressive 1080p25 mpeg2 file diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C index 97b6698a..0264516a 100644 --- a/cinelerra-5.1/cinelerra/ffmpeg.C +++ b/cinelerra-5.1/cinelerra/ffmpeg.C @@ -3468,7 +3468,22 @@ int FFMPEG::ff_coded_height(int stream) float FFMPEG::ff_aspect_ratio(int stream) { - return ffvideo[stream]->aspect_ratio; + //return ffvideo[stream]->aspect_ratio; + AVFormatContext *fmt_ctx = ffvideo[stream]->fmt_ctx; + AVStream *strm = ffvideo[stream]->st; + AVCodecParameters *par = ffvideo[stream]->st->codecpar; + AVRational dar; + AVRational sar = av_guess_sample_aspect_ratio(fmt_ctx, strm, NULL); + if (sar.num) { + printf("sample_aspect_ratio, %f \n", av_q2d(sar)); + av_reduce(&dar.num, &dar.den, + par->width * sar.num, + par->height * sar.den, + 1024*1024); + printf("display_aspect_ratio, %f \n", av_q2d(dar)); + return av_q2intfloat(dar); + } + } const char* FFMPEG::ff_video_codec(int stream) @@ -3509,6 +3524,25 @@ int FFMPEG::ff_video_mpeg_color_range(int stream) return ffvideo[stream]->st->codecpar->color_range == AVCOL_RANGE_MPEG ? 1 : 0; } +int FFMPEG::ff_interlace(int stream) +{ + int interlace = ffvideo[stream]->st->codecpar->field_order; + printf("interlace: %i\n", interlace); + switch (interlace) + { + case AV_FIELD_TT: + return ILACE_MODE_TOP_FIRST; + case AV_FIELD_BB: + return ILACE_MODE_BOTTOM_FIRST; + case AV_FIELD_PROGRESSIVE: + return ILACE_MODE_NOTINTERLACED; + default: + return ILACE_MODE_UNDETECTED; + } +} + + + int FFMPEG::ff_cpus() { return !file_base ? 1 : file_base->file->cpus; diff --git a/cinelerra-5.1/cinelerra/ffmpeg.h b/cinelerra-5.1/cinelerra/ffmpeg.h index 2e1f201f..d4bef2fd 100644 --- a/cinelerra-5.1/cinelerra/ffmpeg.h +++ b/cinelerra-5.1/cinelerra/ffmpeg.h @@ -463,6 +463,7 @@ public: float ff_aspect_ratio(int stream); int ff_color_range(int stream); int ff_color_space(int stream); + int ff_interlace(int sream); double ff_frame_rate(int stream); const char *ff_video_codec(int stream); int64_t ff_video_frames(int stream); diff --git a/cinelerra-5.1/cinelerra/fileffmpeg.C b/cinelerra-5.1/cinelerra/fileffmpeg.C index ff206b10..48c1ca7d 100644 --- a/cinelerra-5.1/cinelerra/fileffmpeg.C +++ b/cinelerra-5.1/cinelerra/fileffmpeg.C @@ -342,6 +342,8 @@ int FileFFMPEG::open_file(int rd, int wr) int video_layers = ff->ff_total_video_layers(); if( video_layers > 0 ) { asset->video_data = 1; + asset->aspect_ratio = ff->ff_aspect_ratio(0); + if (!asset->interlace_mode) asset->interlace_mode = ff->ff_interlace(0); if( !asset->layers ) asset->layers = video_layers; asset->actual_width = ff->ff_video_width(0); asset->actual_height = ff->ff_video_height(0);

1 0

Re: [Cin] actually, added few more formats to theme.C
by Andrew Randrianasulu 13 Nov '20

13 Nov '20

В сообщении от Saturday 31 October 2020 19:21:05 вы написали: > Hi, > > I chime in here, because some time ago I reported what I think may be a > related issue #0000491 on MantisBT: > > 1) HDV format not auto-detected correctly and > 2) HDV formats not available among presets Well, I added two HDV presets, as I udnerstand them .. but I can be wrong, or VERY wrong! diff --git a/cinelerra-5.1/cinelerra/defaultformats.h b/cinelerra-5.1/cinelerra/defaultformats.h index 61bd2165..1fe71282 100644 --- a/cinelerra-5.1/cinelerra/defaultformats.h +++ b/cinelerra-5.1/cinelerra/defaultformats.h @@ -39,14 +39,34 @@ struct formatpresets }; static struct formatpresets format_presets[] = { - { N_("1080P/60"), 2, 2, 48000, 1, 1, 60000.0 / 1001, + { N_("1080P/60"), 2, 2, 48000, 1, 1, 60, + 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("1080P/59.94"), 2, 2, 48000, 1, 1, 60000.0 / 1001, + 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("1080P/30"), 6, 6, 48000, 1, 1, 30, + 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("1080P/29.97"), 6, 6, 48000, 1, 1, 30000.0 / 1001, 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, { N_("1080P/24"), 6, 6, 48000, 1, 1, 24, 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, - { N_("1080I"), 2, 2, 48000, 1, 1, 30000.0 / 1001, + { N_("1080P/23.976"), 6, 6, 48000, 1, 1, 24000.0 / 1001, + 1920,1080, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("1080I/29.97"), 2, 2, 48000, 1, 1, 30000.0 / 1001, 1920,1080, 16,9, ILACE_MODE_BOTTOM_FIRST, BC_YUVA8888 }, + { N_("HDV 1080i/29.97"), 2, 2, 48000, 1, 1, 30000.0 / 1001, + 1440,1080, 16,9, ILACE_MODE_BOTTOM_FIRST, BC_YUVA8888 }, + { N_("HDV 1080i/25"), 2, 2, 48000, 1, 1, 25, + 1440,1080, 16,9, ILACE_MODE_BOTTOM_FIRST, BC_YUVA8888 }, { N_("720P/60"), 2, 2, 48000, 1, 1, 60000.0 / 1001, 1280,720, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("720P/50"), 2, 2, 48000, 1, 1, 50, + 1280,720, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("720P/29.97"), 2, 2, 48000, 1, 1, 30000.0 / 1001, + 1280,720, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("720P/25"), 2, 2, 48000, 1, 1, 25, + 1280,720, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, + { N_("720P/23.976"), 2, 2, 48000, 1, 1, 24000.0 / 1001, + 1280,720, 16,9, ILACE_MODE_NOTINTERLACED, BC_YUVA8888 }, { N_("PAL 576I - DV(D)"), 2, 2, 48000, 1, 1, 25, 720,576, 4,3, ILACE_MODE_BOTTOM_FIRST, BC_YUVA8888 }, { N_("NTSC 480P - DV(D)"), 2, 2, 48000, 1, 1, 60000.0 / 1001, I added plenty of 1080p formats because this line in wiki: https://en.wikipedia.org/wiki/1080p24 "DVB also supports 1080p encoded at ATSC frame rates of 23.976, 24, 29.97, 30, 59.94 and 60.[9][10]" > > https://www.cinelerra-gg.org/bugtracker/view.php?id=491 > > > Terje J. Hanssen > > > Den 31.10.2020 15:30, skrev Andrew Randrianasulu via Cin: > > В сообщении от Saturday 31 October 2020 16:06:48 Pierre autourduglobe via Cin написал(а): > >> Maybe the HDV (1440x1080)? > > Added this too, but in general there is something about pixel aspect ratioI don't understand: > > > > https://en.wikipedia.org/wiki/Pixel_aspect_ratio > > > > 1440x1080i will come as exactly this stream from mpeg2 decoder. But for display/processing it must be stretched 1.33 horizontally? > > > > https://en.wikipedia.org/wiki/HDV > > > > Pixel aspect ratio 1.0 (720p) 1.33 (1080i) > > > > Is this specific kind of aspect ration handled in CinGG? > > > > I see recent (this year) discussion on cin ML, but ... > > > > https://www.mail-archive.com/cin%40lists.cinelerra-gg.org/msg01473.html > > > > "So it changes DAR (Display Aspect Ratio) and/or PAR (Pixel Aspect Ratio) for some types of container/codec: pixel may not be square (1:1)." > > > > so, when it does AND and when it does OR ? :} Because they not the same .... > > > >> Pierre > >> > >> > >> Le 20-10-31 à 07 h 40, Andrew Randrianasulu via Cin a écrit : > >>> Not sure how many of them actually useful (CIF might be, and of course my own 1440x900 :-)), but this list already requires scrolling :} > >>> > >>> diff --git a/cinelerra-5.1/cinelerra/theme.C b/cinelerra-5.1/cinelerra/theme.C > >>> index d89c789f..07cfb1d2 100644 > >>> --- a/cinelerra-5.1/cinelerra/theme.C > >>> +++ b/cinelerra-5.1/cinelerra/theme.C > >>> @@ -274,6 +274,7 @@ void Theme::build_menus() > >>> aspect_ratios.append(new BC_ListBoxItem("3:2")); > >>> aspect_ratios.append(new BC_ListBoxItem("4:3")); > >>> aspect_ratios.append(new BC_ListBoxItem("16:9")); > >>> + aspect_ratios.append(new BC_ListBoxItem("16:10")); > >>> aspect_ratios.append(new BC_ListBoxItem("2.10:1")); > >>> aspect_ratios.append(new BC_ListBoxItem("2.20:1")); > >>> aspect_ratios.append(new BC_ListBoxItem("2.25:1")); > >>> @@ -283,9 +284,11 @@ void Theme::build_menus() > >>> > >>> frame_sizes.append(new BC_ListBoxItem("128x96 ")); > >>> frame_sizes.append(new BC_ListBoxItem("160x120 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("240x160 HQVGA")); > >>> frame_sizes.append(new BC_ListBoxItem("320x240 ")); > >>> frame_sizes.append(new BC_ListBoxItem("360x240 ")); > >>> - frame_sizes.append(new BC_ListBoxItem("400x300 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("384x288 CIF")); > >>> + frame_sizes.append(new BC_ListBoxItem("400x300 qSVGA")); > >>> frame_sizes.append(new BC_ListBoxItem("640x360 nHD")); > >>> frame_sizes.append(new BC_ListBoxItem("640x400 ")); > >>> frame_sizes.append(new BC_ListBoxItem("640x480 VGA")); > >>> @@ -299,19 +302,31 @@ void Theme::build_menus() > >>> frame_sizes.append(new BC_ListBoxItem("1024x576 ")); > >>> frame_sizes.append(new BC_ListBoxItem("1024x768 XGA")); > >>> frame_sizes.append(new BC_ListBoxItem("1152x648 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("1152x768 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("1152x864 XGA+")); > >>> frame_sizes.append(new BC_ListBoxItem("1280x720 HD")); > >>> + frame_sizes.append(new BC_ListBoxItem("1280x800 ")); > >>> frame_sizes.append(new BC_ListBoxItem("1280x1024 SXGA")); > >>> frame_sizes.append(new BC_ListBoxItem("1366x768 WXGA")); > >>> + frame_sizes.append(new BC_ListBoxItem("1440x900 WXGA+")); > >>> frame_sizes.append(new BC_ListBoxItem("1600x900 HD+")); > >>> frame_sizes.append(new BC_ListBoxItem("1600x1200 UXGA")); > >>> frame_sizes.append(new BC_ListBoxItem("1920x1080 Full HD")); > >>> + frame_sizes.append(new BC_ListBoxItem("1920x1280 FHD+")); > >>> + frame_sizes.append(new BC_ListBoxItem("2048x1080 DCI 2K")); > >>> frame_sizes.append(new BC_ListBoxItem("2048x1152 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("2048x1536 QXGA")); > >>> + frame_sizes.append(new BC_ListBoxItem("2160x1440 ")); > >>> frame_sizes.append(new BC_ListBoxItem("2304x1296 ")); > >>> - frame_sizes.append(new BC_ListBoxItem("2560x1440 QHD")); > >>> + frame_sizes.append(new BC_ListBoxItem("2560x1080 UW-FHD")); > >>> + frame_sizes.append(new BC_ListBoxItem("2560x1440 WQHD")); > >>> frame_sizes.append(new BC_ListBoxItem("2880x1620 ")); > >>> - frame_sizes.append(new BC_ListBoxItem("3200x1800 QHD+")); > >>> + frame_sizes.append(new BC_ListBoxItem("3200x1800 WQXGA+")); > >>> + frame_sizes.append(new BC_ListBoxItem("3440x1440 Ultra-Wide QHD")); > >>> frame_sizes.append(new BC_ListBoxItem("3520x1980 ")); > >>> + frame_sizes.append(new BC_ListBoxItem("3840x1600 UW4K")); > >>> frame_sizes.append(new BC_ListBoxItem("3840x2160 4K UHD")); > >>> + frame_sizes.append(new BC_ListBoxItem("4096x2160 DCI 4K")); > >>> frame_sizes.append(new BC_ListBoxItem("4096x2304 Full 4K UHD")); > >>> frame_sizes.append(new BC_ListBoxItem("4480x2520 ")); > >>> frame_sizes.append(new BC_ListBoxItem("5120x2880 5K UHD")); > >>> > >>> ---- > >>> > >>> list of course from https://en.wikipedia.org/wiki/List_of_common_resolutions > >>> > >>> > > > > > >

3 13

UPD: Re: DNxHR presets
by Andrew Randrianasulu 12 Nov '20

12 Nov '20

I also tested _lb and _sq presets. They also seems to accept only yuv422p Should I add some remark all those are for using with progressive video? (in file itself, so user will see it in window, othervise reason why it fails to render may be hidden, if user start Cin from menu) ---------- Пересланное сообщение ---------- Тема: Re: [Cin] DNxHR presets Дата: Понедельник 09 ноября 2020 Отправитель: Andrew Randrianasulu <randrianasulu(a)gmail.com> Получатель: cin(a)lists.cinelerra-gg.org I tried to modify those presets so they show/select right pixel format, but for some reason file path: /dev/shm/DNxHR-yuv422-8bit.mov 435864233 bytes info: format: mov,mp4,m4a,3gp,3g2,mj2 1 video stream vid0 (0), id 0x000063: video1 dnxhd 1920x1080 30.00 pix yuv422p is basically same size as file path: /dev/shm/DNxHR-yuv422.mov 435864233 bytes info: format: mov,mp4,m4a,3gp,3g2,mj2 1 video stream vid0 (0), id 0x000063: video1 dnxhd 1920x1080 30.00 pix yuv422p10le color space:bt709/ range:tv 472+0 frms 15.73 secs 0:00:15.73 (both play fast/realtime on my machine, as opposed to DNxHR_444) -------------------------------------------------------

3 14

Minor cosmetic patch for Format Window
by Andrew Randrianasulu 12 Nov '20

12 Nov '20

Only if I understand terms correctly. diff --git a/cinelerra-5.1/cinelerra/setformat.C b/cinelerra-5.1/cinelerra/setformat.C index cfd43685..1a71b036 100644 --- a/cinelerra-5.1/cinelerra/setformat.C +++ b/cinelerra-5.1/cinelerra/setformat.C @@ -418,7 +418,7 @@ void SetFormatWindow::create_objects() y += mwindow->theme->setformat_margin; add_subwindow(new BC_Title(mwindow->theme->setformat_x3, y, - _("Aspect ratio:"))); + _("Display Aspect Ratio:"))); y += mwindow->theme->setformat_margin; x = mwindow->theme->setformat_x3; add_subwindow(aspect_w = new ScaleAspectText(x, y, thread, mostly self-test to see if I can find where in codebase those strings are located ...

1 0

Parch preventing compilation failure in thirdparty/x264
by Andrew Randrianasulu 12 Nov '20

12 Nov '20

I was recompiling CinGG fot testing "--with-single-user" and found it will fail in x264 directory without some of my old reverts, performed by slackbuild. I have old (2.8) ffmpeg installed system-wide, and x264's configure script was not disabling this integration correctly (even if code was unconditionally adapted to new ffmpeg), so compilation fail. I just added one more parameter in x264 line of thirdparty/Makefile diff --git a/cinelerra-5.1/thirdparty/Makefile b/cinelerra-5.1/thirdparty/Makefile index 27f13c65..880d3128 100644 --- a/cinelerra-5.1/thirdparty/Makefile +++ b/cinelerra-5.1/thirdparty/Makefile @@ -249,7 +249,7 @@ tiff.cfg_params+= --enable-shared=no --disable-zstd $(call if_pkg,libwebp,\ --with-webp-lib-dir=$(call pkg_libs,libwebp))\ $(call if_npkg,libwebp,--disable-webp) twolame.cfg_params?=--enable-shared=no -x264.cfg_params?= --enable-static --enable-pic +x264.cfg_params?= --disable-swscale --enable-static --enable-pic x265.cfg_vars?=$(call cmake_config,source) x265.cfg_params?= -DENABLE_SHARED=no libvpx.cfg_params?= --enable-pic --disable-avx512 shold be applicable cleanly to latest git (commit 3325029f915f54fe7e14d7b2cb1d4b8f4dd8a640 ) I don't think many use such outdated ffmpeg, but this line should not hurt (because x264 in our case just feed via libavcodec API, and scaling can be done early) I rendered small fragment with non-default pixel format, and it appear to work: mediainfo /dev/shm/test.mp4 General Complete name : /dev/shm/test.mp4 Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/avc1/mp41) File size : 1.16 MiB Duration : 15 s 382 ms Overall bit rate : 633 kb/s Writing application : Lavf58.45.100 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High 4:4:4 Predictive@L3 Format settings : CABAC / 4 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 4 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 15 s 360 ms Bit rate : 499 kb/s Width : 720 pixels Height : 576 pixels Display aspect ratio : 4:3 Frame rate mode : Constant Frame rate : 25.000 FPS Standard : PAL Color space : YUV Chroma subsampling : 4:4:4 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.048 Stream size : 936 KiB (79%) Writing library : x264 core 157 Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=4 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=25 / keyint_min=13 / scenecut=40 / intra_refresh=0 / rc_lookahead=25 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 Color range : Limited Matrix coefficients : BT.601 Codec configuration box : avcC Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 15 s 382 ms Bit rate mode : Constant Bit rate : 128 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 240 KiB (20%) Language : Russian Default : Yes Alternate group : 1 mplayer also showing video and saying among other things: [swscaler @ 0x57740034]bicubic scaler, from yuv444p to yuv420p using MMXEXT But I can keep this patch local if you think it risky to apply.

1 0

Sad news: Our developer Good Guy has passed away
by Sam 12 Nov '20

12 Nov '20

It is with dismay and sadness that I have to announce this devastating news that our highly esteemed developer W.P. Morrow aka Good Guy died in a traffic accident last Monday at the age of 66. Bill, as he also called in private, was as so often in his free time, out for sports riding his bicycle when he was hit by a truck. He was taken to hospital, but unfortunately he succumbed to his severe injuries. This news is shocking and makes me speechless, although I find it extremely difficult to find words due to my sadness, I would like to remember him at this point. A look back shows that, together with Phyllis, he has pushed this project forward with great passion, dedication and commitment. His ingenuity and creative solutions were always an enrichment for this project. He was never too comfortable to tackle even small problems and improvements to make the life of the users easier. You could tell that he enjoyed programming a lot. He enjoyed improving Cinelerra-GG and interacting with the community. He has acted selflessly and for the good of all, and through his commitment to free and open software, he has made this world a bit freer and better. The gap he leaves behind is huge and filling it will be hard. Thanks for everything dear Bill. It was a great honor and pleasure to work with you. You will be remembered. We will miss you. Rest in peace. I express my condolences to Phyllis, his family and friends. Sam P.S.: Phyllis has expressed the wish to resume work on the project at a later date, currently she needs some time off, and to participate in the documentation and correspondence as usual. I will continue to support this project as before. The monthly releases cannot be offered in the same way at the moment. Minor changes and improvements will take place from time to time. We are open for new developers and hope for your support.

17 17

Cinelerra for Mageia 7?...
by E R 10 Nov '20

10 Nov '20

Pardon my bad english. I'm an aspiring video editor. I use the Linux distribution Mageia 7. Looking for that software in the "Install & Remove Software", I realize that it is not available (not even for Micro$oft Window$). Then I tried installing it through the console, but the following messages came out like this: sudo: apt-get: command not found sudo: apt-install: command not found That is one of the negative points I have found in this distribution; however, it is the one that performs best on my very old all-in-one computer that I bought many years ago. Not even the official Cinelerra GG website has Mageia documentation?? it's strange This website comes closer to what I'm looking for but I don't understand the many links they provide there. It is not entirely clear their proposal to download it. https://fedora.pkgs.org/rawhide/rpmfusion-free-x86_64/cinelerra-gg-5.1.2020… This is the list of video editing software available for Mageia 7: https://wiki.mageia.org/en/List_of_applications#Video_Players.2C_Video_Edit… I had Linux Mint installed, but it gave me nightmares because the wifi was disconnected very often (the router was somewhat close) and also almost everything I did in this distribution was slow. I uninstalled it. Then I installed Ubuntu Studio but the data pointer (popularly known as "mouse") was "lagging" or getting very slow instead of having that natural and fluid movement. I uninstalled it. Finally, I installed Linux Mageia 7, and it does not give the problems that the previous ones; except for: - The terminal that does not allow me to install any program - The package center does not have some popular softwares (I realized when using Mageia for several months). This forced me to search for several weeks for the rpm softwares that I need, but there are hardly any websites that offer that, except one that took a lot of work to find (but it didn't help me). - Chromium browser does not correctly play sound in Youtube live streams, and videos from other platforms (whether live or not)..... the Opera browser does not play audio and video from Youtube live streams, and does not play videos from other platforms (whether live or not). This is what happened when wanting to install Cinelerra on Mageia 7: THIS I WROTE: urpmi.update-a THIS HAPPENED: medium " Core Release (distrib1)" is up-to-date medium " Core Updates (distrib3)" is up-to-date medium " Nonfree Release (distrib11)" is up-to-date medium " Nonfree Updates (distrib13)" is up-to-date medium " Core Release (distrib46)" is up-to-date medium " Core Updates (distrib48)" is up-to-date medium " Nonfree Release (distrib56)" is up-to-date medium " Nonfree Updates (distrib58)" is up-to-date THEN THIS I WROTE: urpmi cinelerra THIS WAS THE RESULT: bash: urpmi: command not found I will not make you engage to follow up on my case (it is voluntary). And previously said, I'm an aspiring video editor. I use the Linux distribution Mageia 7 (developed by many several former employees of the ex-Mandriva) Beside that, I just recently discovered that now it no longer opens "Install ~ Remove Software" after using " urpmi.update-a” in Mageia's “Konsole Terminal” console; is that common? can't it be fixed anymore? Thanks in advance.

4 3

Re: [Cin] Cin Digest, Vol 25, Issue 13
by Wolfgang Brunner 10 Nov '20

10 Nov '20

I am shocked! First of all, I would like to offer my condolences. I'm lost for words. Dear Phillis, thank you for continuing to support us. I am very sad and stay Wolfgang (video4tux) Am Di., 10. Nov. 2020 um 02:05 Uhr schrieb < cin-request(a)lists.cinelerra-gg.org>: > Send Cin mailing list submissions to > cin(a)lists.cinelerra-gg.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cinelerra-gg.org/mailman/listinfo/cin > or, via email, send a message with subject or body 'help' to > cin-request(a)lists.cinelerra-gg.org > > You can reach the person managing the list at > cin-owner(a)lists.cinelerra-gg.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cin digest..." > > > Today's Topics: > > 1. Re: Sad news: Our developer Good Guy has passed away (W P) > 2. Re: Sad news: Our developer Good Guy has passed away > (edouard chalaron) > 3. Re: Sad news: Our developer Good Guy has passed away > (daniel-cinelerra-gg(a)opayq.com) > 4. Re: Sad news: Our developer Good Guy has passed away > (Andrew Randrianasulu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 09 Nov 2020 22:48:03 +0000 > From: W P <wpfilmmaker(a)yandex.com> > To: Sam via Cin <cin(a)lists.cinelerra-gg.org> > Subject: Re: [Cin] Sad news: Our developer Good Guy has passed away > Message-ID: <4844591604962083(a)iva2-15a880c55b23.qloud-c.yandex.net> > Content-Type: text/plain > > I haven't been active in the community for a while, but I follow the > project closely and read the mailinglist everyday. Reading this news made > me speechless. > > Although I never met him I want to say thank you Good Guy, for your great > efforts not just for Cinelerra but also for creating this cozy community, > your username fit you perfectly. > > Today the world lost a great person. > > My condolences go to Phyllis and the rest of the family, > > Marco aka WPFIlmmaker. > > > ------------------------------ > > Message: 2 > Date: Mon, 9 Nov 2020 23:00:11 +0000 (UTC) > From: edouard chalaron <e.chalaron(a)yahoo.com> > To: "cin(a)lists.cinelerra-gg.org" <cin(a)lists.cinelerra-gg.org> > Subject: Re: [Cin] Sad news: Our developer Good Guy has passed away > Message-ID: <1090245360.3587947.1604962811704(a)mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > What a tragedy. A very sad day indeed ! > All my thoughts to Phyllis and family > Ed > > Sent from Yahoo Mail on Android > > On Tue, Nov 10, 2020 at 8:57, Sam via Cin<cin(a)lists.cinelerra-gg.org> > wrote: It is with dismay and sadness that I have to announce this > devastating > news that our highly esteemed developer W.P. Morrow aka Good Guy died in > a traffic accident last Monday at the age of 66. Bill, as he also called > in private, was as so often in his free time, out for sports riding his > bicycle when he was hit by a truck. He was taken to hospital, but > unfortunately he succumbed to his severe injuries. > > This news is shocking and makes me speechless, although I find it > extremely difficult to find words due to my sadness, I would like to > remember him at this point. > > A look back shows that, together with Phyllis, he has pushed this > project forward with great passion, dedication and commitment. His > ingenuity and creative solutions were always an enrichment for this > project. He was never too comfortable to tackle even small problems and > improvements to make the life of the users easier. You could tell that > he enjoyed programming a lot. He enjoyed improving Cinelerra-GG and > interacting with the community. He has acted selflessly and for the good > of all, and through his commitment to free and open software, he has > made this world a bit freer and better. > > The gap he leaves behind is huge and filling it will be hard. > > Thanks for everything dear Bill. It was a great honor and pleasure to > work with you. You will be remembered. We will miss you. Rest in peace. > > I express my condolences to Phyllis, his family and friends. > > Sam > > P.S.: Phyllis has expressed the wish to resume work on the project at a > later date, currently she needs some time off, and to participate in the > documentation and correspondence as usual. I will continue to support > this project as before. The monthly releases cannot be offered in the > same way at the moment. Minor changes and improvements will take place > from time to time. We are open for new developers and hope for your > support. > -- > Cin mailing list > Cin(a)lists.cinelerra-gg.org > https://lists.cinelerra-gg.org/mailman/listinfo/cin > >

1 0

Re: [Cin] Sad news: Our developer Good Guy has passed away
by daniel-cinelerra-gg＠opayq.com 09 Nov '20

09 Nov '20

so sorry to hear about this. what a generous person he was. is there anything we can do for phyllis, the family or for anyone directly involved or for the project itself? dan > On 11/10/2020 12:00 AM edouard chalaron via Cin <> wrote: > > > > Preview: What a tragedy. A very sad day indeed ! All my thoughts to Ph --> SPAM? CLICK to BLOCK https://dnt.abine.com/#/block_email/daniel-cinelerra-gg@opayq.com/ > > This email is Masked using Blur - it was sent from lists.cinelerra-gg.org to daniel-cinelerra-gg(a)opayq.com (your reply stays Masked). To protect your privacy https://www.abine.com/faq.html#caniaddcc , do not forward this message, or add new recipients like CCs or BCCs. > > Thanks for being a Blur customer! If you haven't yet, [ Try DeleteMe at a discount. https://joindeleteme.com/?utm_source=blur&utm_medium=email&utm_campaign=blu… ] > > > What a tragedy. A very sad day indeed ! > All my thoughts to Phyllis and family > Ed > > Sent from Yahoo Mail on Android https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_And… > > > > > On Tue, Nov 10, 2020 at 8:57, Sam via Cin > > <cin(a)lists.cinelerra-gg.org> wrote: > > > > > > It is with dismay and sadness that I have to announce this devastating > > news that our highly esteemed developer W.P. Morrow aka Good Guy died in > > a traffic accident last Monday at the age of 66. Bill, as he also called > > in private, was as so often in his free time, out for sports riding his > > bicycle when he was hit by a truck. He was taken to hospital, but > > unfortunately he succumbed to his severe injuries. > > > > This news is shocking and makes me speechless, although I find it > > extremely difficult to find words due to my sadness, I would like to > > remember him at this point. > > > > A look back shows that, together with Phyllis, he has pushed this > > project forward with great passion, dedication and commitment. His > > ingenuity and creative solutions were always an enrichment for this > > project. He was never too comfortable to tackle even small problems and > > improvements to make the life of the users easier. You could tell that > > he enjoyed programming a lot. He enjoyed improving Cinelerra-GG and > > interacting with the community. He has acted selflessly and for the good > > of all, and through his commitment to free and open software, he has > > made this world a bit freer and better. > > > > The gap he leaves behind is huge and filling it will be hard. > > > > Thanks for everything dear Bill. It was a great honor and pleasure to > > work with you. You will be remembered. We will miss you. Rest in peace. > > > > I express my condolences to Phyllis, his family and friends. > > > > Sam > > > > P.S.: Phyllis has expressed the wish to resume work on the project at a > > later date, currently she needs some time off, and to participate in the > > documentation and correspondence as usual. I will continue to support > > this project as before. The monthly releases cannot be offered in the > > same way at the moment. Minor changes and improvements will take place > > from time to time. We are open for new developers and hope for your > > support. > > -- > > Cin mailing list > > Cin(a)lists.cinelerra-gg.org mailto:Cin@lists.cinelerra-gg.org > > https://lists.cinelerra-gg.org/mailman/listinfo/cin > > > > > > > > -- > Cin mailing list > Cin(a)lists.cinelerra-gg.org > https://lists.cinelerra-gg.org/mailman/listinfo/cin >

1 0

Re: [Cin] Removal of AVStream.*index_entries*
by Andrew Randrianasulu 06 Nov '20

06 Nov '20

В сообщении от Friday 06 November 2020 01:40:34 вы написали: > Quoting Andrew Randrianasulu (2020-11-05 17:53:51) > > В сообщении от Thursday 05 November 2020 14:57:22 вы написали: > > > Hi, > > > Quoting Andrew Randrianasulu (2020-10-30 21:23:22) > > > > Hello, Anton. > > > > > > > > Sorry for writing to you directly and not to ffmpeg-devel, I'm not subscribed to it (just reader via web interface). You can copy my email there if you want. > > > > > > > > In https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/cea7c19cda0ea1630ae1de8c102… you moved nb_index_entries to private header, yet as it turned out this code was used by CinelerraGG: > > > > > > > > https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerr… > > > > > > > > line 723 for example .. > > > > > > > > Do you have any alternative route for getting this info? > > > > I hacked sources of CinlerraGG a bit by directly including libavformat's internal header, but it was not very good idea becaiuse something conflicted when I added it to header file, and required alteration of yet another file even if I added it only to ffmpeg.C > > > > > > > > My hack attached ... > > > > > > frankly, that code looks like a horrible pile of hacks. I cannot, from a > > > quick glance, tell what is it using those private fields for and why it > > > doesn't just call avformat_seek_file() like any other well-behaved > > > program would. > > > > Good question. I think code 'evolved' this way, because this is > > non-linear video editor (so, playback/decoding position can jump > > randomly forward and backward). Also, some format seeks better than > > others. May be other editors work-around this problem differently. Or > > their users just adviced to avoid hard-to-edit formats. > > I think ffms2 <https://github.com/FFMS/ffms2> also operates under > similar constraints, but it does not access private fields. Maybe you > could draw some inspiration from there. Thanks, I compiled it once for Aegisub, and forgot about it :/ > > > > > Can I forward your question about this code to our mail list? > > Sure. I can also be reached on IRC in freenode/#ffmpeg-devel, if anyone > wants to discuss this further. > Forwarding ...

1 0