Re: [Cin] Fixed typo in my latest attempt at Russian translation

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 06 September 2020 04:25:39 Phyllis Smith via Cin 
написал(а):
> Andrew,
> Is it OK to add this in for the next release?

I guess only way to test it - is to put it in release and listen to complains 
of users 
(at least in Kbabel I can search for misspelled strings :})


> 
> On Sat, Sep 5, 2020 at 7:17 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > "Оистить" -> "Очистить".
> >
> > compile msgfmt ru-4.po -o cin.mo and put it for tests in
> > /usr/share/locale/ru/LC_MESSAGES
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Crash at fast 'z' (undo) for many-fade-keyframes?

[Andrew Randrianasulu via Cin]

I was playing with new bump autos, set some on fade curve, 
played with type of each keyframe point, and then decided to
remove them all by hitting 'z' fast. This resulted in:

 cin
Cinelerra Infinity - built: Aug 31 2020 05:07:06
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

RenderFarmClient::main_loop: client started
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
Mutex::lock: Resource temporarily unavailable
Mutex::unlock: Invalid argument
** segv at 0xf6a2d558 in pid 3994, tid 4011
writing debug data to /tmp/cinelerra_3994.dmp
lock_items: 19
lock_frees: 6
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
** dump complete
Ошибка сегментирования

Dump attached
** segv at 0xf6a2d558 in pid 3994, tid 4011
created on Mon Aug 31 15:26:53 2020
by 1000:100 guest()

OS:

CPUS: 4

CPUINFO:
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 21
model   : 2
model name  : AMD FX(tm)-4300 Quad-Core Processor
stepping: 0
microcode   : 0x6000852
cpu MHz : 2599.151
cache size  : 2048 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 16
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf 
pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c 
lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch 
osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core 
perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid 

[Cin] Theme "bright" color inconsistence?

[Andrew Randrianasulu via Cin]

Hi, all!

User asked me how to make new themes for CinelerraGG. While I was unable to 
answer this question, I at least tried few themes more, and found theme 
"Bright" to have  too-coloriful (IMO, for mostly-b/w theme) icon for 
'locklablels'. I tried to GIMP them into something acceptable, but I literally 
can't make straight line (checkmark for activated icon) even with automatic 
line drawing!

Attached are png files I de-colorized. I uncheked all of 'exif' stuff in GIMP"s 
png export dialog - this made files smaller, and I also run 'optipng' over 
them, and compile-tested them:


root@slax:/dev/shm/tmp/cinelerra-goodguy-20200905/cinelerra-5.1/plugins/theme_bright#
 make clean && make

cp ../../bin/plugins/themes/theme_bright.plugin /usr/lib/cin/plugins/themes/

cin launched without libpng's CRC errors (I had some if I left GIMP to write 
exif to png, as it did by default). And those icons kinda ..less-coloriful now.

I think artistic user can start from copying existing theme and just modifying 
icons one by one, but what to do with hypothetical mytheme_theme.c and h  
files? They can remain the same if line colors not changed?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Few update profiles

[Andrew Randrianasulu via Cin]

I tried to update few mpeg4 (DivX) profiles for better quality.

div3
div3v2
div5 - 

added

trellis=1
mbd=bits

huffyuv_screencapture.mov added
cin_pix_fmt bgra (so it will be picked by 'pixels' chooser)

mjpeg_444.qt added
cin_pix_fmt yuvj444p (again, so it will be picked by Cinelerra's output encoder 
config dialog window)



div3.qt
Description: Binary data


div5.qt
Description: Binary data


huffyuv_screencapture.mov
Description: Binary data


div3v2.qt
Description: Binary data


mjpeg_444.qt
Description: Binary data
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Crash after I played with transitions

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 15 September 2020 02:45:52 Phyllis Smith via Cin 
написал(а):
> Andrew,
> Yes, it looks like a different crash, but that is OK -- we appreciate these
> crashes because we can find the cause and fix them before others report
> them years later.  Someone has to stress test better than I do.  Meanwhile
> GG has made some analysis on a 32-bit system and got a crash that may or
> may not be the same as what you had -- it seems that it is out of memory
> and the O/S does not warn Cinelerra.

I think I got same situation, but then Cin was killed by OOM killer for me...

Obvious solutions I can imagine:
Disable reverse playback/transition caches on 32-bit
Put caches on disc (configurable location), may be compressed with lz4/lzo

On this crash I'll try to uncheck transition cache manually and see if it goes 
away ...

> 
> On Mon, Sep 14, 2020 at 5:16 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > В сообщении от Tuesday 15 September 2020 01:51:45 Phyllis Smith via Cin
> > написал(а):
> > > Andrew, we have been trying to crash all day long and GG is now reverse
> > > engineering the assembly code in the dump on a 32-bit system -- that is
> > how
> > > desperate he is becoming !
> > > Hopefully, this additional dump, session file, and Cinelerra_rc will
> > help.
> > > So thanks.
> >
> > I'm really sorry for crashing Cin so hard. May be this is different crash
> > (much smaller video, rgba-8bit project format ...)
> >
> > Video file
> > https://cloud.mail.ru/public/4Xry/3gzFXHRGJ
> >
> >
> > >
> > > On Mon, Sep 14, 2020 at 4:28 PM Andrew Randrianasulu via Cin <
> > > cin@lists.cinelerra-gg.org> wrote:
> > >
> > > > Sorry, still crashing ..
> > > >
> > > > I cut video into four parts, each on its own track, and tried to add
> > some
> > > > transitions.
> > > > After I added circle ("shape wipe") and tried to play it back and
> > forth by
> > > > draggin vertical playback line - Cin crashed
> > > >
> > > > DRI_PRIME=1 LANG=ru_RU.utf8 cin
> > > > Cinelerra Infinity - built: Sep 14 2020 05:20:48
> > > > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > > > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > > > 2007-2020 mods for Cinelerra-GG 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.
> > > >
> > > > RenderFarmClient::main_loop: client started
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the
> > harbor.flv
> > > > FFMPEG::open_decoder: some stream times estimated:
> > > > /h

[Cin] Sorry, updated mpeg4 profiles again

[Andrew Randrianasulu via Cin]

This time using info from https://ffmpeg.org/faq.html
-
3.9 Which are good parameters for encoding high quality MPEG-4?
’-mbd rd -flags +mv4+aic -trellis 2 -cmp 2 -subcmp 2 -g 300 -pass 1/2’, things 
to try: ’-bf 2’, ’-mpv_flags qp_rd’, ’-mpv_flags mv0’, ’-mpv_flags skip_rd’. 



For msmpeg4 only +aic flag is valid

For  mpeg4 bot flags (+mv4+aic) are valid

I also tried AVC-Intra-100 encoding - slow on my machine, but apparently 
produces mp4?

mediainfo /dev/shm/avcintra100.mp4
General
Complete name: /dev/shm/avcintra100.mp4
Format   : MPEG-4
Format profile   : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size: 879 MiB
Duration : 1 min 5 s
Overall bit rate mode: Constant
Overall bit rate : 113 Mb/s
Writing application  : Lavf58.55.100

Video
ID   : 1
Format   : AVC
Format/Info  : Advanced Video Codec
Format profile   : High 4:2:2 Intra@L4.1
Format settings, CABAC   : No
Format settings, GOP : N=1
Codec ID : avc1
Codec ID/Info: Advanced Video Coding
Duration : 1 min 4 s
Bit rate mode: Constant
Bit rate : 114 Mb/s
Width: 1 920 pixels
Height   : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode  : Constant
Frame rate   : 25.000 FPS
Color space  : YUV
Chroma subsampling   : 4:2:2
Bit depth: 10 bits
Scan type: Progressive
Bits/(Pixel*Frame)   : 2.193
Stream size  : 878 MiB (100%)
Color range  : Limited
Color primaries  : BT.709
Transfer characteristics : BT.709
Matrix coefficients  : BT.709
Codec configuration box  : avcC

Audio
ID   : 2
Format   : AAC LC
Format/Info  : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1 min 5 s
Duration_LastFrame   : -16 ms
Bit rate mode: Constant
Bit rate : 129 kb/s
Channel(s)   : 2 channels
Channel layout   : L R
Sampling rate: 44.1 kHz
Frame rate   : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size  : 1 022 KiB (0%)
Language : Russian
Default  : Yes
Alternate group  : 1

Of course audio better to be PCM 
Can anyone check if this file edi(t)able by other video editors?




div3.qt
Description: Binary data


div3v2.qt
Description: Binary data


msmpeg4.avi
Description: Binary data


xvid.avi
Description: Binary data


div5.qt
Description: Binary data


AVC_Intra_100.mp4
Description: Binary data
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Single-frame step fwd/bak in viewer delayed?

[Andrew Randrianasulu via Cin]

I tried to re-create this lesson where you put in and out points in viewer, and 
then create clips and from them make your timeline.

I discovered that at least on highly-compressed mkv file ("Swimming with orca 
in New Zealand-JQ3mDXF3bcE.mkv") setting position cursor (in viewer window) at 
random place with mouse and then trying to use frame forward/frame backward 
buttons doesn't work: I need to click many times until it finally (after 
hitting codec keyframe?) started to advance. I tried to set cache to 1 Mb - 
from 250 or 768Mb - bug was still around.

Problem is - this is not just visual bug - rendered file also has this pause (I 
was surprized)

Cinelerra Infinity - built: Sep 14 2020 05:20:48 - hopefully latest git.

Anyone can confirm/deny?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Sorry, updated mpeg4 profiles again

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 01:06:18 Phyllis Smith via Cin 
написал(а):
> Andrew,
> Your changes + the new Intra... will be checked in later today (or soon).
> I tested all of them and they all worked but you know more about it then we
> do.

Unfortunately, not much (just was looking at checkboxes in Avidemux settings 
and tried to upscale verysmall video - http://samples.mplayerhq.hu/MPEG1/ where 
difference  in file size was obvious.

I also tried to create two new profiles mpeg1.mpeg and mpeg2.mpeg with those 
recommended settings in them, and mpeg1_mp2.mpeg as audio file (so you can mux 
mpeg1 streams with sound) - but not sure how useful they can be?

I also tried to create h264 flv, but swftool failed to merge it into swf, and I 
don't know any other open-source tool for merging/wrapping flv into swf

https://en.wikipedia.org/wiki/Flash_Video
https://stackoverflow.com/questions/45484607/how-to-properly-wrap-h264-into-flv-with-ffmpeg

Those two somewhat confusing, _I think_ flv muxer in ffmpeg can mux h264 in flv 
(for example for uploading to youtube/etc), but how useful this can be in 
real-life I don't know 

https://trac.ffmpeg.org/wiki/EncodingForStreamingSites

---
Encoding a file for streaming
 If your computer is too slow to encode the file on-the-fly like the example 
above then you can re-encode it first: 
$ ffmpeg -i input.mkv -c:v libx264 -preset medium -b:v 3000k -maxrate 3000k 
-bufsize 6000k \
-vf "scale=1280:-1,format=yuv420p" -g 50 -c:a aac -b:a 128k -ac 2 -ar 44100 
file.flv

 Then stream copy it to the streaming service: 
$ ffmpeg -re -i file.flv -c copy -f flv rtmp://live.twitch.tv/app/



> 
> I also tried AVC-Intra-100 encoding - slow on my machine, but apparently
> > produces mp4?
> >
> Yes, it produced mp4 and it was not slow on my laptop but I ran a very
> small file without audio.
> 
> >
> > Of course audio better to be PCM 
> > Can anyone check if this file edi(t)able by other video editors?
> >
>   I do not have MLV or any other video editor to test.  Maybe Andrea can
> after we check it in?
> 
> >
> >
> 




mpeg1.mpeg
Description: Binary data


flv_h264.flv
Description: Binary data


mpeg2.mpeg
Description: Binary data


mpeg1_mp2.mpeg
Description: Binary data
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Sorry, updated mpeg4 profiles again

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 03:52:23 Phyllis Smith via Cin 
написал(а):
> Andrew,
> I just noticed that the flv_h264.flv output file is so pixelated (original
> was 352x240) that I think it would only be useful on a small play device
> (lots of those around in phones these days). 

Try to set "quality" (in GUI) to somehting like "23" ?
or "b=300" in this small window where you can add ffmpeg options)

> And for some reason the 
> mpeg1_mp2.mpeg is now working so obviously I was doing something wrong
> originally.

I think just selecting some other output type momentary and then re-selecting 
desired type reload all those options?

> 
> On Tue, Sep 15, 2020 at 6:40 PM Phyllis Smith 
> wrote:
> 
> > Andrew,
> >
> > I also tried to create two new profiles mpeg1.mpeg and mpeg2.mpeg with
> >> those recommended settings in them, and mpeg1_mp2.mpeg as audio file (so
> >> you can mux mpeg1 streams with sound) - but not sure how useful they can 
> >> be?
> >>
> >> I also tried to create h264 flv, but swftool failed to merge it into swf,
> >> and I don't know any other open-source tool for merging/wrapping flv into
> >> swf
> >>
> > Well, I tried these 4 and the 3 seem to work and could be useful.  BUT
> > mpeg1_mp2.mpeg for audio just gives me the error message of:
> > libtwolame @ 0x7fffa0701f80] Specified channel layout '5.1' is not
> > supported
> > FFMPEG::open_encoder  err: Invalid argument
> > which I do not understand as I only had 2 channels.
> >
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 03 September 2020 04:43:51 Phyllis Smith via Cin 
написал(а):
> Andrew,  thanks for the suggestions on the following.
> 
> Please add this to known issues for this release?
> >
> I did add this to the releasenotes.pdf as it was too important to leave out.
> 
> 
> >
> > Also, documentation (pdf) is not up-to-date for now (file modification
> > from 9 aug 2020).
> >
> The manual is now updated on the website (includes Bump Autos and Selected
> Edits as added by Andrea).  Somehow I missed email of Andrea's rework for
> the Advanced Editing chapter and MatN's review.

Thanks A LOT for this - up-to-date documentatio definitely not easy task 
for fast-changing program!

downloaded it already.


> 
> >
> > > > Clear Keyframes (Shift+Del) do not delete the right keyframes.
> > > > Maybe it's too late for the monthy release but a bug I found. I don't
> > > > know if this bug is also in the last GIT release.
> > > > 1. Create three (or more) Fade keyframes
> > > > 2. Highlight an area to select one or more Fade keyframe
> > > > 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes
> > > > 4. It delete the wrong keyframes and move others.
> > > > (Note: Settings-> keyframes follow edits = checked)
> > > >
> > > > Take a look the screencast at
> > > > https://streamable.com/q58t37
> > > >
> >
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] August Monthly Builds now available on cinelerra-gg.org

[Andrew Randrianasulu via Cin]

В сообщении от Friday 04 September 2020 19:58:57 Phyllis Smith via Cin 
написал(а):
> Andrew,
> 
> Build for Rosa Linux (x86_64) completed:
> >
> > https://cloud.mail.ru/public/5kZr/5zuKPjpYJ
> >
> > You can find there rpm and debuginfo rpm files, sha256 checksums, and
> > updated Russian translation (but I did it at 5-7am, so be aware about
> > possible bugs!)
> >
> > 0eedc02bbd369b9fa32ba3cf49a2c868fe948bb8cd549248eb93cf3a188b21e5
> > cinelerra-5.1-20200831-rosa2016.1.x86_64.rpm
> > bee7ac827827fa42899dccc8709a7cde133d498cfaf193f7026b550169cbd7ae
> > cinelerra-debuginfo-5.1-20200831-rosa2016.1.x86_64.rpm
> >
> > Just wanted to let you know that in the August news on the website, I put
> a link to your Rosa Linux build.  Hope that is OK?
> 


Yes, I shared this link around already. Unfortunately my (very good) friend 
Vlad was unable to test it because for some reason his Rosa installation since 
2014 refused to update correctly, so he will resinstall it...
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Possible hack/idea for automatically workaround clearing wrong keyframes?

[Andrew Randrianasulu via Cin]

So, I looked into mainmenu.C and there I can see
(searching for ClearKeyframes)
 

int ClearKeyframes::handle_event()
{
 if( mwindow->session->current_operation == NO_OPERATION )
  mwindow->clear_automation();
 return 1;
}

and for "keyframes_follow_edits"
I see

keyframes_follow_edits->set_checked(mwindow->edl->session->autos_follow_edits);

so, may be save this state into tmp variable,  test this 
mwindow->edl->session->autos_follow_edits , 
and if set to 1 - clear temporarily before calling mwindow->clear_automation(); 
and restore
from tmp variable afterwards?

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)

[Andrew Randrianasulu via Cin]

В сообщении от Monday 31 August 2020 15:56:28 Igor BEGHETTO via Cin написал(а):
> Clear Keyframes (Shift+Del) do not delete the right keyframes.
> Maybe it's too late for the monthy release but a bug I found. I don't 
> know if this bug is also in the last GIT release.

I think bug still exist in latest (0678b17975f50a831fb8a1cda6baaa961e3b6de7) 
code,
at least if I try to cover all existing keyframes by highlighting them - they 
all disappear.

But if I only select 2-3 out of 4 - yes, remaining keyframes moved left, into 
higlighted region.

Thing is, because those keyframes represent change ... deleting only SOME of 
them will 
create new curve (default value in highlighted region, abruptly starting to 
climb to remaining keyframes
as  we move outside of highlighted region).

I mean, isn't this operation ought to *create* some keyframes in such case, 
too? 

> 1. Create three (or more) Fade keyframes
> 2. Highlight an area to select one or more Fade keyframe
> 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes
> 4. It delete the wrong keyframes and move others.
> (Note: Settings-> keyframes follow edits = checked)
> 
> Take a look the screencast at
> https://streamable.com/q58t37
> 
> Thanks! (Sorry for the late)
> 
> IgorBeg


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)

[Andrew Randrianasulu via Cin]

--  Пересланное сообщение  --

Тема: Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)
Дата: Понедельник 31 августа 2020
Отправитель: Andrew Randrianasulu 
Получатель:  cin@lists.cinelerra-gg.org

В сообщении от Monday 31 August 2020 15:56:28 Igor BEGHETTO via Cin написал(а):
> Clear Keyframes (Shift+Del) do not delete the right keyframes.
> Maybe it's too late for the monthy release but a bug I found. I don't 
> know if this bug is also in the last GIT release.

I think bug still exist in latest (0678b17975f50a831fb8a1cda6baaa961e3b6de7) 
code,
at least if I try to cover all existing keyframes by highlighting them - they 
all disappear.

But if I only select 2-3 out of 4 - yes, remaining keyframes moved left, into 
higlighted region.

Thing is, because those keyframes represent change ... deleting only SOME of 
them will 
create new curve (default value in highlighted region, abruptly starting to 
climb to remaining keyframes
as  we move outside of highlighted region).

I mean, isn't this operation ought to *create* some keyframes in such case, 
too? 

*update*

No, my thinking above was not useful here, but may be keyframes saved not as 
absolute pairs (distance from start of timeline, value), but as relative 
(delta) to 
previous keyframe values?

If so, 'delete keyframes' should recalculate this delta for next left keyframe 
outside of 
highlighted region relative to keyframe right before highlight started (if any).
And then apply those values to left (next) keyframe.

At least when it comes to automatization keyframes like fade, speed, etc.
Not sure how plugin automatization  should react.
 


> 1. Create three (or more) Fade keyframes
> 2. Highlight an area to select one or more Fade keyframe
> 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes
> 4. It delete the wrong keyframes and move others.
> (Note: Settings-> keyframes follow edits = checked)
> 
> Take a look the screencast at
> https://streamable.com/q58t37
> 
> Thanks! (Sorry for the late)
> 
> IgorBeg



---
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] BUG on Clear keyframes (CinGG-release by GIT 30Aug 2020)

[Andrew Randrianasulu via Cin]

В сообщении от Monday 31 August 2020 19:34:20 Phyllis Smith via Cin написал(а):
> Thanks Igor and Andrew for testing some more,
> GG was hoping to come up with a fast solution to get into the builds but
> unfortunately it is going to take a design change which needs a week to
> code and test.  So he decided it is better to do the builds and leave in a
> "known bug" instead of create an unknown one.  He says a workaround is to
> turn on/off "keyframes follow edits when this error could surface.

Yes ... this seems to work!
Please add this to known issues for this release?

Also, documentation (pdf) is not up-to-date for now (file modification from 9 
aug 2020).

May be wait few days or week before all this synced again? I'm not aware about 
any scripted automatic download/builders for CinGG outside your dev. machine ...

> 
> Sorry about this.  It is mostly my fault as I have been unable to test this
> major mod for bump autos.
> 
> On Mon, Aug 31, 2020 at 6:57 AM Igor BEGHETTO via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > Clear Keyframes (Shift+Del) do not delete the right keyframes.
> > Maybe it's too late for the monthy release but a bug I found. I don't
> > know if this bug is also in the last GIT release.
> > 1. Create three (or more) Fade keyframes
> > 2. Highlight an area to select one or more Fade keyframe
> > 3. Hit Shift+Del shortcut or Keyframes-> Clear Keyframes
> > 4. It delete the wrong keyframes and move others.
> > (Note: Settings-> keyframes follow edits = checked)
> >
> > Take a look the screencast at
> > https://streamable.com/q58t37
> >
> > Thanks! (Sorry for the late)
> >
> > IgorBeg
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Fast reverse playback crash in latest cinGG?

[Andrew Randrianasulu via Cin]

В сообщении от Monday 14 September 2020 05:23:06 Phyllis Smith via Cin 
написал(а):
> Andrew,
> Another day, another GIT checkin to fix caching in order to get speed
> improvements.  Only when you have time, if you do a new build and it still
> crashes, could you supply the media you use, a session file, and your
> preferences so we can reproduce the problem?  I have been testing without
> problems this afternoon and evening in forward, reverse, with transition,
> using X11 and lastly using OpenGL and it is always working for me.  Thanks.

It seems to work fine after reboot (was 10 days long uptime before this)

But here is file anyway:
https://cloud.mail.ru/public/CLQ7/4ev13oVMj

I set CinGG to project format with RGBA-float colorspace, and then moved fade 
slider for video track down to 70%
Then I set cursor to start and hit "fast normal playback". After it reached end 
of timeline I hit "fast reverse playback". After *this* finished I quickly 
randomly set  cursor on timeline few times, quite far from both start and end.

All worked.

May be issue was caused by already-filled VRAM/RAM (my biggest GPU only have 
1Gb of vram, and I had Seamonkey + Firefox all opened with openGL acceleration).

Thanks a lot for fast responce on all those issues!

> 
> On Sat, Sep 12, 2020 at 8:54 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > В сообщении от Saturday 12 September 2020 23:16:45 Phyllis Smith via Cin
> > написал(а):
> > > Andrew,
> > > I was able to get a hang, but not a crash, on my laptop using 4K Big Buck
> > > Bunny RGBA-float, playing fast reverse.  GG has checked into GIT a cache
> > > fix and now I can no longer get the hang.  When you have time, see if
> > this
> > > fixes the problem you encountered also -- he says there is a high
> > > probability that it will.
> >
> > Sorry, still crash, thistime on cursor reposition after fast rev. playback
> > finished:
> >
> > LANG=ru_RU.utf8 DRI_PRIME=1 cin
> > Cinelerra Infinity - built: Sep 13 2020 04:03:24
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> >
> > init plugin index: /usr/lib/cin/plugins
> > PluginFFilter::new_ffilter(overlay_opencl)
> >   err: Ошибка ввода/вывода
> > PluginFFilter::new_ffilter(xfade_opencl)
> >   err: Ошибка ввода/вывода
> > [openclsrc_742 @ 0xcc76f00] OpenCL source requires output dimensions to be
> > specified.
> > PluginFFilter::new_ffilter(openclsrc)
> >   err: Недопустимый аргумент
> > init lv2 index:
> > LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x16_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x32_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/latency_meter
> > LOAD: http://lsp-plug.in/plugins/lv2/limiter_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/limiter_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_stereo
> > LOAD: http://ls

Re: [Cin] [spam?] Re: Fast reverse playback crash in latest cinGG?

[Andrew Randrianasulu via Cin]

В сообщении от Monday 14 September 2020 07:52:07 Georgy Salnikov написал(а):
> On Mon, 14 Sep 2020, Andrew Randrianasulu via Cin wrote:
> 
> > Aw, no, sorry this time it crashed again (maybe having Seamonkey in
> > background makes this issue more visible)
> 
> There may be two additional methods of hunting such sporadic
> bugs/weaknesses. Where some rare bugs might become exposed.
> 
> 1) Try to run program on a very poor computer (a single core, few memory,
> economy graphic board, or may be even 32 bit platform).

I think I can do this!

I tried this file (720x400 , 25 fps, h264)

https://cloud.mail.ru/public/4TUh/4SXe5ec1a

LANG=ru_RU.utf8 DRI_PRIME=1 taskset -c 0 cin

taskset set cin to use only 1st CPU core.

DRI_PRIME=1 set cin to use my second (faster) GPU


cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 4.0 us.
  hardware limits: 1.40 GHz - 3.80 GHz
  available frequency steps: 3.80 GHz, 3.40 GHz, 2.60 GHz, 1.80 GHz, 1.40 GHz
  available cpufreq governors: ondemand, userspace
  current policy: frequency should be within 1.40 GHz and 3.80 GHz.
  The governor "userspace" may decide which speed to use
  within this range.
  current CPU frequency is 1.40 GHz (asserted by call to hardware).
  cpufreq stats: 3.80 GHz:15,48%, 3.40 GHz:5,42%, 2.60 GHz:6,62%, 1.80 
GHz:20,96%, 1.40 GHz:51,52%  (458934)

so, I set cpu frequency to lowest possible value.

Next I splice video in two, add 1v/2a tracks to proj, move second half under 
first, set play
from very beginning, add faders to both video tracks ...play/fast play 
back/forward, mouse jumps ...

After some time it _may_ crash. But unfortunately not now :(

I already use 32-bit userspace (including Cin) on top of x86_64 kernel.


> 
> 2) Try to run on as powerful as possible one, on many cores, lots of memory,
> high end graphics.

Well, GG have 128 CPU machine, hopefully this one powerful enough for exposing 
high end bugs :}

> 
> ___
> 
> Georgy Salnikov
> NMR Group
> Novosibirsk Institute of Organic Chemistry
> Lavrentjeva, 9, 630090 Novosibirsk, Russia
> Phone   +7-383-3307864
> Email   s...@nmr.nioch.nsc.ru
> ___
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Anyone with h264-enc capable Radeon?

[Andrew Randrianasulu via Cin]

Hi all!

I was looking into https://gitlab.freedesktop.org/mesa/mesa/-/issues/3540 and 
found something interesting.

Apparently, current driver hardcodes quality profile to SPEED, but those who 
interested in quality encoding might wat to play with other modes?


https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/radeon/radeon_vcn_enc_1_2.c

static void radeon_enc_op_speed(struct radeon_encoder *enc)
{
   RADEON_ENC_BEGIN(RENCODE_IB_OP_SET_SPEED_ENCODING_MODE);
   RADEON_ENC_END();
}

defined in 
https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/radeon/radeon_vcn_enc.h

#define RENCODE_IB_OP_SET_SPEED_ENCODING_MODE   
0x0106
#define RENCODE_IB_OP_SET_BALANCE_ENCODING_MODE 
0x0107
#define RENCODE_IB_OP_SET_QUALITY_ENCODING_MODE 
0x0108

I wonder what results will be if you change such setting?

May be something like Nouveau's use of env. variables can be copied if there is 
no way to express this via va-api ?

https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/nouveau/nouveau_video.c


 if (getenv("XVMC_VL")) 

just in our case it will be like, RADEON_ENC_QUALITY?

also, there are other interesting parameters related to quality. Might be worth 
experimenting with.

static void radeon_enc_quality_params(struct radeon_encoder *enc)
{
   enc->enc_pic.quality_params.vbaq_mode = 0;
   enc->enc_pic.quality_params.scene_change_sensitivity = 0;
   enc->enc_pic.quality_params.scene_change_min_idr_interval = 0;

   RADEON_ENC_BEGIN(enc->cmd.quality_params);
   RADEON_ENC_CS(enc->enc_pic.quality_params.vbaq_mode);
   RADEON_ENC_CS(enc->enc_pic.quality_params.scene_change_sensitivity);
   RADEON_ENC_CS(enc->enc_pic.quality_params.scene_change_min_idr_interval);
   RADEON_ENC_END();
}

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] I tried to build CinGG for Rosa, but it segfaults on startup ....

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 03 October 2020 01:31:30 Phyllis Smith via Cin 
написал(а):
> Andrew,
> GG was able to reproduce via:
> 
> #create a session with a "Disolve" transition; save backup; quit
> cd /path/cinelerra-5.1/bin/plugins/
> mv video/dissolve.plugin /tmp/.
> #restart cin5, and load from backup
> #Notice the message in the controlling terminal, same backtrace as dump
> # [Detaching after vfork from child process 16241]
> # The transition 'Dissolve' in file '/root/.bcast5/backup.xml' is not part
> of your installation of Cinelerra.
> # The project won't be rendered as it was meant and Cinelerra might crash.

Vlad explained his crash a bit more - it was new session with two different 
media files on same video track, he tried to add transition to them and Cin 
crashed at playing it 

Still a bit strange because modulo packaging bug all those plugin files should 
be installed in same places as before, and exactly those video transition 
plugins were not changed lately?

> 
> He has made a mod that reports the problem of the missing plugin_server
> plugin BUT it might not be checked into GIT for a day or 2.
> 
> On Fri, Oct 2, 2020 at 1:56 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > Dump attached.
> >
> > Files (rpm) themselves at
> >
> > https://cloud.mail.ru/public/4UHi/u7GSkKZp5
> >
> > Terminal output was:
> >
> > Cinelerra Infinity - built: Oct  1 2020 21:55:26
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> > init plugin index: /usr/lib64/cin/plugins
> > init lv2 index:
> > ** segv at 0xae5b88 in pid 11125, tid 11709
> > writing debug data to /tmp/cinelerra_11125.dmp
> > lock_items: 23
> > lock_frees: 8
> > ** dump complete
> > Ошибка сегментирования (слепок снят)
> >
> > From brief look it still tries to access some media files, I asked user
> > (Vlad) to try and tar up .bcast5 and then remove it altogether 
> >
> > It might provide some clue(s)? Waiting for archive from Vlad 
> >
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Cool stuff

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 18:26:07 Sam via Cin написал(а):
> Hi guys,
> 
> i have found an interesting video which shows how you can convert 
> footage with a lower FPS to a video with a much higher FPS without any 
> losses.

Not exactly this type of cools stuff, but I found interesting article:

https://www.collabora.com/news-and-blog/blog/2020/09/21/open-source-meets-super-resolution-part-1/

quote
Performance
Despite their great upscaling performance, deep learning backed 
Super-Resolution methods cannot be easily applied to real-world applications 
due to their heavy computational requirements. At Collabora we have addressed 
this issue by introducing an accurate and light-weight deep network for video 
super-resolution.

To achieve a good tradeoff between computational complexity and reproduction 
quality, we implemented a cascading mechanism on top of a standard network 
architecture, producing a light-weight solution. We also used a multi-tile 
approach in which we divide a large input into smaller tiles to better utilize 
memory bandwidth and overcome size constraints posed by certain frameworks and 
devices. Multi-tile significantly improves inference speed. This approach can 
be extended from single image SR to video SR where video frames are treated as 
a group of multiple tiles.

We designed our solution on top of the open-source Panfrost video driver, 
allowing us to offload compute to the GPU.

Coming up in Part 2 of this series, we'll take a deep dive into how our model 
works, and how you can use free, open source software to achieve a higher level 
of compression than existing video compression methods. Stay tuned!
---quote end

Might be interesting  read, waiting for second part!

PS: as far as I understand this "AI" thing actually just 'invent' a lot of 
specialized algorithms on the fly (while training) and then apply them if 
similar situation in image occurs ?



> 
> https://youtu.be/sFN9dzw0qH8
> 
> https://github.com/baowenbo/DAIN
> 
> The nice thing is that this software is free of charge. For my 
> commercial projects I mainly use Da Vinci Resolve and there is the same 
> possibility which I use again and again. This feature is great if you 
> want to create slow motion effects and you only have footage that was 
> created with a low FPS.  I don't know if one day this software will be 
> used for Cinelerra, but it would be a great feature to use. Maybe you 
> can transfer footage from Cinelerra to this tool with a mouse click and 
> transfer it back to Cinelerra after the rendering is finished? Even if 
> an integration would not be possible, you can use this tool independently.
> 
> Sam
> 
> P.S.: By the way, the problems with the language plugin and web site are 
> still bothering me, but a solution will surely be found soon.
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] I tried to build CinGG for Rosa, but it segfaults on startup ....

[Andrew Randrianasulu via Cin]

В сообщении от Monday 05 October 2020 10:54:21 Igor BEGHETTO via Cin написал(а):
> > I use new .bcast5 and can not reproduce a crash. 
> Probably I am Off Topic.
> Have I delete my "old" .bcast5? I have a few of presets there. Which of 
> those, can I save and, then, restore?
> Loading old projects and doing something a crash is occured.
> Thanks!

I think you can mv it as, say, .bcast6:

mv .bcast5 .bcast6

Then Cin will re-create it, and you can add your xml files one by one (from 
your backup dir .bcast6) until crash occur.



> 
> IgorBeg
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] ffmpeg.git.patch4 is not needed anymore?

[Andrew Randrianasulu via Cin]

В сообщении от Friday 16 October 2020 04:13:48 Phyllis Smith via Cin написал(а):
> Andrew,
> FINALLY, gg got rid of Patch 4 as you notified us August 26 (GIT update).
> Thanks so much for the notify and sorry for the long delay.

I see it was removed  for ffmpeg 4.3, yet I don't think this patch hit ffmpeg 
tree before 4.3 was branched?

> 
> for my usual rebuild of CinGG with ffmpeg.git I found ffmpeg.git.patch4
> > is not applicable anymore, and ffmpeg log list this commit:
> >
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] ffmpeg.git.patch4 is not needed anymore?

[Andrew Randrianasulu via Cin]

Hello, all!

for my usual rebuild of CinGG with ffmpeg.git I found ffmpeg.git.patch4
is not applicable anymore, and ffmpeg log list this commit:

https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/a7bd37927628df3672488e07f718b3549bea717d

avfilter/af_aformat: Add uninit function

so, i just moved this patch away from buildsystem for now.

sadly, bigger patch ffmpeg.git.patch2 (mpegts/blu-ray) also started to show at 
least one failure:

(as of ffmpeg commit 649a6969f75f2378c65768deb9debd325eb2fc7f):

root@slax:/dev/shm/tmp/cinelerra-goodguy-20200826/cinelerra-5.1/thirdparty/ffmpeg.git#
 cat ../src/_ffmpeg.git.patch2 | patch -p1
patching file libavformat/mpegtsenc.c
Hunk #1 succeeded at 57 (offset 1 line).
Hunk #2 succeeded at 78 (offset 1 line).
Hunk #3 succeeded at 93 (offset 1 line).
Hunk #4 succeeded at 109 (offset 1 line).
Hunk #5 succeeded at 218 (offset 1 line).
Hunk #6 succeeded at 238 (offset 1 line).
Hunk #7 succeeded at 260 (offset 3 lines).
Hunk #8 succeeded at 282 (offset 3 lines).
Hunk #9 succeeded at 295 (offset 3 lines).
Hunk #10 succeeded at 324 (offset 4 lines).
Hunk #11 succeeded at 676 (offset 28 lines).
Hunk #12 succeeded at 702 (offset 28 lines).
Hunk #13 succeeded at 742 (offset 28 lines).
Hunk #14 succeeded at 755 (offset 28 lines).
Hunk #15 succeeded at 814 (offset 28 lines).
Hunk #16 succeeded at 876 (offset 28 lines).
Hunk #17 succeeded at 1077 (offset 28 lines).
Hunk #18 succeeded at 1086 (offset 28 lines).
Hunk #19 succeeded at 1104 (offset 28 lines).
Hunk #20 succeeded at 1173 (offset 28 lines).
Hunk #21 succeeded at 1233 (offset 28 lines).
Hunk #22 succeeded at 1241 (offset 28 lines).
Hunk #23 succeeded at 1315 (offset 28 lines).
Hunk #24 succeeded at 1345 (offset 28 lines).
Hunk #25 succeeded at 1363 (offset 28 lines).
Hunk #26 succeeded at 1424 (offset 28 lines).
Hunk #27 succeeded at 1522 (offset 28 lines).
Hunk #28 succeeded at 1534 (offset 28 lines).
Hunk #29 FAILED at 1585.
Hunk #30 succeeded at 1644 (offset 28 lines).
Hunk #31 succeeded at 1789 with fuzz 1 (offset 85 lines).
Hunk #32 succeeded at 1843 (offset 85 lines).
Hunk #33 succeeded at 1857 (offset 85 lines).
Hunk #34 succeeded at 1925 (offset 86 lines).
1 out of 34 hunks FAILED -- saving rejects to file libavformat/mpegtsenc.c.rej

cat libavformat/mpegtsenc.c.rej
--- libavformat/mpegtsenc.c
+++ libavformat/mpegtsenc.c
@@ -1585,7 +1446,7 @@ static int mpegts_write_packet_internal(AVFormatContext 
*s, AVPacket *pkt)

 ret = avio_open_dyn_buf(_st->amux->pb);
 if (ret < 0)
-return ret;
+return AVERROR(ENOMEM);

 ret = av_write_frame(ts_st->amux, );
 if (ret < 0) {

I tried to make new patch (by manually adding missed chunk), but not tested it 
yet (attached)
diff --git a/libavformat/mpegtsenc.c b/libavformat/mpegtsenc.c
index 1687de74ad..bb486748a6 100644
--- a/libavformat/mpegtsenc.c
+++ b/libavformat/mpegtsenc.c
@@ -57,7 +57,8 @@ typedef struct MpegTSService {
 int sid;   /* service ID */
 uint8_t name[256];
 uint8_t provider_name[256];
-int pcr_pid;
+int64_t pcr, pcr_packet_timer, pcr_packet_period;
+int pcr_sid, pcr_pid;
 AVProgram *program;
 } MpegTSService;
 
@@ -77,11 +78,12 @@ typedef struct MpegTSWrite {
 MpegTSSection pat; /* MPEG-2 PAT table */
 MpegTSSection sdt; /* MPEG-2 SDT table context */
 MpegTSService **services;
-int64_t sdt_period; /* SDT period in PCR time base */
-int64_t pat_period; /* PAT/PMT period in PCR time base */
+int64_t sdt_packet_timer, sdt_packet_period;
+int64_t pat_packet_timer, pat_packet_period;
 int nb_services;
-int64_t first_pcr;
-int64_t next_pcr;
+int onid;
+int tsid;
+int64_t pcr, first_pcr, delay;
 int mux_rate; ///< set to 1 when VBR
 int pes_payload_size;
 
@@ -91,14 +93,14 @@ typedef struct MpegTSWrite {
 int service_type;
 
 int pmt_start_pid;
+int pcr_start_pid;
 int start_pid;
 int m2ts_mode;
-int m2ts_video_pid;
-int m2ts_audio_pid;
-int m2ts_pgssub_pid;
-int m2ts_textsub_pid;
+int64_t ts_offset;
 
-int pcr_period_ms;
+int reemit_pat_pmt; // backward compatibility
+
+double pcr_period;
 #define MPEGTS_FLAG_REEMIT_PAT_PMT  0x01
 #define MPEGTS_FLAG_AAC_LATM0x02
 #define MPEGTS_FLAG_PAT_PMT_AT_FRAMES   0x04
@@ -107,10 +109,8 @@ typedef struct MpegTSWrite {
 int flags;
 int copyts;
 int tables_version;
-int64_t pat_period_us;
-int64_t sdt_period_us;
-int64_t last_pat_ts;
-int64_t last_sdt_ts;
+double pat_period;
+double sdt_period;
 
 int omit_video_pes_length;
 } MpegTSWrite;
@@ -218,14 +218,15 @@ static int mpegts_write_section1(MpegTSSection *s, int tid, int id,
 /* mpegts writer */
 
 #define DEFAULT_PROVIDER_NAME   "FFmpeg"
-#define DEFAULT_SERVICE_NAME"Service"
+#define DEFAULT_SERVICE_NAME"Service01"
 
-/* we retransmit the SI info at this rate */
+/* we retransmit the SI info 

[Cin] minterpolate (Was: Re: ffmpeg.git.patch4 is not needed anymore?)

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 27 August 2020 10:54:38 Igor BEGHETTO via Cin 
написал(а):
> Hi Andrew!
> I don't understand nothing (really a little) of Linux and maybe I wrong 
> to write here.
> I don't know if you (Andrew) or GG can see, but is it possible to have 
> "minterpolate" option inside Cinelerra-gg? It is a filter of ffmpeg.
> Thank you!

I uncommented it in /usr/share/cin/ffmpeg/plugin.opts
and deleted rm ~/.bcast5/Cinelerra_plugins so plugin list was refreshed on next 
Cin start.

but I got crash as fast as I tried to drag it over selected video region on 
timeline:


DRI_PRIME=1 cin
Cinelerra Infinity - built: Aug 27 2020 01:56:06
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

RenderFarmClient::main_loop: client started
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
signal_entry: got SIGFPE my pid=23403 execution table size=0:
signal_entry: lock table size=27
0xe2ea530 VIconThread::draw_lock, VIconThread::run 0 0xed1ffb40
0xeb7c8d0 RecordSetChannel::change_channel, (null) 0xe5bfdb40
0xec88ff0 ChannelInfo::scan_lock, (null) 0xe53fcb40
0xec8bac0 SWindow::swin_lock, (null) 0xe4bfbb40
0xd9cc2b0 MWindow::run_lock, MWindow::run 0xf7b46dc0 *
0xecbccc0 MainIndexes::input_lock, MainIndexes::run 1 0xe33f8b40
0xeea24e0 BRenderThread::input_lock, BRenderThread::run 0xe1bf5b40
0xec8d5a0 BC_Repeater::pause_lock, BC_Repeater::run 0xe43fab40 0xf7b46dc0
0xd42ffa20 BC_Repeater::pause_lock, BC_Repeater::run 0xcbeffb40 0xeeb9fb40
0xcb59f310 BC_Repeater::pause_lock, BC_Repeater::run 0xcf565b40 0xeeb9fb40
0xe9b9950 PlaybackEngine::output_lock, PlaybackEngine::run 0xea7feb40
0xd993b70 BC_Synchronous::next_command, BC_Synchronous::run 0xdf3f0b40
0xea01cd0 ResourceThreadBase::draw_lock, ResourceThreadBase::run 0xe8dfeb40
0xea01ad0 ResourceThreadBase::draw_lock, ResourceThreadBase::run 0xe85fdb40
0xe8852d0 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xec1fdb40
0xea01b80 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xe75fbb40
0xd189dc90 BC_Xfer::Slicer::init, Slicer::run 0xd9be5b40
0xec8f160 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xe03f2b40
0xe1b5ce0 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xeeb9fb40
0xe71d650 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xe13f4b40
0xed53b50 BC_WindowBase::event_condition, BC_WindowBase::get_event 
0xdfbf1b40
0xe9bf3d4 Cinelerra, BC_WindowBase::dispatch_event 2 0xf7b46dc0 *
lock_items: 22
lock_frees: 5
BC_Trace::delete_temps: deleting 1 temp files
/tmp/cinelerra.cef7b377-a6bb-452b-9db9-116739130d42
SigHandler::signal_handler total files=0
Аварийный останов

> 
> IgorBeg
> 
> 
> Il 26/08/2020 22:01, Andrew Randrianasulu via Cin ha scritto:
> > Hello, all!
> >
> > for my usual rebuild of CinGG with ffmpeg.git I found ffmpeg.git.patch4
> > is not applicable anymore, and ffmpeg log list this commit:
> >
> > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/a7bd37927628df3672488e07f718b3549bea717d
> >
> > avfilter/af_aformat: Add uninit function
> >
> > so, i just moved this patch away from buildsystem for now.
> >
> > sadly, bigger patch ffmpeg.git.patch2 (mpegts/blu-ray) also started to show 
> > at least one failure:
> >
> > (as of ffmpeg commit 649a6969f75f2378c65768deb9debd325eb2fc7f):
> >
> > root@slax:/dev/shm/tmp/cinelerra-goodguy-20200826/cinelerra-5.1/thirdparty/ffmpeg.git#
> >  cat ../src/_ffmpeg.git.patch2 | patch -p1
> > patching file libavformat/mpegtsenc.c
> > Hunk #1 succeeded at 57 (offset 1 line).
> > Hunk #2 succeeded at

Re: [Cin] minterpolate (Was: [spam?] Re: Bump Autos + other checked into GIT)

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 27 August 2020 15:49:47 Andrea paz via Cin написал(а):
> I've tried to enable F_minterpolate: CinGG loads without errors, but
> when trying to put the plugin on the timeline, I crash without dump.
> In the terminal I have these lines:
> 
> signal_entry: got SIGFPE my pid=26964 execution table size=0:
> signal_entry: lock table size=34
> 0x55cff793d020 VIconThread::draw_lock, VIconThread::run 0 0x7f53217fa640
> 0x55cff82e76d0 CWindowTool::input_lock, CWindowTool::run 0x7f52b7fff640
> 0x55cff83231d0 BC_DialogThread::active_lock, BC_DialogThread::run
> 0x7f52b6ffd640 *
> 0x55cff8745100 RecordSetChannel::change_channel, (null) 0x7f5194ff9640
> 0x55cff8899b40 SWindow::swin_lock, (null) 0x7f518f7fe640
> 0x55cff8899670 ChannelInfo::scan_lock, (null) 0x7f518640
> 0x55cff66bcfa0 MWindow::run_lock, MWindow::run 0x7f53e8419800 *
> 0x55cff889a600 BC_Repeater::pause_lock, BC_Repeater::run
> 0x7f518e7fc640 0x7f53e8419800
> 0x7f52b02c9cd0 PlaybackEngine::output_lock, PlaybackEngine::run
> 0x7f5261ffb640
> 0x55cff8aadc80 MainIndexes::input_lock, MainIndexes::run 1 0x7f5182fe5640
> 0x7f53d152a030 BC_Repeater::pause_lock, BC_Repeater::run
> 0x7f5162fa5640 0x7f5388ff9640
> 0x7f53d0436290 BC_Repeater::pause_lock, BC_Repeater::run
> 0x7f51637a6640 0x7f5388ff9640
> 0x7f52b00028c0 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f52b6ffd640
> 0x55cff83fde20 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f51967fc640
> 0x55cff889e8f0 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f53ddcde640
> 0x55cff801c1a0 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f53dccdc640
> 0x55cff8ab29c0 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f53c77fe640
> 0x55cff831c880 PlaybackEngine::output_lock, PlaybackEngine::run
> 0x7f52b77fe640
> 0x55cff66bd810 BC_Synchronous::next_command, BC_Synchronous::run
> 0x7f53c67fc640
> 0x55cff83fd420 ResourceThreadBase::draw_lock,
> ResourceThreadBase::run 0x7f51f37fe640
> 0x55cff83fd750 ResourceThreadBase::draw_lock,
> ResourceThreadBase::run 0x7f51f2ffd640
> 0x55cff8324ec0 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f53e8419800
> 0x55cff7965390 BC_WindowBase::event_condition,
> BC_WindowBase::get_event 0x7f5388ff9640
> 0x7f538c0066c0 BC_Xfer::Slicer::init, Slicer::run 0x7f516ffbf640
> 0x7f538c006a50 BC_Xfer::Slicer::init, Slicer::run 0x7f516f7be640
> 0x7f538c006530 BC_Xfer::Slicer::init, Slicer::run 0x7f53adffb640
> lock_items: 26
> lock_frees: 8
> SigHandler::signal_handler total files=0

and under gdb:

Thread 83 "cin" received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xce8f4b40 (LWP 25922)]
0xf6c61b2b in __divdi3 () from /usr/lib/libgcc_s.so.1
(gdb) bt full
#0  0xf6c61b2b in __divdi3 () from /usr/lib/libgcc_s.so.1
No symbol table info available.
#1  0x095cc710 in ?? ()
No symbol table info available.
#2  0x094f7768 in ff_filter_activate ()
No symbol table info available.
#3  0x094faf47 in av_buffersink_get_frame ()
No symbol table info available.
#4  0x086676f2 in PluginFVClient::process_buffer(VFrame**, long long, double) ()
No symbol table info available.
#5  0x086753a3 in PluginServer::process_buffer(VFrame**, long long, double, 
long long, int) ()
No symbol table info available.
#6  0x087143cb in VAttachmentPoint::render(VFrame*, int, long long, double, 
int, int) ()
No symbol table info available.
#7  0x08721093 in VirtualVNode::render(VFrame*, long long, double, int) ()
No symbol table info available.
#8  0x087211c5 in VirtualVNode::render_as_module(VFrame*, VFrame*, long long, 
double, int) ()
No symbol table info available.
#9  0x0872100e in VirtualVNode::render(VFrame*, long long, double, int) ()
No symbol table info available.
#10 0x08720985 in VirtualVConsole::process_buffer(long long, int) ()
No symbol table info available.
#11 0x08726b61 in VRender::process_buffer(long long, int) ()
No symbol table info available.
#12 0x087270d2 in VRender::run() ()
No symbol table info available.
#13 0x087fe101 in Thread::entrypoint(void*) ()
No symbol table info available.
#14 0xf7be0f66 in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#15 0xf6ba6c36 in clone () from /lib/libc.so.6
No symbol table info available.

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Latest Cin fail to launch, boxblur plugin at fault?

[Andrew Randrianasulu via Cin]

terminal output 

cin
Cinelerra Infinity - built: Sep 29 2020 10:55:32
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

init plugin index: /usr/lib/cin/plugins
int PluginServer::open_plugin(int, Preferences *, EDL *, Plugin *):
PluginServer::open_plugin: load_obj /usr/lib/cin/plugins/boxblur.plugin = 
/usr/lib/cin/plugins/boxblur.plugin: undefined symbol: 
_ZN10BC_Tumbler11calculate_wEv
[frei0r_382 @ 0xdfbdec0] No filter name provided.
PluginFFilter::new_ffilter(frei0r)
  err: Недопустимый аргумент
PluginFFilter::new_ffilter(overlay_opencl)
  err: Ошибка ввода/вывода
PluginFFilter::new_ffilter(xfade_opencl)
  err: Ошибка ввода/вывода
[frei0r_src_728 @ 0xdfb9e40] No filter name provided.
PluginFFilter::new_ffilter(frei0r_src)
  err: Недопустимый аргумент
[openclsrc_744 @ 0xdfbdec0] OpenCL source requires output dimensions to be 
specified.
PluginFFilter::new_ffilter(openclsrc)
  err: Недопустимый аргумент
init lv2 index:
LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_mono
LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_stereo
LOAD: http://lsp-plug.in/plugins/lv2/compressor_lr
LOAD: http://lsp-plug.in/plugins/lv2/compressor_mono
LOAD: http://lsp-plug.in/plugins/lv2/compressor_ms
LOAD: http://lsp-plug.in/plugins/lv2/compressor_stereo
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_lr
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_mono
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_ms
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_stereo
LOAD: http://lsp-plug.in/plugins/lv2/expander_lr
LOAD: http://lsp-plug.in/plugins/lv2/expander_mono
LOAD: http://lsp-plug.in/plugins/lv2/expander_ms
LOAD: http://lsp-plug.in/plugins/lv2/expander_stereo
LOAD: http://lsp-plug.in/plugins/lv2/gate_lr
LOAD: http://lsp-plug.in/plugins/lv2/gate_mono
LOAD: http://lsp-plug.in/plugins/lv2/gate_ms
LOAD: http://lsp-plug.in/plugins/lv2/gate_stereo
LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x16_mono
LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x32_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_stereo
LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_stereo
LOAD: http://lsp-plug.in/plugins/lv2/latency_meter
LOAD: http://lsp-plug.in/plugins/lv2/limiter_mono
LOAD: http://lsp-plug.in/plugins/lv2/limiter_stereo
LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_mono
LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_stereo
LOAD: http://lsp-plug.in/plugins/lv2/mb_compressor_mono
LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_lr
LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_mono
LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_ms
LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_stereo
LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_lr
LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_mono
LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_ms
LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_stereo
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x12
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x12_do
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x24
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x24_do
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x48
LOAD: http://lsp-plug.in/plugins/lv2/multisampler_x48_do
LOAD: http://lsp-plug.in/plugins/lv2/oscillator_mono
LOAD: http://lsp-plug.in/plugins/lv2/phase_detector
LOAD: http://lsp-plug.in/plugins/lv2/profiler_mono
LOAD: http://lsp-plug.in/plugins/lv2/profiler_stereo
LOAD: http://lsp-plug.in/plugins/lv2/room_builder_mono
LOAD: http://lsp-plug.in/plugins/lv2/room_builder_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sampler_mono
LOAD: http://lsp-plug.in/plugins/lv2/sampler_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_compressor_mono
LOAD: http://lsp-plug.in/plugins/lv2/sc_compressor_ms
LOAD: http://lsp-plug.in/plugins/lv2/sc_compressor_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_expander_lr
LOAD: http://lsp-plug.in/plugins/lv2/sc_expander_mono
LOAD: http://lsp-plug.in/plugins/lv2/sc_expander_ms
LOAD: http://lsp-plug.in/plugins/lv2/sc_expander_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_gate_lr
LOAD: http://lsp-plug.in/plugins/lv2/sc_gate_mono
LOAD: http://lsp-plug.in/plugins/lv2/sc_gate_ms
LOAD: http://lsp-plug.in/plugins/lv2/sc_gate_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_limiter_mono
LOAD: http://lsp-plug.in/plugins/lv2/sc_limiter_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_mb_expander_lr
LOAD: http://lsp-plug.in/plugins/lv2/sc_mb_expander_mono
LOAD: http://lsp-plug.in/plugins/lv2/sc_mb_expander_ms
LOAD: http://lsp-plug.in/plugins/lv2/sc_mb_expander_stereo
LOAD: http://lsp-plug.in/plugins/lv2/sc_mb_gate_lr

Re: [Cin] Contents of yesterday's GIT checkin

[Andrew Randrianasulu via Cin]

В сообщении от Friday 25 September 2020 05:00:03 Phyllis Smith via Cin 
написал(а):
> Sorry for the big delay -- usually I let you know what was checked into GIT
> that same day.
> 
> Because currently existing downloadable 4K webm files when loaded into
> Cinelerra were no longer seekable, we backed down the dav1d library from
> 7.1 to 5.1. Unfortunately it took some time to discover this as it is not a
> widely used format in CinGG.  I also had trouble with "ffplay" of the one I
> tested.


Hm, this is sad. As far as I understand webm is subset of mkv (matroska), so 
may be finding root case(s) of mkvs unseekability will fix this too, eventually?

https://www.webmproject.org/about/faq/

The WebM file structure is based on the Matroska media container.


I have dav1d 0.6.0 as system library, will try to replicate seek issue locally.

> 
> Alpha is being set to 1 for background color always now – just a missing
> thing.
> 
> Render Farm hang fixes that were a consequence of a previous change a
> couple of weeks ago and was missed.
> 
> Render Farm “linger” is turned off and Render Farm usage will no longer
> send messages it does not know how to handle.
> 
> Pierre’s SEGV discovery on load project when in Create Resources Only mode
> BT #510 which was a result of using the wrong copy is now fixed.
> 
> Moved code of location where the background color was set -- just code
> cleanup.
> 
> Minor ru.po Russian translation provided by Andrew.
> 
> Fixed new Slider Bar resize problem I found in Histogram plugin.
> 
> MotionCV and MotionHV will no longer get built (but code still there). Too
> confusing for users and have some issues with anyway.
> 
> Added 1 new and 1 modified ffmpeg formats as provided by Andrew (flv_h264
> and ffv1.avi).
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latest Cin fail to launch, boxblur plugin at fault?

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 29 September 2020 17:18:16 Phyllis Smith via Cin 
написал(а):
> I can't be sure, but it looks like you have the plugin library from
> the previous build as the default plugin directory.  The tumbler
> widget was tweaked and the new interface has a few different
> decorated names for the entry points.  Any object that uses the
> tumbler has to be rebuilt.  If you are using a "system" install,
> then the /usr/lib*/cin/plugins directory has to be re-installed...
> It is generally a good idea to "make uninstall" before invoking
> "make install" so that all of the binaries are replaced when
> using the system build   If you are using a "user" build, the
> plugins are in the build/bin and they are current and usable.
> gg

Yeah, installpkg as opposed to upgradepkg did the trick (tried force-reindexing 
plugins too).

Sorry!

> 
> 
> On Tue, Sep 29, 2020 at 3:22 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> >
> > terminal output
> >
> > cin
> > Cinelerra Infinity - built: Sep 29 2020 10:55:32
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> >
> > init plugin index: /usr/lib/cin/plugins
> > int PluginServer::open_plugin(int, Preferences *, EDL *, Plugin *):
> > PluginServer::open_plugin: load_obj /usr/lib/cin/plugins/boxblur.plugin =
> > /usr/lib/cin/plugins/boxblur.plugin: undefined symbol:
> > _ZN10BC_Tumbler11calculate_wEv
> > [frei0r_382 @ 0xdfbdec0] No filter name provided.
> > PluginFFilter::new_ffilter(frei0r)
> >   err: Недопустимый аргумент
> > PluginFFilter::new_ffilter(overlay_opencl)
> >   err: Ошибка ввода/вывода
> > PluginFFilter::new_ffilter(xfade_opencl)
> >   err: Ошибка ввода/вывода
> > [frei0r_src_728 @ 0xdfb9e40] No filter name provided.
> > PluginFFilter::new_ffilter(frei0r_src)
> >   err: Недопустимый аргумент
> > [openclsrc_744 @ 0xdfbdec0] OpenCL source requires output dimensions to be
> > specified.
> > PluginFFilter::new_ffilter(openclsrc)
> >   err: Недопустимый аргумент
> > init lv2 index:
> > LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/compressor_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/expander_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/gate_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x16_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x32_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/latency_meter
> > LOAD: http://lsp-plug.in/plugins/lv2/limiter_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/limiter_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/loud_comp_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_compressor_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_ms
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_expander_stereo
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_lr
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_mono
> > LOAD: http://lsp-plug.in/plugins/lv2/mb_gate_ms
> > LOAD: http://lsp-plug.

Re: [Cin] Single-frame step fwd/bak in viewer delayed?

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 22 September 2020 21:42:39 Andrea paz via Cin написал(а):
> @Andrew
> I can't test your new ffv1.avi and flv_h264.flv; it gives me "error
> codec not found" and rendering doesn't start. Pierre, have you tried?
> Do they work for you?


Strange, while I usually build with ffmpeg.git, those codecs must be in bundled 
 4.3 too ...
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Single-frame step fwd/bak in viewer delayed?

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 23 September 2020 06:24:06 Pierre autourduglobe via 
Cin написал(а):
> @Andrea paz
> 
> The option to encode in ffv1 is not yet included in the list of codecs 
> offered with the avi container.
> 
> So I haven't tested it yet.


You can put those files into /usr/share/cin/ffmpeg/video/ and they should 
appear in Cin's encoder choices ... (after restart?)

> 
> Pierre
> 
> 
> Le 20-09-22 à 14 h 42, Andrea paz via Cin a écrit :
> > @Andrew
> > I can't test your new ffv1.avi and flv_h264.flv; it gives me "error
> > codec not found" and rendering doesn't start. Pierre, have you tried?
> > Do they work for you?
> > 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Small typo fix for ru.po, question

[Andrew Randrianasulu via Cin]

В сообщении от Monday 21 September 2020 22:15:42 Phyllis Smith via Cin 
написал(а):
> Dumb question here -- did you make the corresponding code changes?

No :} I was hoping just changing .po file will be enough 

> For example int plugins/crikey/crikeywindow.C, there is this line to make
> it all work:
>CriKeyDelPoint::CriKeyDelPoint(CriKeyWindow *gui, CriKey *plugin, int x,
> int y)
>  : BC_GenericButton(x, y, xS(80), *C_("Del")*)
> 
> On Mon, Sep 21, 2020 at 12:32 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > В сообщении от Monday 21 September 2020 20:38:38 Phyllis Smith via Cin
> > написал(а):
> > > Andrew,
> > >
> > > > I translated Del as Удалить yet this word appear in dropdown menu
> > > > (Edit->Clear-> Clear (Del) ... ) in main window, where (I think) it
> > > > shouldn't be translated. Can this be fixed by marking it  as
> > untraslatable?
> > > >
> > > > Yes, for example look in ru.po to see how the following are handled +
> > look
> > > at the code since a small code change is needed as explained below.  It
> > is
> > > easy to change and we did this at the request of IgorUbuntu as needed in
> > > the past.  But of course, you can supply the patch yourself.
> > >
> > > sketcherwindow#Del
> > > tracerwindow#Del
> > > crikeywindow#Del
> >
> > Like I did in attached file? (it seems to work, but I hope in other
> > instances it remain translated). Ah, no, in Shell Commands window Del also
> > remain Del (and not "Удалить")
> >
> > I tried to make two spearate sections in po file, but it doesn't work
> > either 
> >
> > #: cinelerra/binfolder.C:1635.
> > #: cinelerra/shbtnprefs.C:172
> > msgid "Del"
> > msgstr "Удалить"
> >
> > #: cinelerra/mainmenu.C:1012
> > msgid "mainmenu.C#Del"
> > msgstr ""
> >
> >
> >
> >
> > > This is documented in the Manual in the Translation chapter but it is a
> > > little difficult to comprehend -
> > >
> > > NOTE: some words and abbreviations can lead to ambiguous language trans-
> > > lations. Therefore, the usage of C_ and D_ in the program code was added
> > to
> > > represent Contextual and Definitional exceptions to the usual _ and N_ .
> > You
> > > will
> > > see the following:
> > >
> > > C_(“msgstr”) is translated to D_(“qual#msgstr”) by xlat.sh, and invokes
> > get-
> > > text with msgid = “qual#msgstr”
> > >
> > > When no po translation is supplied, the qual# is removed, and only the
> > > default
> > > msgstr text is displayed. If a po translation is defined for the current
> > > locale, then
> > >
> > > the translated msgid = “qual#msgstr” is used to access the translated
> > > msgstr.
> > >
> > > The default MSGQUAL is the basename of the C source file. For the file
> > > src_file.C,
> > >
> > > the default MSGQUAL is:
> > >
> > > # define MSGQUAL “src_file”
> > >
> > > It is used to define the qualifier needed to transform:
> > >
> > > C_(“str”) to D_(“src_file#str”)
> > >
> > > The resulting xlat.sh’d source is scanned by xgettext to create the
> > initial
> > > cin.po. In
> > > other words:
> > >
> > > _(s) does normal international text translation as always -
> > >
> > > The msgid line is: msgid “s”
> > >
> > > C_(s) makes it appear as if you used D_(“src_file#” s) -
> > >
> > > The msgid line is: msgid “src_file#s” If it does not translate, the
> > default
> > > msgtext is “s”, not “src_file#s”
> > >
> > > D_(qual#s) tries to look up _(qual#s).
> > >
> >
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Current (10 sep 2020) pdf manual has some pictures displaced?

[Andrew Randrianasulu via Cin]

В сообщении от Friday 18 September 2020 22:13:10 Andrea paz via Cin написал(а):
> Thank you for pointing this out; I attach the correction.
> 

Also, I think those are typos (misplaced space):

"Figure 16.4: Shows the Cakewalk theme (courtesy Olaf )on Preferences window 
with list of
themes"

p. 516

should be 

"Figure 16.4: Shows the Cakewalk theme (courtesy Olaf) on Preferences window 
with list of
themes"

"8.1 Automation Keyframes,/ Autos"

at p. 213 and in Index should be

"8.1 Automation Keyframes / Autos"

also, I think line under illustartion 10.4 at p. 243 is worng

it says "Figure 10.4: Screencast of the native Video plugins in the default 
Cinfinity icon set." but same text was for fig 10.1 on page 240

also, i think fig 10.8 ("Figure 10.8: Remove Deinterlace-CV plugin") on p.248 
can be moved up a bit, so it will be  visually inside same section

also, fig Figure 10.11: , = expander; "-" = options at p. 253 ..

I think something wrong with template: a lot of those illustrations are just 
visually in next section, and not where they should be (page vs section anchor?)

p. 369 Figure 10.76: Before and after YUVShift adjusting is in section "10.9.90 
Zoom Blur" as opposed to its own section "10.9.89 YUVShift"

at p. 470 "Figure 14.9: Subtitles on timeline" invaded section "14.4 Dvd 
Interlaced Chroma"

at p. 504 "Figure 16.2: Multi-screen Playback example useful for watching 
CINELERRA-GG run on the big screen" is visually in section "16.1.1 Audio Out 
section"

at p. 544 you probably should mention "Figure 18.1: Some windows used to 
manipulate Shell Commands scripts" somewhere in section text ?

at p. 563, I thing saying  "(Fig 19.2)" somewhere at the end of paragraph
==
19.7.2 Camera supplied LUTs
A LUT, acronym for Look-Up Table, is a mathematically precise way of taking spe-
cific RGB image values from a source image and modifying them to new RGB val-
ues by changing the hue, saturation and brightness values of that source image.
In other words, LUTs are used to map one color space to another. Some high-end
cameras supply a .cube file to use as input. There are several different ffmpeg
plugins included with CinGG for using Lut’s. These are:
=

will help? (image right after it, but with all this unwanted illustration 
wandering around ...)


May be all those will be autofixed by attached by Andrea  .tex file, but I know 
no way to test it without TeX installed 


I mean, may be it was design choice, but I prefer illustrations to be literally 
on the same page or in same section as txt referencing them, if possible 
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Current (10 sep 2020) pdf manual has some pictures displaced?

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 19 September 2020 17:59:38 Andrea paz via Cin 
написал(а):
> > I mean, may be it was design choice, but I prefer illustrations to be
> > literally on the same page or in same section as txt referencing them, if
> > possible 
> 
> Something can be done, but sometimes it lacks the space to let an
> image enter its section and the same page. This is the case of fig.
> 10.8 and 16.2, which I cannot fix.
> Latex works like this: we can give indications of where we want an
> image, but then it takes care of finding the best layout. It is one of
> the great advantages and convenience of Latex, but often the solution
> it finds is not good. Moreover, when you change or add something over
> time, the structure changes again every time you build the pdf.
> For example, I have arranged the figures you pointed out, but nothing
> prevents latex from changing their position again in the future. I
> have learned that the best solution is to intervene as little as
> possible, even if in truth I always find myself fixing something and
> then again and again.
> Keep reporting every issue, when you notice them: this finishing work
> is important.
> 

https://tex.stackexchange.com/questions/32598/force-latex-image-to-appear-in-the-section-in-which-its-declared
=
If you want the figure to float, but not passing a \section command. you can 
use the placeins package and its \FloatBarrier command beyond which floats may 
not pass. A package option allows you to declare that floats may not pass a 
\section command, but you can place \FloatBarriers wherever you choose.
==

may this link help?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] I tried to build CinGG for Rosa, but it segfaults on startup ....

[Andrew Randrianasulu via Cin]

Dump attached.

Files (rpm) themselves at

https://cloud.mail.ru/public/4UHi/u7GSkKZp5

Terminal output was:

Cinelerra Infinity - built: Oct  1 2020 21:55:26
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.
init plugin index: /usr/lib64/cin/plugins
init lv2 index:
** segv at 0xae5b88 in pid 11125, tid 11709
writing debug data to /tmp/cinelerra_11125.dmp
lock_items: 23
lock_frees: 8
** dump complete
Ошибка сегментирования (слепок снят)

From brief look it still tries to access some media files, I asked user (Vlad) 
to try and tar up .bcast5 and then remove it altogether 

It might provide some clue(s)? Waiting for archive from Vlad 


** segv at 0xae5b88 in pid 11125, tid 11709
created on Fri Oct  2 22:24:39 2020
by 500:500 vladimir(Vladimir)

OS:
NAME="ROSA Desktop Fresh R11.1"
VERSION="EE 2016.1 Desktop"
ID=rosa
VERSION_ID=2016.1
PRETTY_NAME="ROSA Desktop Fresh R11.1 EE 2016.1 Desktop"
ANSI_COLOR="1;43"
CPE_NAME="cpe:/o:rosa:rosalinux:2016.1"
HOME_URL="http://www.rosalinux.com/;
BUG_REPORT_URL="https://bugs.rosalinux.ru/;

CPUS: 4

CPUINFO:
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 4
model name  : AMD Phenom(tm) II X4 955 Processor
stepping: 3
microcode   : 0x1c8
cpu MHz : 2500.000
cache size  : 512 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 5
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid 
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy 
abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt 
lbrv svm_lock nrip_save
bugs: tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg 
amd_e400 spectre_v1 spectre_v2
bogomips: 6423.73
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor   : 1
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 4

THREADS:
thread 0x7f2311ffb700, owner 0x7f233b0d6700, 7VRender
thread 0x7f233b0d6700, owner 0x7f236a8a9700, 12RenderEngine
thread 0x7f22baffd700, owner 0x7f233b8d7700, 10DirectUnit
thread 0x7f23195da700, owner 0x7f233b8d7700, 10DirectUnit
thread 0x7f231a5dc700, owner 0x7f233b8d7700, 10DirectUnit
thread 0x7f23321c9700, owner 0x7f233b8d7700, 10DirectUnit
thread 0x7f231affd700, owner 0x7f237b20a700, 15BC_WindowEvents
thread 0x7f231b7fe700, owner 0x7f237a208700, 15BC_WindowEvents
thread 0x7f231bfff700, owner 0x7f2379a07700, 15BC_WindowEvents
thread 0x7f2330ff9700, owner 0x7f2379a07700, 11BC_Repeater
thread 0x7f23317fa700, owner 0x7f238e609f40, 15BC_WindowEvents
thread 0x7f2377a03700, owner 0x7f238e609f40, 11BC_Repeater
thread 0x7f2379206700, owner 0x7f23754be700, 15BC_WindowEvents
thread 0x7f2378a05700, owner 0x7f238e609f40, 10Playback3D
thread 0x7f2378204700, owner 0x7f237b20a700, 11BC_Repeater
thread 0x7f237bb4c700, owner 0x7f237a208700, 11BC_Repeater
thread 0x7f2379a07700, owner 0x7f238e609f40, 7GWindow
thread 0x7f237b20a700, owner 0x7f238e609f40, 11LevelWindow
thread 0x7f237aa09700, owner 0x7f23754be700, 11BC_Repeater
thread 0x7f237a208700, owner 0x7f238e609f40, 7CWindow
thread 0x7f23754be700, owner 0x7f238e609f40, 7AWindow
thread 0x7f233cff1700, owner 0x7f238e609f40, 12BC_Clipboard
thread 0x7f2341ffb700, owner 0x7f238e609f40, 11MainIndexes
thread 0x7f23427fc700, owner 0x7f238e609f40, 12BC_Clipboard
thread 0x7f234bfff700, owner 0x7f238e609f40, 11BC_Repeater
thread 0x7f2350fd9700, owner 0x7f238e609f40, 7SWindow
thread 0x7f23517da700, owner 0x7f238e609f40, 11ChannelInfo
thread 0x7f2351fdb700, owner 0x7f238e609f40, 13RecordChannel
thread 0x7f23527dc700, owner 0x7f23537de700, 15BC_WindowEvents
thread 0x7f2352fdd700, owner 0x7f23537de700, 11BC_Repeater
thread 0x7f23537de700, owner 0x7f238e609f40, 13RemoteControl
thread 0x7f2353fdf700, owner 0x7f238e609f40, 12BC_Clipboard
thread 0x7f2358fe9700, owner 0x7f238e609f40, 19ResourceVideoThread
thread 0x7f23597ea700, owner 0x7f238e609f40, 19ResourceAudioThread
thread 0x7f2359feb700, owner 0x7f238e609f40, 12BC_Clipboard
thread 0x7f235eff5700, owner 0x7f236a0a8700, 15BC_WindowEvents
thread 0x7f235f7f6700, owner 0x7f236a0a8700, 11BC_Repeater
thread 0x7f235fff7700, owner 0x7f236a0a8700, 9VPlayback
thread 0x7f23607f8700, owner 0x7f236a0a8700, 12BC_Clipboard
thread 

[Cin] What exactly happens with av1 video seeking?

[Andrew Randrianasulu via Cin]

I see dav1d revert [1] in CinGG tree but no specific explanation given? Was it 
issue only with ffmpeg 4.3 and self-generated media, or was it seen on pre-made 
samples/youtube downloads?

[1] - 
https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=commit;h=abdff69b9309c7d5cd2ed6ce17dd2e0d85aef9a1
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Crash after I played with transitions

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 15 September 2020 01:51:45 Phyllis Smith via Cin 
написал(а):
> Andrew, we have been trying to crash all day long and GG is now reverse
> engineering the assembly code in the dump on a 32-bit system -- that is how
> desperate he is becoming !
> Hopefully, this additional dump, session file, and Cinelerra_rc will help.
> So thanks.

I'm really sorry for crashing Cin so hard. May be this is different crash (much 
smaller video, rgba-8bit project format ...)

Video file
https://cloud.mail.ru/public/4Xry/3gzFXHRGJ


> 
> On Mon, Sep 14, 2020 at 4:28 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > Sorry, still crashing ..
> >
> > I cut video into four parts, each on its own track, and tried to add some
> > transitions.
> > After I added circle ("shape wipe") and tried to play it back and forth by
> > draggin vertical playback line - Cin crashed
> >
> > DRI_PRIME=1 LANG=ru_RU.utf8 cin
> > Cinelerra Infinity - built: Sep 14 2020 05:20:48
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> >
> > RenderFarmClient::main_loop: client started
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Flipper, Norwegian Dolphin chilling in the harbor.flv
> > FFMPEG::open_decoder: some stream times estimated:
> > /hom

Re: [Cin] Sorry, updated mpeg4 profiles again

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 15:48:04 Andrea paz via Cin 
написал(а):
> >   I do not have MLV or any other video editor to test.  Maybe Andrea can 
> > after we check it in?
> >>
> 
> Try various renderings:
> 
> div3 --> 40 fps
> div3v2 --> 41
> div5 --> 68
> AVC_Intra --> ERROR [libx264 @ 0x7fdda80c8b40] FPS 30/1p not
> compatible with AVC-Intra


https://en.wikipedia.org/wiki/AVC-Intra
Common to both classes; 
Frame rates: 1920 × 1080 (23.98p / 25p / 29.97p / 50i / 59.94i), 1280 × 720 
(23.98p / 25p / 29.97p / 50p / 59.94p)

yeah, it seems exact 30 fps is not specified :(

> msmpeg4 --> 40
> xvid --> 63
> 
> The default settings are low quality.
> I currently have no other NLEs installed (I cannot get DaVinci Resolve
> to work with AMD).
> The files produced work well in VLC and MPV.


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Single-frame step fwd/bak in viewer delayed?

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 11:21:32 Andrea paz via Cin 
написал(а):
> I gave up using mkv because it always gave me seek problems (see BT
> #137). I tried to use Transcode and got new mkv, but it doesn't solve
> the problem. I tried to use mkvtoolnix (which was created just for
> these problems) but I didn't solve the problem. In the latter case,
> however, it could be my fault that I don't know how to use the program
> well.
> Sorry to leave this container because it is the only one using ffv1,
> which is a (better) alternative to ProRes and DNxHD. But it is really
> too problematic. In my ignorance I ask: can you bring ffv1 (and opus,
> flac, etc) under mov or other container


Maybe avi will work (with usual avi limitations)?

https://natron.readthedocs.io/en/rb-2.3/plugins/fr.inria.openfx.WriteFFmpeg.html

--
Output format/container.
guess from filename (default)
AVI (Audio Video Interleaved) [avi] (avi): Compatible with ayuv, cinepak, ffv1, 
ffvhuff, flv, h263p, huffyuv, jpeg2000, jpegls, ljpeg, mjpeg, mpeg2video, 
mpeg4, msmpeg4v2, msmpeg4, png, svq1, targa, v308, v408, v410, vc2, 
libopenjpeg, libtheora, libvpx, libvpx-vp9, libx264, libx264rgb, libxvid, 
libopenh264.
---

also recommended here:
http://download.das-werkstatt.com/pb/mthk/info/video/FAQ-digital_video_archiving.html


Q: What are the pros and cons regarding these video formats for archiving?
container
video-codec
audio-codec
1.  MXF  JPEG2000  PCM (uncompressed)
  2.  MXF  Uncompressed  PCM (uncompressed)
  3.  MOV  ProRes  PCM (uncompressed)
  4.  MKV  FFV1  PCM (uncompressed)
  5.  AVI  FFV1  PCM (uncompressed)
   
 This answer is so long, that we've put a detailed comparison of the "usual 
suspects" on its own page: Comparing video codecs and containers for archives 
Q: Which audio/video codecs does the Mediathek use?
 For captured material, we use FFV1 for video and uncompressed PCM for audio. 
Audio resolution depends on the source material, but analogue sources are 
captured using 48kHz 24bit, as this is the SDI standard.
 
 "Born digital" material, coming in as a file already, is a whole different 
story. Please read up on born digital details, below. 
Q: Which container does the Mediathek use?
 We use AVI (Audio Video Interleaved).
 
 Almost every application that has to do with video can handle AVI files. 
Ranging from Free Software (Open Source) to proprietary tools, professional and 
consumer alike. It has a quite limited set of features, but this is also a main 
feature for long-term preservation: simple = robust. 
 Also: more features = more possible points of failure. Some archives argue the 
case for containers with complex features, but do not acknowledge the dangers 
accompanying this decision: the more features a container has, the more 
possible points of failure are added to your archive copy. Keeping this in 
mind, we made our decision for a simple container. 
 In practice, we've had almost no interoperability issues with using AVI across 
different tools from different vendors. Even across different operating system 
platforms. 
 We currently do not yet know of any other container that is so widely and 
stably supported.

===end of quotation
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Error compiling .tex to pdf

[Andrew Randrianasulu via Cin]

Hi all!

I installed texlive for Slackware and additional fonts (on another partition 
due to its size, mounted with -obind), and Kile 1.9.3 (KDE3 TeX editor).

Now when I try to compile documentation I get:

/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
declaration has incorrect series value `mc'.
/usr/share/texmf-dist/tex/latex/mathdesign/mdbch/mdbch.sty:186:Font 
T1/mdbch/m/n/12=mdbchr8t at 11.52008pt not loadable: Metric (TFM) file not 
found. \renewcommand{\rmdefault}{mdbch}\rmfamily
/usr/share/texmf-dist/tex/latex/mathdesign/mdbch/mdbch.sty:186:pdfTeX error 
(font): invalid font identifier. \renewcommand{\rmdefault}{mdbch}\rmfamily

even if I have 

find /usr/share/texmf-dist/ -name mdbchr8t*
/usr/share/texmf-dist/fonts/vf/public/mathdesign/mdbch/mdbchr8t.vf
/usr/share/texmf-dist/fonts/tfm/public/mathdesign/mdbch/mdbchr8t.tfm

I tried to run mktexlsr (as root):

mktexlsr
mktexlsr: Updating /usr/share/texmf-config/ls-R...
mktexlsr: Updating /usr/share/texmf-dist/ls-R...
mktexlsr: Updating /usr/share/texmf-local/ls-R...
mktexlsr: Updating /usr/share/texmf-var/ls-R...
mktexlsr: Done.

same error.

Any ideas?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Single-frame step fwd/bak in viewer delayed?

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 20 September 2020 17:05:37 Andrea paz via Cin написал(а):
> > Interesting... It would be enough to add in Cinelerra-GG the possibility
> > to use the ffv1 video codec to the list offered with the AVI container
> > for rendering and to make sure that these files (ffv1.avi) are then
> > readable and usable for editing in Cinelerra-GG.
> >
> > Pierre
> 
> +1
> I would like to ffv1 also inside .mov that doesn't have the
> limitations of .avi, but just for this could be more problematic.


I tried to add simple ffv1.avi file (use with avi_pcm_s16 sound)

It doesn't play smooth in CinGG for me (for 1080p/30 fps), but plays in Mplayer 
(but frame forward/backward seems to work in Cin, just slowly)

I also added cin_quality=23 to flv_h264.flv (now it gives 32 Mb / min for 
1080p/30 fps video - hopefully this quality is good for you too)



ffv1.avi
Description: Binary data


flv_h264.flv
Description: Binary data
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] [spam?] Error compiling .tex to pdf

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 20 September 2020 20:23:24 Georgy Salnikov написал(а):
> On Sun, 20 Sep 2020, Andrew Randrianasulu via Cin wrote:
> 
> > I installed texlive for Slackware and additional fonts (on another
> > partition due to its size, mounted with -obind), and Kile 1.9.3 (KDE3 TeX
> > editor).
> > Now when I try to compile documentation I get:
> > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape 
> > declaration has incorrect series value `mc'.
> 
> Several minutes before I tex'ed the manual from git under Slackware64-14.1
> and Texlive-2017 with pdflatex -- absolutely no problem!
> 
> I installed no additional fonts, but simply installed the complete Texlive.
> It was not Texlive for Slackware, it was just plain Texlive-CD from CTAN.
> And I do not know kile (emacs forever:).

Now I have output \o/ ...

https://cloud.mail.ru/public/2dSp/5uXXcmK3C (there should be pdf and various 
log files from compilation)

Probably I messed up my TeX install by manually unpacking various rpms and debs 
into it 

> 
> ___
> 
> Georgy Salnikov
> NMR Group
> Novosibirsk Institute of Organic Chemistry
> Lavrentjeva, 9, 630090 Novosibirsk, Russia
> Phone   +7-383-3307864
> Email   s...@nmr.nioch.nsc.ru
> ___
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Error compiling .tex to pdf

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 20 September 2020 21:10:05 Андрей Спицын via Cin 
написал(а):
> The overfull warning is a just info, that latex cant fit line into its
> borders. Its can be skipped if that line looks ok.
> The reference and labels warnings are important, it's indicates that some
> references are undefined, or labels used more than one time.

For now I only fixed (hopefully!) 'assetts' vs 'assets' in 
Editing.tex and Loadandsave.tex


> 
> The pdf looks the same after optimization, but it's better to ask Phyllis.
> 
> вс, 20 сент. 2020 г., 20:32 Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org>:
> 
> > В сообщении от Sunday 20 September 2020 20:03:10 Андрей Спицын via Cin
> > написал(а):
> > > Hi, Andrew!
> > > Indeed, very strange error. But you can bypass it by comment
> > > out renewcommand{\rmdefault}{mdbch}\rmfamily string. Although latex will
> > > use the default CM font.
> > >
> > > That texlive version you use? Can it be possible to update it?
> >
> > texlive-2020.200608-i586-2_SBo.txz
> > texlive-extra-2020.200608-i586-1_SBo.txz (but with fonts moved to separate
> > dir)
> > But when I run it (kile) from root it worked better, now I have huge log
> > file, still no pdf :/
> >
> > Ah, no, reinstalling both packages give me output!
> >
> > But A LOT of warnings too ... (log attached)
> >
> > I also optimized a bit png files by running optipng on them, do you think
> > this is safe procedure to do in main repo ? (just few mb less - > 57765K vs
> > 60487K)
> >
> >
> > >
> > >  --
> > > Best regards,
> > > Andrey
> > >
> > > вс, 20 сент. 2020 г., 18:57 Andrew Randrianasulu via Cin <
> > > cin@lists.cinelerra-gg.org>:
> > >
> > > > Hi all!
> > > >
> > > > I installed texlive for Slackware and additional fonts (on another
> > > > partition due to its size, mounted with -obind), and Kile 1.9.3 (KDE3
> > TeX
> > > > editor).
> > > >
> > > > Now when I try to compile documentation I get:
> > > >
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
> > > > declaration has incorrect series value `mc'.
> > > > /usr/share/texmf-dist/tex/latex/mathdesign/mdbch/mdbch.sty:186:Font
> > > > T1/mdbch/m/n/12=mdbchr8t at 11.52008pt not loadable: Metric (TFM) f

[Cin] frei0r plugins

[Andrew Randrianasulu via Cin]

I tried to recompile CinGG's version of ffmpeg with those plugins enabled:

FFMPEG_EXTRA_CFG="--enable-frei0r" (I have frei0r plugins 1.7.0 installed) and 
after tweaking  /usr/share/cin/ffmpeg/plugin.opts (added frei0r 
filter_name=vignette at very end of it) I can see this plugin and even use some 
effects. But not sure where  to find exact documentation for all those 
parameters?

https://ffmpeg.org/ffmpeg-filters.html#frei0r-1
-

Apply the colordistance effect, taking a color as the first parameter: 
frei0r=colordistance:0.2/0.3/0.4
frei0r=colordistance:violet
frei0r=colordistance:0x112233

 Apply the perspective effect, specifying the top left and top right image 
positions: 
frei0r=perspective:0.2/0.2|0.8/0.2
-

I tried those two and few others (list at the end), they worked, but their 
configuration a bit unintuitive 

List of working effects:
colordistance - works
edgeglow - works
glow - works
bw0r.- works
posterize - work
vignette. - work
sobel - work
perspective -- work
emboss - works
sharpness. - works
colorize. - works
contrast0r.  - works
squareblur.  - works
brightness. - works
threshold0r. - works (try 0.6 as parameter)
equaliz0r - works
glitch0r. - works (try 1 as param)
gamma. - works
pr0file. - works
invert0r - works
cartoon.  - works
pr0be.  - works
saturat0r - works (try 3)
dither. - works (try 0.8)
primaries - works
colortap - works (not sure how to use it)
luminance. - works?
hqdn3d - works ?
twolay0r. - seems to work ?
rgbnoise - works
sopsat - works (try 0.1)
ndvi - works
nervous - works (motion effect)
colortap - works
c0rners.  - works 
vertigo. - works
softglow - works
spillsupress.  - works (not sure what it does)
normaliz0r - works
tint0r - seems to work (not sure how it was supposed to look)
nosync0r/distort0r - not sure how to use them?
hue - works ?

Site seems to be 

https://www.dyne.org/software/frei0r/ , it even says

  Frei0r is the result of a collective effort in coordination with several 
software developers meeting at Piksel between 2003 and 2005 to find a common 
standard for video effect plugins to be used among their applications: Andraz 
Tori (Cinelerra/CVS), [..]
=

so, huh :}
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Cool stuff

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 18:26:07 Sam via Cin написал(а):
> Hi guys,
> 
> i have found an interesting video which shows how you can convert 
> footage with a lower FPS to a video with a much higher FPS without any 
> losses.
> 
> https://youtu.be/sFN9dzw0qH8
> 
> https://github.com/baowenbo/DAIN

---
Requirements and Dependencies
Ubuntu (We test with Ubuntu = 16.04.5 LTS)
Python (We test with Python = 3.6.8 in Anaconda3 = 4.1.1)
Cuda & Cudnn (We test with Cuda = 9.0 and Cudnn = 7.0)
PyTorch (The customized depth-aware flow projection and other layers require 
ATen API in PyTorch = 1.0.0)
GCC (Compiling PyTorch 1.0.0 extension files (.c/.cu) requires gcc = 4.9.1 and 
nvcc = 9.0 compilers)
NVIDIA GPU (We use Titan X (Pascal) with compute = 6.1, but we support 
compute_50/52/60/61 devices, should you have devices with higher compute 
capability, please revise this)


quite a lot of Nvidia dependencies :}

But may be someone will port it to OpenCL ...someday.

Thanks anyway!

> 
> The nice thing is that this software is free of charge. For my 
> commercial projects I mainly use Da Vinci Resolve and there is the same 
> possibility which I use again and again. This feature is great if you 
> want to create slow motion effects and you only have footage that was 
> created with a low FPS.  I don't know if one day this software will be 
> used for Cinelerra, but it would be a great feature to use. Maybe you 
> can transfer footage from Cinelerra to this tool with a mouse click and 
> transfer it back to Cinelerra after the rendering is finished? Even if 
> an integration would not be possible, you can use this tool independently.
> 
> Sam
> 
> P.S.: By the way, the problems with the language plugin and web site are 
> still bothering me, but a solution will surely be found soon.
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Current (10 sep 2020) pdf manual has some pictures displaced?

[Andrew Randrianasulu via Cin]

Hello!

I was just looking into Manual, and found 

"Figure 13.16: A Tablet with Android Remote Control" currently visually in 
section  "13.3 The commercial DB", p. 440 instead of p 439.

Also, on p.446 I can read

"13.4.1  Use Case #1 – EasyCap Model # DC60
A very specific case using an Easy CAPture USB 2.0 Video Adapter with Audio,
Model #DC60 (supports NTSC and PAL) is shown here next. The setup for this
device is seen in figure 13.21. A somewhat unusual choice to make note of in this

^^

shouldn't it be figure 13.20 ? where I can see CinGG windows, and not just 
external view of devices .

There might be others I overlooked
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Deleting "CompressorMulti" from playing audio track lead to crash?

[Andrew Randrianasulu via Cin]

I played with some effects.

Loaded my usual video (mkv)
Then I added "CompressorMulti' to just one audio track (paused).
I hit play, it worked for some time, I bring up config window, then tried to 
delete effect while timeline was still playing. Crash (not very informative):

 PRI_PRIME=1 LANG=ru_RU.utf8 cin
Cinelerra Infinity - built: Sep 16 2020 10:46:53
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

RenderFarmClient::main_loop: client started
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
free(): invalid next size (fast)
Аварийный останов

Adding same effect to playing timeline also *may* results in crash:

PRI_PRIME=1 LANG=ru_RU.utf8 cin
Cinelerra Infinity - built: Sep 16 2020 10:46:53
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

RenderFarmClient::main_loop: client started
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
FFMPEG::open_decoder: some stream times estimated: /home/guest/New_hdd/Swimming 
with orca in New Zealand-JQ3mDXF3bcE.mkv
free(): invalid next size (fast)
Аварийный останов

Attached are backup session file, compressormulti's settings file and 
Cinelerra_rc

PS: I wonder if real midi keyboard/soft synth can be used with Synthetizer 
plugin...
I also think Synth interface a bit large for 1440 screen, but not sure if 
anything can/should be done about this  (Other UI elements are OK, so 
global scaling probably not very good idea for me).
MWINDOWWIDTH 1432
MWINDOWHEIGHT 479
TOTAL_LOADS 10
TOTAL_AEFFECTS 0
TOTAL_VEFFECTS 0
FILEBOX_HISTORY_PATH0 /
FILEBOX_HISTORY_ID0 1655
FILEBOX_HISTORY_PATH1 /dev/
FILEBOX_HISTORY_ID1 1654
FILEBOX_HISTORY_PATH2 /dev/shm/
FILEBOX_HISTORY_ID2 1653
FILEBOX_HISTORY_PATH3 /home/
FILEBOX_HISTORY_ID3 1656
FILEBOX_HISTORY_PATH4 /home/guest/
FILEBOX_HISTORY_ID4 1705
FILEBOX_HISTORY_PATH5 /home/guest/botva/
FILEBOX_HISTORY_ID5 1666
FILEBOX_HISTORY_PATH6 /home/guest/botva/Downloads/
FILEBOX_HISTORY_ID6 1665
FILEBOX_HISTORY_PATH7 /home/guest/botva/Downloads/from_Vladimir/
FILEBOX_HISTORY_ID7 1664
FILEBOX_HISTORY_PATH8 /home/guest/botva/Downloads/from_Vladimir/Leningrad 
dolphinarium 16 09 2009/
FILEBOX_HISTORY_ID8 1663
FILEBOX_HISTORY_PATH9 /home/guest/Music/
FILEBOX_HISTORY_ID9 1470
FILEBOX_HISTORY_PATH10 /home/guest/Music/Nightwish/
FILEBOX_HISTORY_ID10 1467
FILEBOX_HISTORY_PATH11 /home/guest/New_hdd/
FILEBOX_HISTORY_ID11 1715
FILEBOX_HISTORY_PATH12 /home/guest/New_hdd/MLP_fan_fiction/
FILEBOX_HISTORY_ID12 1570
FILEBOX_HISTORY_PATH13 /home/guest/Nokia/
FILEBOX_HISTORY_ID13 1697
FILEBOX_HISTORY_PATH14 /home/guest/?? ? /
FILEBOX_HISTORY_ID14 1704
FILEBOX_HISTORY_PATH15 ?? ? /
FILEBOX_HISTORY_ID15 1702
FILEBOX_MODE 0
FILEBOX_W 948
FILEBOX_H 480
FILEBOX_TYPE0 0
FILEBOX_TYPE1 1
FILEBOX_TYPE2 2
FILEBOX_TYPE3 3
FILEBOX_WIDTH0 456
FILEBOX_WIDTH1 100
FILEBOX_WIDTH2 284
FILEBOX_WIDTH3 100
FILEBOX_FILTER [*.avi][*.mpg][*.m2v][*.m1v][*.mov] [*.mp4] [*.flv] [*.xml] 
[*.mkv] [*.mp3] [*.wav][*.MOV] [*.ogg] [*.MP3] [*.flac] 
[*.wmv][*.ARW][*.mov][*.avi][*.AVI][*.jpg][*.mj2][*.jp2][*.mxf][*.MLV][*.mlv][*.mkv][*.webm][*.png]
 [*.ts][*.bmp] [*.qt][*.exr*][*.m4a][*.prores]
ACHANNEL_ANGLE_0 180
ACHANNEL_ANGLE_1 0
ACHANNEL_ANGLE_2 0
ACHANNEL_ANGLE_3 0
ACHANNEL_ANGLE_4 0
ACHANNEL_ANGLE_5 0
ACHANNEL_ANGLE_6 0
ACHANNEL_ANGLE_7 0
ACHANNEL_ANGLE_8 0
ACHANNEL_ANGLE_9 0
ACHANNEL_ANGLE_10 0
ACHANNEL_ANGLE_11 0
ACHANNEL_ANGLE_12 0
ACHANNEL_ANGLE_13 0

Re: [Cin] Deleting "CompressorMulti" from playing audio track lead to crash?

[Andrew Randrianasulu via Cin]

В сообщении от Monday 21 September 2020 04:57:22 Phyllis Smith via Cin 
написал(а):
> Andrew,
> GG could not get this to crash.  I am still working on trying.  Was it a
> 32-bit system?

Yes

> 
> On Fri, Sep 18, 2020 at 9:49 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > I played with some effects.
> >
> > Loaded my usual video (mkv)
> > Then I added "CompressorMulti' to just one audio track (paused).
> > I hit play, it worked for some time, I bring up config window, then tried
> > to delete effect while timeline was still playing. Crash (not very
> > informative):
> >
> >  PRI_PRIME=1 LANG=ru_RU.utf8 cin
> > Cinelerra Infinity - built: Sep 16 2020 10:46:53
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> >
> > RenderFarmClient::main_loop: client started
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > free(): invalid next size (fast)
> > Аварийный останов
> >
> > Adding same effect to playing timeline also *may* results in crash:
> >
> > PRI_PRIME=1 LANG=ru_RU.utf8 cin
> > Cinelerra Infinity - built: Sep 16 2020 10:46:53
> > git://git.cinelerra-gg.org/goodguy/cinelerra.git
> > (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> > 2007-2020 mods for Cinelerra-GG 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.
> >
> > RenderFarmClient::main_loop: client started
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > FFMPEG::open_decoder: some stream times estimated:
> > /home/guest/New_hdd/Swimming with orca in New Zealand-JQ3mDXF3bcE.mkv
> > free(): invalid next size (fast)
> > Аварийный останов
> >
> > Attached are backup session file, compressormulti's settings file and
> > Cinelerra_rc
> >
> > PS: I wonder if real midi keyboard/soft synth can be used with Synthetizer
> > plugin...
> > I also think Synth interface a bit large for 1440 screen, but not sure if
> > anything can/should be done about this  (Other UI elements are OK, so
> > global scaling probably not very good idea for me).
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] frei0r plugins

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 16 September 2020 23:05:52 Phyllis Smith via Cin 
написал(а):
> Andrew, 88 plugins -- I wonder are there any that are so unique that CinGG
> should have them?

Some of them just duplicates of existing functionality 
but some are not. After all - ffmpeg handles them, CinGG can only add few more 
examples in documentation (and --with-frei0r configure switch to pass to 
ffmpeg's configure)


> 
> On Wed, Sep 16, 2020 at 11:19 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > I tried to recompile CinGG's version of ffmpeg with those plugins enabled:
> >
> > FFMPEG_EXTRA_CFG="--enable-frei0r" (I have frei0r plugins 1.7.0 installed)
> > and after tweaking  /usr/share/cin/ffmpeg/plugin.opts (added frei0r
> > filter_name=vignette at very end of it) I can see this plugin and even use
> > some effects. But not sure where  to find exact documentation for all those
> > parameters?
> >
> 
> Some are at (you have to scroll down to frei0r...)
>https://www.mltframework.org/plugins/PluginsFilters/

Thanks!

frei0r.delaygrab seems to produce cool effect :}

> 
> Site seems to be
> >
> > https://www.dyne.org/software/frei0r/
> 
> 
> I liked the way they spelled --  Miscro*$*oft / Win*doz*
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] OpenCL benchmarking ....

[Andrew Randrianasulu via Cin]

Hi all, and happy editing

Not VERY useful for CinelerraGG yet, still I found whole topic attractive 
enough :}

http://www.bealto.com/gpu-benchmarks_mem.html

I compiled benchmarks for my machine, with two simple fixes, and uploaded 
result to github:

 https://github.com/Randrianasulu/MPBenchmarks

IMO my current devices quite fast:

=
Host to device copy   223 424 771118217702147
240323782506250114901828 756 743 777 771
 776 708 683   0
 
Device to host copy   325 6131155197133204811
6282718880398316703954712817269531073256
322126342716   0
 
copyN 327 6511272218933004486
5419593261936266629963206330634563486349
63466335   0   0

For fastest NVA3 gpu (reclocked manually)

GPU<->GPU copy still slow .

https://gitlab.freedesktop.org/mesa/mesa/-/issues/3479

This is with very hacked mix of two experimental mesa branches ...

Master (mesa3d) doesn't support compute on nv50-era cards.

This bench requires images(2D) support, and works with OpenCL 1.1 driver

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Can 'play track' status propagate to ganged tracks?

[Andrew Randrianasulu via Cin]

В сообщении от Friday 23 October 2020 17:51:42 Phyllis Smith via Cin написал(а):
> IgorBeg:
> 
> We must remember what the goal of the "Gang Channels" was -- it was to
> ensure that the Audiophiles do NOT have to mark each and every audio track
> the exact same way which created mistakes.   They expect to turn off "Play
> track" and have none of the possibly 6 audio tracks playing -- else they
> would have to switch to "Gang None" mode, click on each of the 6 tracks to
> disable "Play track".  That is exactly what the Gang Channels mode was for
> to prevent this duplication.
> 
> I think that an User might just want to save space.
> > Sometimes I use Gang modes only for save space on the timeline, in my case
> > I use it for Video tracks.
> > And it may occur that I have to disable "Play track" on one or more Slave
> > tracks (an example may be Mixer Viewer, Multi Camera editing). So I have
> > the "Play track" of the Master Track enabled and all the "Play track" of
> > the Slave tracks disabled: with the new changes, it doesn't work anymore.
> > Like Andrea_paz wrote, is it possible to make this feature an option in
> > Preferences (or where you think better)?
> >
> 
> We will contemplate this today some more, but making it a Preference is not
> a good idea.
> 

May be yet another gang_mode? (this way it will be saved in user's session).

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] OpenCL benchmarking ....

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 24 October 2020 03:51:42 Phyllis Smith via Cin 
написал(а):
> Andrew,
> 
> > Not VERY useful for CinelerraGG yet, still I found whole topic attractive
> > enough :}
> >
> > http://www.bealto.com/gpu-benchmarks_mem.html
> >
> >
> Interesting benchmarks.  What I found a little puzzling was in the first
> graph where the Read and Write throughput is the same as I always thought a
> Read would be faster.
> 


Yeah, on hdd/ usb flash/ssd and related memory devices it usually like this - 
read is fast, but writing is less fast .. But this specific benchmark sometimes 
works with smaller sizes, so they fit into cache and thus work much faster than 
usual..  I also was quite sure read and write speeds even on RAM should be a 
bit different, but I guess I need to read more on this ...

In the meantime I found another becnhmark (apparently also requring OpenCL 1.1 
+ images), it doesn't work correctly for me on hacked nv92, but might be of 
some interest:

https://github.com/CRVI/OpenCLIPP
"OpenCLIPP - OpenCL Integrated Performance Primitives" - mostly from 2014 and 
last activity was in 2017 

I found it via https://www.iwocl.org/resources/opencl-libraries-and-toolkits/

As far as I understand scanline-based image processing doesn't fit very well to 
opencCL, but may be some plugins will benefit from it?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] x265 10/12 bit patch3 a bit reworked

[Andrew Randrianasulu via Cin]

I used advice from 

https://stackoverflow.com/questions/106387/is-it-possible-to-detect-32-bit-vs-64-bit-in-a-bash-script

and reworked my patch like this:

--- /dev/null   2020-07-19 09:07:01.788494015 +0300
+++ multilib.sh 2020-08-02 02:34:58.444933214 +0300
@@ -0,0 +1,54 @@
+#!/bin/sh
+
+mkdir -p 8bit 10bit 12bit
+
+
+cd 12bit
+if [ $(uname -m) == 'x86_64' ]; then
+  # 64-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=ON -DEXPORT_C_API=OFF 
-DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON
+else
+  # 32-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF 
-DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON
+fi
+make  -j 1
+
+cd ../10bit
+if [ $(uname -m) == 'x86_64' ]; then
+  # 64-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=ON -DEXPORT_C_API=OFF 
-DENABLE_SHARED=OFF -DENABLE_CLI=OFF
+else
+  # 32-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF 
-DENABLE_SHARED=OFF -DENABLE_CLI=OFF
+fi
+make -j 1
+
+cd ../8bit
+ln -sf ../10bit/libx265.a libx265_main10.a
+ln -sf ../12bit/libx265.a libx265_main12.a
+cmake ../source -DEXTRA_LIB="x265_main10.a;x265_main12.a" -DENABLE_SHARED=OFF 
-DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON
+make -j 1
+
+# rename the 8bit library, then combine all three into libx265.a
+mv libx265.a libx265_main.a
+
+uname=`uname`
+if [ "$uname" = "Linux" ]
+then
+
+# On Linux, we use GNU ar to combine the static libraries together
+ar -M 

Re: [Cin] July monthly builds available BUT lots of clean up still..

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 01 August 2020 23:43:20 Phyllis Smith via Cin 
написал(а):
> Andrew,
> 
> > > We had a lot of problems with the builds yesterday so have a lot of
> > cleanup
> > > and documentation fixes to do yet this weekend.  Some problems listed
> > here.
> >
> > Problems nearly always sad and definitely time consuming.. Sorry to hear
> > that.
> >
> > I was looking at gitweb, and new tag (2020-07 ?) not yet appeared, so I
> > can sleep some more and wait for clean-up to complete.
> >
> 
> OK, you and the dog can wake up now as the Tag has been added !  We did not
> add the updated Russian translations as you mentioned to wait, but I wanted
> to make sure that I did not miss your email as sometimes it ends up in spam
> and I never look there).
> 

Ok, thanks!

I compiled and tested it briefly - seems to work 
(loading mp4 video, cutting a bit, adding fade keyframes, selecting region 
and rendering it into mkv vp9)

Yes, I also had few emails from Cin in spam folder today. But now they arrived 
in normal inbox (gmail).
Probably Google had bad day! {I'm fairly sure Internet Wayback Machine had - it 
keep throwing err 500 or even 520 at me!}

On 10-bit front - I still have those patches around, one required minor fixing 
today ...

in patch3 just try to remove  -DENABLE_ASSEMBLY=OFF statements - 10/12-bit 
assembly only exist for x86_64 ...
For thirdparty/makefile patch you probably need to cut off additional 
parameters - I add it after another my patch,
for build trimming (on disk space/compilation/linking time) 

--- /dev/null	2020-03-14 06:02:18.586124011 +0300
+++ ./configure	2020-03-18 00:04:59.360807192 +0300
@@ -0,0 +1 @@
+/bin/true
--- /dev/null	2020-03-14 06:02:18.586124011 +0300
+++ ./Makefile	2020-03-18 00:04:59.388807329 +0300
@@ -0,0 +1,4 @@
+#$(shell cd build/linux ; ./multilib.sh)
+.NOTPARALLEL:
+all:
+	$(shell ./multilib.sh ; cp 8bit/libx265.a . ; cp 8bit/x265.pc . ; cp 8bit/x265_config.h .)
--- /dev/null	2020-03-14 06:02:18.586124011 +0300
+++ ./multilib.sh	2020-03-18 00:04:59.404807407 +0300
@@ -0,0 +1,41 @@
+#!/bin/sh
+
+mkdir -p 8bit 10bit 12bit
+
+cd 12bit
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON
+make  -j 1
+
+cd ../10bit
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF
+make -j 1
+
+cd ../8bit
+ln -sf ../10bit/libx265.a libx265_main10.a
+ln -sf ../12bit/libx265.a libx265_main12.a
+cmake ../source -DEXTRA_LIB="x265_main10.a;x265_main12.a" -DENABLE_SHARED=OFF -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON
+make -j 1
+
+# rename the 8bit library, then combine all three into libx265.a
+mv libx265.a libx265_main.a
+
+uname=`uname`
+if [ "$uname" = "Linux" ]
+then
+
+# On Linux, we use GNU ar to combine the static libraries together
+ar -M 

Re: [Cin] July monthly builds available BUT lots of clean up still..

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 01 August 2020 19:00:56 Phyllis Smith via Cin 
написал(а):
> We had a lot of problems with the builds yesterday so have a lot of cleanup
> and documentation fixes to do yet this weekend.  Some problems listed here.

Problems nearly always sad and definitely time consuming.. Sorry to hear that.

I was looking at gitweb, and new tag (2020-07 ?) not yet appeared, so I
can sleep some more and wait for clean-up to complete.

Thanks a ton, everyone!


> 
> Tumbleweed (Leap-ish) may be eliminated next month because it is very
> time-consuming to upgrade this Operating System every month since it is not
> a distro that we use on a daily basis.  It has been a problem every month;
> for example 2,000 packages had to be updated for it between June 29 and
> July 29 and then it did not work correctly.  Instead we ended up doing a
> brand new install which also took a lot of time (about 4 hours).  So unless
> we get feedback that it is worth the time, it will be dropped.
> 
> Leap 15-02 build and Mint 20 are new builds this month but installing has
> not been tested or updated on the website due to time constraints.
> Arch, Tumbleweed, and Gentoo are OK but GG had to make some changes.
> 
>  *Release Notes *(found on website as usual)
> 
> Cinelerra-GG (Version Infinity)  Release Notes for 07/01/2020-07/31/2020
> for builds
> 
> 1. *Upgraded several thirdparty libraries* to include:
> *FFmpeg to 4.3* – with new plugins of asubboost (audio) and addroi,
> bilateral, cas, dblur, gradients,
>median, photosensitivity, scdet, scroll, sierpinski, thistogram,
> tmedian, untile, v360, yaepblur
>   (video) plugins.  You can use “i” in the Resources window and mouse
> on each to get short
>   information.
> *+ turbo-jpeg, vorbis, x265, vpx, lv2, aom, and dav1d.*
> 2.  Mint 20 builds are now available and Leap is updated to 15.2.2.
> 3.  *Gang modes*, which includes Gang Channels mode for DAW-like editing,
> has minor improvements:
> - Using Shift on the gang mode toggle, switches back to the previous
> mode thus making it easy to
>   see a different view temporarily in order to view the actual track
> lineup.
> - Gang Channel icon in the top line of the timeline, is yellow to help
> make it clear that you are in this
>mode.  The Gang Media icon is red as a warning of this mode.  The
> default Gang None is just in a
>theme related ordinary color, often white.
> - A slight change in the order of symbols in the Patchbay has been made
> for aesthetic purposes.
> - Wysiwig tweak for ganging set of the Master Track for channels.
> 4.  *Align Timecodes* feature has been added based on different timecodes
> or timings included with the
>  files.  LTC from external generated audio has not been incorporated
> due to lack of proper test
>  material.  Usage description is included temporarily as a pdf file
> attached to BT# 448 (which
>  prompted this incomplete feature).
> 5. *Tracks Swap Up/Down* added to the Tracks pulldown to provide previous
> capability that was in
>  “move up”/”move down”.
> 6. *Usability Improvements:*
> In the Viewer window, you can, but no longer have to press Rewind
> button to start Play over again.
>   This includes play, fast play, play reverse, and fast play reverse
> (Skinkie BT #463).
> Many FFmpeg plugins required the use of the Apply button before a
> parameter change would take
>   effect.  Now when you type in a parameter change and hit the Enter
> key, the change will take effect
>   (Skinkie BT #464).
> *Auto Rotate for ffmpeg video that has “metadata” *defining the
> rotation in 90 degree increments has
>   been implemented and is now the default, but you can change this in
> Settings→Preferences,
>   Appearance, Flags (Ig0r forum “Rotation metadata usage in
> viewer/compositor”).
> Added a dump_stack to the generated crash dumps so that this
> information is always included, thus
>   making user crash dumps more valuable for analysis and potentially
> fixing the bugs that are found.
> *Subtitles now have a choice of format* in that menu; srt for SubRip
> which is now the default, sub
>for Subviewer and udvd which was the original MicroDVD format
> (RafaMar BT #475).
> *Mix master*s menu item added under the Window pulldown → Mixers
> subwindow.  This additional
>feature makes it very easy to get into the multi-camera mixer mode
> after tracks have already been
>set up and edited.
> When using “File by Reference”  if you exit without “saving”, a
> reminder will popup to allow you to
>choose to save so that you do not lose work.
> Minor Spanish translation update (from Rafamar).
> 7. *Bugs/Issues fixed:*
> The “drag” checkbox for the following plugins has had a major rework
> done:
> Sketcher, CriKey, Title, Tracer, and Boxblur
> Change prompted by BT #482 from RafaMar which was 

Re: [Cin] [spam?] Fixed typo in my x265-8/10/12 bit patchset, tried CineformHD encoder in ffmpeg.git

[Andrew Randrianasulu via Cin]

В сообщении от Friday 07 August 2020 20:16:52 вы написали:
> On Thu, 6 Aug 2020, Andrew Randrianasulu via Cin wrote:
> 
> > It worked at around 7 fps for 1080p h264 source in RGBA-float project ...
> > Decoding with mplayer was fine if I set CPU to on-demand performance,
> > but just 4x 1.4Ghz of my AMD FX 4300  was not enough for single stream 
> > decode.
> >
> > This codec was rumored to be fast for both encode and decode, guess ffmpeg
> > implementation not very fast yet ...
> 
> Mplayer can sometimes be too slow at decoding full HD H.264. I think,
> because it is trying to visualize video with too much accuracy, while some
> other players do it simpler (and therefore faster).
> 
> To me, sometimes the following options helped, mplayer was accelerated
> without any visible degrade in quality:
> 
> mplayer -autosync 30
> mplayer -lavdopts lowres=1
> mplayer -lavdopts fast
> mplayer -lavdopts skiploopfilter=nonkey

Yeah, those work on h264 and some other video codecs
(I tried lowres on mpeg2/dv/mjpeg). But cineformHD decoding
doesn't like lowres (gives errors and black window), probably not implemented 
yet 

 mplayer /dev/shm/cineformhd.mov -quiet -vo gl  -lavdopts lowres=1
MPlayer SVN-r38192-5.5.0 (C) 2000-2020 MPlayer Team
226 audio & 470 video codecs
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/cineformhd.mov.
libavformat version 58.46.101 (internal)
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x576a8aa0]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 (cfhd), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang rus
VIDEO:  [CFHD]  1920x1080  24bpp  29.970 fps  87349.2 kbps (10662.7 kbyte/s)
[gl] using extended formats. Use -vo gl:nomanyfmts if playback fails.
==
Opening video decoder: [dshow] DirectShow video codecs
Win32 LoadLibrary failed to load: /usr/lib/codecs/CFDecode2.ax
Warning: DS_Filter() could not open DirectShow DLL.  (DLL=CFDecode2.ax)
Failed to create DirectShow filter
ERROR: Could not open required DirectShow codec CFDecode2.ax.
You need to upgrade/install the binary codecs package.
Go to http://www.mplayerhq.hu/dload.html
VDecoder init failed :(
Opening video decoder: [vfw] Win32/VfW video codecs
Loading codec DLL: 'cinevfw.dll'
Win32 LoadLibrary failed to load: /usr/lib/codecs/cinevfw.dll
Can't open library cinevfw.dll
ICOpen failed! unknown codec / wrong parameters?
VDecoder init failed :(
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 58.92.100 (internal)
[cfhd @ 0x577feea0]The maximum value for lowres supported by the decoder is 0
Selected video codec: [ffcfhd] vfm: ffmpeg (FFmpeg Cineform HD)
==
Clip info:
 major_brand: qt
 minor_version: 512
 compatible_brands: qt
 encoder: Lavf58.49.100
Load subtitles in /dev/shm/
==
Forced audio codec: mad
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
[aac @ 0x577feea0]Multiple frames in a packet.
AUDIO: 44100 Hz, 2 ch, floatle, 129.0 kbit/4.57% (ratio: 16121->352800)
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 @ 0x577feea0]channel element 0.0 is not allocated
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [gl] 960x540 => 960x540 Planar 422P 10-bit little-endian
Mesa: User error: GL_INVALID_ENUM in 
glTexParameter(pname=GL_TEXTURE_STORAGE_HINT_APPLE)
[cfhd @ 0x577feea0]Invalid lowpass width
[cfhd @ 0x577feea0]Invalid lowpass width
[cfhd @ 0x577feea0]Invalid lowpass width
[cfhd @ 0x577feea0]g frame!
Invalid lowpass width
Error while decoding frame!
[cfhd @ 0x577feea0]Invalid lowpass width
[cfhd @ 0x577feea0]Invalid lowpass width
Error while decoding frame!
[cfhd @ 0x577feea0]Error while decoding frame!
Invalid lowpass width
[cfhd @ 0x577feea0]Invalid lowpass width
Error while decoding frame!
[cfhd @ 0x577feea0]Error while decoding frame!
Invalid lowpass width
[cfhd @ 0x577feea0]Error while decoding frame!
Invalid lowpass width
 
[a lot of those]



> 
> The latter option being perhaps most important, with it mplayer was
> accelerated drastically on some video.
> 
> Somewhen I have seen also a strange video from some digital camera with the
> usual 30 fps actual, but 1000 fps set in metadata. Mplayer tried to display
> it at 1000 fps and came in nirvana...

[Cin] Fixed typo in my x265-8/10/12 bit patchset, tried CineformHD encoder in ffmpeg.git

[Andrew Randrianasulu via Cin]

Hi all ...

Not much to report, just another recompile of CinelerraGG. I made typo in one
of my patches, so compilation stopped in x265, but then I fixed it and tried 
resulted Cinelerra for encoding ..

 cin
Cinelerra Infinity - built: Aug  6 2020 08:57:33
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

RenderFarmClient::main_loop: client started
x265 [info]: HEVC encoder version 3.4
x265 [info]: build info [Linux][clang 10.0.0][32 bit][noasm] 10bit
x265 [info]: using cpu capabilities: none!
x265 [info]: Main 4:2:2 10 profile, Level-4 (Main tier)
x265 [info]: Thread pool created using 4 threads
x265 [info]: Slices  : 1
x265 [info]: frame threads / pool features   : 2 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 3
x265 [info]: Keyframe min / max / scenecut / bias  : 25 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt: 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb   : 1 / 1 / 0
x265 [info]: References / ref-limit  cu / depth  : 3 / off / on
x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress: CRF-28.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 early-skip rskip mode=1 signhide tmvp
x265 [info]: tools: b-intra strong-intra-smoothing lslices=6 deblock sao
FFStream::encode_frame: encode failed.
file: /dev/shm/x265-10bit.m2ts
  err: Ресурс временно недоступен
FFStream::flush failed
:file:/dev/shm/x265-10bit.m2ts
  err: Операция не позволена
FFStream::encode_frame: encode failed.
file: /dev/shm/x265-10bit.m2ts
  err: Ресурс временно недоступен
FFStream::flush failed
:file:/dev/shm/x265-10bit.m2ts
  err: Операция не позволена
x265 [info]: frame I: 10, Avg QP:27.41  kb/s: 3481.49
x265 [info]: frame P:502, Avg QP:29.10  kb/s: 2210.02
x265 [info]: frame B:   1274, Avg QP:32.85  kb/s: 942.35
x265 [info]: Weighted P-Frames: Y:2.4% UV:0.4%
x265 [info]: consecutive B-frames: 8.4% 7.8% 13.0% 67.7% 3.1%

encoded 1786 frames in 3014.28s (0.59 fps), 1312.88 kb/s, Avg QP:31.76
Render::render_single: Session finished.
** rendered 1814 frames in 3014.337 secs, 0.602 fps
Mesa: User error: GL_INVALID_OPERATION in glDeleteShader
Session time: 3:08:33
Cpu time: user: 3:06:29.051 sys: 0:01:52.474

a bit strange, because resulted m2ts file still plays until end, just 
video stops a bit before audio (with mplayer).

I also tried this new CineformHD encoder in ffmpeg, using attached options file:

cat /usr/share/cin/ffmpeg/video/cfhdenc.qt
mov cfhd

It worked at around 7 fps for 1080p h264 source in RGBA-float project ...
Decoding with mplayer was fine if I set CPU to on-demand performance,
but just 4x 1.4Ghz of my AMD FX 4300  was not enough for single stream decode.

This codec was rumored to be fast for both encode and decode, guess ffmpeg 
implementation not very fast yet ...



--- /dev/null	2020-03-14 06:02:18.586124011 +0300
+++ ./configure	2020-03-18 00:04:59.360807192 +0300
@@ -0,0 +1 @@
+/bin/true
--- /dev/null	2020-03-14 06:02:18.586124011 +0300
+++ ./Makefile	2020-03-18 00:04:59.388807329 +0300
@@ -0,0 +1,4 @@
+#$(shell cd build/linux ; ./multilib.sh)
+.NOTPARALLEL:
+all:
+	$(shell ./multilib.sh ; cp 8bit/libx265.a . ; cp 8bit/x265.pc . ; cp 8bit/x265_config.h .)
--- /dev/null	2020-07-19 09:07:01.788494015 +0300
+++ ./multilib.sh	2020-08-02 02:34:58.444933214 +0300
@@ -0,0 +1,54 @@
+#!/bin/sh
+
+mkdir -p 8bit 10bit 12bit
+
+
+cd 12bit
+if [ $(uname -m) == 'x86_64' ]; then
+  # 64-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON
+else
+  # 32-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON
+fi
+make  -j 1
+
+cd ../10bit
+if [ $(uname -m) == 'x86_64' ]; then
+  # 64-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF
+else
+  # 32-bit stuff here
+cmake ../source -DHIGH_BIT_DEPTH=ON -DENABLE_ASSEMBLY=OFF -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF
+fi
+make -j 1
+
+cd ../8bit
+ln -sf ../10bit/libx265.a libx265_main10.a
+ln -sf ../12bit/libx265.a libx265_main12.a
+cmake ../source -DEXTRA_LIB="x265_main10.a;x265_main12.a" -DENABLE_SHARED=OFF -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON
+make -j 1
+
+# rename the 8bit library, then combine all three into libx265.a
+mv libx265.a libx265_main.a
+
+uname=`uname`
+if [ "$uname" = 

Re: [Cin] AOMedia AV1 2.0

[Andrew Randrianasulu via Cin]

В сообщении от Friday 10 July 2020 03:34:56 Phyllis Smith via Cin написал(а):
> Andrew,
> 
> GG is looking at updating any third party that needs updating.  I found
> dav1d 0.7.1 at:
> 
> https://code.videolan.org/videolan/dav1d/-/archive/0.7.1/dav1d-0.7.1.tar.gz
> and it appears to still be the latest version.  Is that correct?

yes, 0.7.1 seems to be latest 
 https://code.videolan.org/videolan/dav1d/-/releases

 0.7.1
Assets 4
dav1d 0.7.1 'Frigatebird' the fast and lean AV1 decoder

This is a minor update of the dav1d decoder, from the 0.7.x branch.

This release increases the speed of decoding on ARM32 by up to 28%, adds some 
SSE2 optimizations, some AVX2 for MC scaled and fixes a couple of minor issues.
e9df70c4
0.7.1
Created  2 weeks ago by  (there was  author's image)



> 
> But I am having trouble finding aom v2.0.  I downloaded from:
>https://github.com/mozilla/aom
> These 2 files:
>   aom-master.zip
>   aom-bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz
> but I am used to seeing the version number in what I download.  Is there a
> more reliable tarball that I should get?

I think current source should be at

https://aomedia.googlesource.com/aom/


https://aomedia.googlesource.com/aom/+/refs/tags/v2.0.0


> 
> Thanks for your help.  Phyllis
> 
> 
> On Tue, May 26, 2020 at 3:19 PM Andrew Randrianasulu <
> randrianas...@gmail.com> wrote:
> 
> > В сообщении от Tuesday 19 May 2020 18:37:05 Phyllis Smith написал(а):
> > > Thanks for the warning.  GG was just talking about getting around to
> > > upgrading the thirdparty libraries soon so an attempt can be made with
> > aom.
> >
> > Also dav1d 0.7 was  released, with some additional speedup
> > (but because CinGG's version uses custom buildsystem for this one...
> >  upgrade may be not very smooth)
> >
> > https://www.phoronix.com/scan.php?page=news_item=Dav1d-0.7-Performance
> >
> >
> >
> > >
> > > On Tue, May 19, 2020 at 6:58 AM Andrew Randrianasulu <
> > > randrianas...@gmail.com> wrote:
> > >
> > > > Hi all!
> > > >
> > > > Just was refreshing Phoronix page and this scrolls into view:
> > > >
> > > >
> > > >
> > https://www.phoronix.com/scan.php?page=news_item=AOMedia-libaom-2.0-Released
> > > > ---
> > > > AOMedia AV1 2.0 Codec Library Released With Many Improvements
> > > > Written by Michael Larabel in Multimedia on 19 May 2020 at 06:53 AM
> > EDT. 2
> > > > Comments
> > > > MULTIMEDIA --  Version 2.0 of the libaom AOMedia AV1 video encoder /
> > video
> > > > codec
> > > > SDK library is now available as the first major update in nearly two
> > > > years.
> > > >
> > > > Libaom 2.0 is the first release since the original 1.0 release back in
> > > > mid-2018 after
> > > > the AOMedia codec working group approved the 1.0 release.
> > > > The developers view this AOMedia AV1 2.0 release as now
> > > > being their "first official release" for production.
> > > >
> > > > Libaom 2.0 adds a real-time encoding mode, SVC support,
> > > > drops multi-resolution encoding, documentation updates, and other
> > > > improvements
> > > > to this open-source AV1 reference encoder.
> > > > --
> > > >
> > > > Hm, beaware about  possible buildsystem changes, I guess?
> > > >
> > > > I have early snapshot running, from around Mar, 19 2020
> > > > but I have recent Cmake and stuff 
> > > > --
> > > > Cin mailing list
> > > > Cin@lists.cinelerra-gg.org
> > > > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> > > >
> > >
> >
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 

Re: [Cin] FFmpeg 4.3 mpegts patch - questions ....

[Andrew Randrianasulu via Cin]

В сообщении от Monday 13 July 2020 20:07:48 Phyllis Smith via Cin написал(а):
> Andrew, gg has yet to look at this BUT I can tell you for a fact that he
> had to revert to his original BluRay media mods because "yes" the ffmpeg
> ones did not work with our bluray player.  And we use this quite
> frequently.  First it cut off the audio at the beginning on a 1 1/2 minute
> video and then it would not replay until powered off/on the device.  The
> particular bluray player we use matches the one that Terje originally had.
> GG's mods were based on "Sintel" (available via download).  It would take a
> lot more debugging to get the ffmpeg mods working and we thought there were
> a lot more useful things to do. 

Yeah , media (in this sense) tend to be a hard-to-get-right area 

I wonder if your player  accept streams re-muxed by

https://github.com/justdan96/tsMuxer ?

On the webpage it says:
Some of the major features include:

Ability to set muxing fps manually and automatically
Ability to change level for H.264 streams
Ability to shift a sound tracks
Ability to extract DTS core from DTS-HD
Ability to join files
Output/Author to compliant Blu-ray Disc or AVCHD
Blu-ray 3D support

but of course bugs exist 


> I suspect the number of people making this 
> kind of media today is very low but we need it to work for us.  I will
> provide his feedback later after he has time to read this all.
> Thanks, Phyllis

Well, it was not my best review, but I was just curious 
Take your time, and thanks again... it seems bug stream will never end!

> 
> On Sun, Jul 12, 2020 at 11:41 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> >
> > src on cgit:
> >
> >
> > https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/thirdparty/src/ffmpeg-4.3.patch2;h=81cae5e66d85d3c089603a5a6425cd165aa9f16e;hb=HEAD
> >
> > Well, I don't understand it, just worried about GROWING diff between
> > original ffmpeg and Cin's version of it in this area.
> >
> > (added Marton as CC, as current maintainer of this area of code - sorry
> > for my cont. ignorance, Marton!)
> >
> > @@ -76,11 +77,12 @@
> >  MpegTSSection pat; /* MPEG-2 PAT table */
> >  MpegTSSection sdt; /* MPEG-2 SDT table context */
> >  MpegTSService **services;
> > -int64_t sdt_period; /* SDT period in PCR time base */
> > -int64_t pat_period; /* PAT/PMT period in PCR time base */
> > +int64_t sdt_packet_timer, sdt_packet_period;
> > +int64_t pat_packet_timer, pat_packet_period;
> >  int nb_services;
> > -int64_t first_pcr;
> > -int64_t next_pcr;
> > +int onid;
> > +int tsid;
> >
> > as far as I understand those  (onid, tsid) used donwstream:
> >
> > @@ -259,7 +257,7 @@
> >  put16(, service->sid);
> >  put16(, 0xe000 | service->pmt.pid);
> >  }
> > -mpegts_write_section1(>pat, PAT_TID, ts->transport_stream_id,
> > ts->tables_version, 0, 0,
> > +mpegts_write_section1(>pat, PAT_TID, ts->tsid,
> > ts->tables_version, 0, 0,
> >
> >
> > was it just for shortening typing time?
> >
> > @@ -90,14 +92,14 @@
> >  int service_type;
> >
> >  int pmt_start_pid;
> > +int pcr_start_pid;
> >  int start_pid;
> >  int m2ts_mode;
> > -int m2ts_video_pid;
> > -int m2ts_audio_pid;
> > -int m2ts_pgssub_pid;
> > -int m2ts_textsub_pid;
> > +int64_t ts_offset;
> >
> >
> > Hm, it think major point in 4.3 was exactly
> >
> > - Support for muxing pcm and pgs in m2ts
> >
> > ? (PGS are Blu-Ray subtitle graphics - no encoder in ffmpeg yet. But
> > probably you can remux the from existing track?)
> >
> >
> > @@ -217,14 +217,15 @@
> >  /* mpegts writer */
> >
> >  #define DEFAULT_PROVIDER_NAME   "FFmpeg"
> > -#define DEFAULT_SERVICE_NAME"Service"
> > +#define DEFAULT_SERVICE_NAME"Service01"
> >
> >
> > Was it required from your Blu-Ray Disk player? May be it can be made
> > conditional on new m2ts_b  (say) mode?
> >
> >
> > -/* we retransmit the SI info at this rate */
> > +/* we retransmit the SI info at this rate (ms) */
> >  #define SDT_RETRANS_TIME 500
> >  #define PAT_RETRANS_TIME 100
> > -#define PCR_RETRANS_TIME 20
> > +#define PCR_RETRANS_TIME 50
> >
> > may be comment improvement can be made into standalone patch?
> >
> > @@ -281,148 +279,6 @@
> >  *q_ptr = 

Re: [Cin] FFmpeg 4.3 mpegts patch - questions ....

[Andrew Randrianasulu via Cin]

eg's MPEG-TS output also has issues, 
especially with timing information if I remember correctly, its output is 
generally accepted as 
"valid" by renderers. So, despite imperfections in FFmpeg's implementation, 
they seem to have 
gotten something right with regards to "compatibility". I guess it could also 
be that their output is widespread, 
so that decoder implementations are likely to be tested with FFmpeg's output.

I just discovered that tsMuxer had been open-sourced +1 right now, so we have 
been 
using the 2014 version exclusively. That means that this might be a red herring 
and that whatever 
issue caused some renderers to choke has already been addressed by other fixes. 
This issue just 
sounds like a "perfect" explanation.

---quote end

Unfortunately, it was  not disclosed if some suggestions helped or not


https://github.com/justdan96/tsMuxer/issues/141
[Bug] BD Transport stream bitrate is not limited #141

I hope this one can be workarounded by just keeping traget bitrate for 
elementary streams a bit lower?

Sorry for somewhat pushing this software on you, just as it was noted in 
comments currently only few
open-source implementations of ts muxers exist, and this one actually was 
compile-able on my machine (w/o QT GUI):

./tsmuxer
tsMuxeR version git-97d49e4. github.com/justdan96/tsMuxer

tsMuxeR is a simple program to mux video to TS/M2TS files or create BD disks.
tsMuxeR does not use external filters (codecs).

[...]

--blu-ray   Mux as a BD disc. If the output file name is a folder, a
Blu-Ray folder structure is created inside that folder.
SSIF files for BD3D discs are not created in this case. If
        the output name has an .iso extension, then the disc is
created directly as an image file.
--blu-ray-v3As above - except mux to UHD BD discs.
--avchd Mux to AVCHD disc.

(last one was said to work with PlayStation *3*)

So, _in theory_, if your device accept stream from it - you can try to abuse it
for various needs - like, muxing subtitles :}



> 
> gg
> 
> 
> On Sun, Jul 12, 2020 at 11:41 PM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> >
> > src on cgit:
> >
> >
> > https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/thirdparty/src/ffmpeg-4.3.patch2;h=81cae5e66d85d3c089603a5a6425cd165aa9f16e;hb=HEAD
> >
> > Well, I don't understand it, just worried about GROWING diff between
> > original ffmpeg and Cin's version of it in this area.
> >
> > (added Marton as CC, as current maintainer of this area of code - sorry
> > for my cont. ignorance, Marton!)
> >
> > @@ -76,11 +77,12 @@
> >  MpegTSSection pat; /* MPEG-2 PAT table */
> >  MpegTSSection sdt; /* MPEG-2 SDT table context */
> >  MpegTSService **services;
> > -int64_t sdt_period; /* SDT period in PCR time base */
> > -int64_t pat_period; /* PAT/PMT period in PCR time base */
> > +int64_t sdt_packet_timer, sdt_packet_period;
> > +int64_t pat_packet_timer, pat_packet_period;
> >  int nb_services;
> > -int64_t first_pcr;
> > -int64_t next_pcr;
> > +int onid;
> > +int tsid;
> >
> > as far as I understand those  (onid, tsid) used donwstream:
> >
> > @@ -259,7 +257,7 @@
> >  put16(, service->sid);
> >  put16(, 0xe000 | service->pmt.pid);
> >  }
> > -mpegts_write_section1(>pat, PAT_TID, ts->transport_stream_id,
> > ts->tables_version, 0, 0,
> > +mpegts_write_section1(>pat, PAT_TID, ts->tsid,
> > ts->tables_version, 0, 0,
> >
> >
> > was it just for shortening typing time?
> >
> > @@ -90,14 +92,14 @@
> >  int service_type;
> >
> >  int pmt_start_pid;
> > +int pcr_start_pid;
> >  int start_pid;
> >  int m2ts_mode;
> > -int m2ts_video_pid;
> > -int m2ts_audio_pid;
> > -int m2ts_pgssub_pid;
> > -int m2ts_textsub_pid;
> > +int64_t ts_offset;
> >
> >
> > Hm, it think major point in 4.3 was exactly
> >
> > - Support for muxing pcm and pgs in m2ts
> >
> > ? (PGS are Blu-Ray subtitle graphics - no encoder in ffmpeg yet. But
> > probably you can remux the from existing track?)
> >
> >
> > @@ -217,14 +217,15 @@
> >  /* mpegts writer */
> >
> >  #define DEFAULT_PROVIDER_NAME   "FFmpeg"
> > -#define DEFAULT_SERVICE_NAME"Service"
> > +#define DEFAULT_SERVICE_NAME"Service01"
> >
> >
> > Was it required from your Blu-Ray Disk player? May be it can be 

[Cin] Offtop: "Spp2Pgs - Converts general subtitles to HDMV PG streams"

[Andrew Randrianasulu via Cin]

So, I was doing another pass at 'what exactly can encode those PGS streams?' 
and found this little project:

https://github.com/subelf/Spp2Pgs

--desc

Spp2Pgs

Converts general subtitles to HDMV PG streams.
In other words, converts .ass files to .sup files.

The project generates a command line application and a CLR dll file.
Core of them is a static library, libspp2pgs.

An external dll, xy-VSSppf, is introduced to deal with subtitle files.
It's based on a forked version of xy-VSFilter, rendering and providing 
subtitles in a more easy way.

Here is a breif description for all the four parts.
Spp2Pgs*.exe

An executable converts subtitles to .sup files.
Usage:
Spp2Pgs -i "X:\Saya1011con.ass" -s 1080 -r 23 "X:\Saya1011con.sup"
Type Spp2Pgs -h for more help.
libspp2pgs & Spp2PgsNet*.dll

The core and its CLR library wrapper for .NET framework applications.
Three classes play the main role:

PgsEncoder, encoding and writing a pgs file.
FrameStream, reading subtitles and rendering subtitles into image.
Spp2Pgs, an entrance for all other things. Also reading images from 
FrameStream and sending them to PgsEncoder.
---

It seems to be Windows-based (at least build files are *.vcxproj), and has some 
x86 asm (yasm) functions,
but better than nothing, I guess ...

This specific fork was not updated in four years (since 2016), so some subtle 
(!) bugs may exist 

For license it says: GPL-3.0 License 

Found this one via google and this forum post from 2019:

http://forum.doom9.org/showthread.php?t=176899

Also found subtitler program written in C#/.Net (so it sorta run under 
Linux/Mono):

https://nikse.dk/SubtitleEdit/Help#linux

But I have no idea how (if at all) it can be compiled under Linux .. (Arch 
package basically repackages
binary file). Found via 
https://unix.stackexchange.com/questions/278001/open-hdmv-pgs-subtitles-in-gnu-linux

Also there was KDE5 based subtitle editor with some speech recognition,
but apparently it was archived by developer last year:

https://github.com/maxrd2/SubtitleComposer

Ah, no I'm blind , it was moved into KDE!

https://invent.kde.org/multimedia/subtitlecomposer/-/commits/master

So, some interesting findings, but making any of them to work (at least on my 
machine) will be ..non-trivial.








-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] FFmpeg 4.3 mpegts patch - questions ....

[Andrew Randrianasulu via Cin]

В сообщении от Monday 13 July 2020 21:42:21 Marton Balint написал(а):
> 
> On Mon, 13 Jul 2020, Andrew Randrianasulu wrote:
> 
> >
> > src on cgit:
> >
> > https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/thirdparty/src/ffmpeg-4.3.patch2;h=81cae5e66d85d3c089603a5a6425cd165aa9f16e;hb=HEAD
> >
> > Well, I don't understand it, just worried about GROWING diff between
> > original ffmpeg and Cin's version of it in this area.
> >
> > (added Marton as CC, as current maintainer of this area of code - sorry for 
> > my cont. ignorance, Marton!)
> 
> This patch was a bit hard to go through even in its original form, but 
> some features got intergrated into ffmpeg master or my ffmpeg m2ts 
> branch. I'd at least consider dropping this and using the top 5 patches 
> from this branch:
> 
> https://github.com/cus/ffmpeg/commits/mpegts2

Thanks for updating this patchest. Unfortunately, I don't have any hardware (BD 
burner, player) to
play with those accurately enough (software players can be convince to play 
stream anyway).


> 
> However, if somebody wants to mux compliant BluRay i'd probably say 
> tsMuxer is still slightly better for the job then ffmpeg, because some 
> codec descriptors are still not generated which should be needed for 
> BluRay, I don't remember which ones.

At some point in the future I might try to burn (with tsMuxer's help)
"AVC on DVD" type of disk just to see if some far away PS3 will really play it
(but then I think I need to keep bitrate in typical DVD range - 8000 kbits/s or 
so ...)

> 
> Regarding pgs muxing, there was an interesting patch series on 
> ffmpeg-devel which should be needed to convert between the pgs format of 
> mpegts and matroska, that might be of interest for you too:
> 
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=1163

Thanks, interesting (I wonder what kind of sw was creating those mkvs, 
but probably something proprietary/freeware from doom9 archives :} )

> 
> Regards,
> Marton
> 
> 
> 
> >
> > @@ -76,11 +77,12 @@
> > MpegTSSection pat; /* MPEG-2 PAT table */
> > MpegTSSection sdt; /* MPEG-2 SDT table context */
> > MpegTSService **services;
> > -int64_t sdt_period; /* SDT period in PCR time base */
> > -int64_t pat_period; /* PAT/PMT period in PCR time base */
> > +int64_t sdt_packet_timer, sdt_packet_period;
> > +int64_t pat_packet_timer, pat_packet_period;
> > int nb_services;
> > -int64_t first_pcr;
> > -int64_t next_pcr;
> > +int onid;
> > +int tsid;
> >
> > as far as I understand those  (onid, tsid) used donwstream:
> >
> > @@ -259,7 +257,7 @@
> > put16(, service->sid);
> > put16(, 0xe000 | service->pmt.pid);
> > }
> > -mpegts_write_section1(>pat, PAT_TID, ts->transport_stream_id, 
> > ts->tables_version, 0, 0,
> > +mpegts_write_section1(>pat, PAT_TID, ts->tsid, ts->tables_version, 
> > 0, 0,
> >
> >
> > was it just for shortening typing time?
> >
> > @@ -90,14 +92,14 @@
> > int service_type;
> >
> > int pmt_start_pid;
> > +int pcr_start_pid;
> > int start_pid;
> > int m2ts_mode;
> > -int m2ts_video_pid;
> > -int m2ts_audio_pid;
> > -int m2ts_pgssub_pid;
> > -int m2ts_textsub_pid;
> > +int64_t ts_offset;
> >
> >
> > Hm, it think major point in 4.3 was exactly
> >
> > - Support for muxing pcm and pgs in m2ts
> >
> > ? (PGS are Blu-Ray subtitle graphics - no encoder in ffmpeg yet. But 
> > probably you can remux the from existing track?)
> >
> >
> > @@ -217,14 +217,15 @@
> > /* mpegts writer */
> >
> > #define DEFAULT_PROVIDER_NAME   "FFmpeg"
> > -#define DEFAULT_SERVICE_NAME"Service"
> > +#define DEFAULT_SERVICE_NAME"Service01"
> >
> >
> > Was it required from your Blu-Ray Disk player? May be it can be made
> > conditional on new m2ts_b  (say) mode?
> >
> >
> > -/* we retransmit the SI info at this rate */
> > +/* we retransmit the SI info at this rate (ms) */
> > #define SDT_RETRANS_TIME 500
> > #define PAT_RETRANS_TIME 100
> > -#define PCR_RETRANS_TIME 20
> > +#define PCR_RETRANS_TIME 50
> >
> > may be comment improvement can be made into standalone patch?
> >
> > @@ -281,148 +279,6 @@
> > *q_ptr = q;
> > }
> >
> > -static int get_dvb_stream_type(AVFormatContext *s, AVStream *st)
> > [..]
> > -static int get_m2ts_stream_type(AVFormatContext *s, AVStream *st)
> >
> > here whole two functions are gone ..
> >
> > and probably replaced by homegrown one a bit downstream:
> >
> > @@ -472,8 +320,72 @@
> > err = 1;
> > break;
> > }
> > -
> > -stream_type = ts->m2ts_mode ? get_m2ts_stream_type(s, st) : 
> > get_dvb_stream_type(s, st);
> > +switch (st->codecpar->codec_id) {
> >
> >
> > any reason for this move?
> >
> > @@ -736,7 +648,7 @@
> > int i, running_status, free_ca_mode, val;
> >
> > q = data;
> > -put16(, ts->original_network_id);
> > +put16(, ts->onid);
> >
> >
> > again, just shorter to type?
> >
> > @@ -802,49 +714,12 

[Cin] UPD: Offtop: "Spp2Pgs - Converts general subtitles to HDMV PG streams"

[Andrew Randrianasulu via Cin]

And of course I found something  related to VCXPROJ->Cmake 
conversion minutes after I send this email out!

https://pypi.org/project/cmake-converter/

written in Python3, tries to autoconvert c/c++/fortran projects ...
Last version is 2.0.1 from  10 Dec, 2019  (so, not  abandoned)

Interesting, it may not work for big projects with GUI, but hopefully 
for small command line tools like this (lib)spp2pgs 

--  Пересланное сообщение  --

Тема: Offtop: "Spp2Pgs - Converts general subtitles to HDMV PG streams"
Дата: Вторник 14 июля 2020
Отправитель: Andrew Randrianasulu 
Получатель:  "Cinelerra.GG" , Marton Balint 
, "Cinelerra.GG" 

So, I was doing another pass at 'what exactly can encode those PGS streams?' 
and found this little project:

https://github.com/subelf/Spp2Pgs

--desc

Spp2Pgs

Converts general subtitles to HDMV PG streams.
In other words, converts .ass files to .sup files.

The project generates a command line application and a CLR dll file.
Core of them is a static library, libspp2pgs.

An external dll, xy-VSSppf, is introduced to deal with subtitle files.
It's based on a forked version of xy-VSFilter, rendering and providing 
subtitles in a more easy way.

Here is a breif description for all the four parts.
Spp2Pgs*.exe

An executable converts subtitles to .sup files.
Usage:
Spp2Pgs -i "X:\Saya1011con.ass" -s 1080 -r 23 "X:\Saya1011con.sup"
Type Spp2Pgs -h for more help.
libspp2pgs & Spp2PgsNet*.dll

The core and its CLR library wrapper for .NET framework applications.
Three classes play the main role:

PgsEncoder, encoding and writing a pgs file.
FrameStream, reading subtitles and rendering subtitles into image.
Spp2Pgs, an entrance for all other things. Also reading images from 
FrameStream and sending them to PgsEncoder.
---

It seems to be Windows-based (at least build files are *.vcxproj), and has some 
x86 asm (yasm) functions,
but better than nothing, I guess ...

This specific fork was not updated in four years (since 2016), so some subtle 
(!) bugs may exist 

For license it says: GPL-3.0 License 

Found this one via google and this forum post from 2019:

http://forum.doom9.org/showthread.php?t=176899

Also found subtitler program written in C#/.Net (so it sorta run under 
Linux/Mono):

https://nikse.dk/SubtitleEdit/Help#linux

But I have no idea how (if at all) it can be compiled under Linux .. (Arch 
package basically repackages
binary file). Found via 
https://unix.stackexchange.com/questions/278001/open-hdmv-pgs-subtitles-in-gnu-linux

Also there was KDE5 based subtitle editor with some speech recognition,
but apparently it was archived by developer last year:

https://github.com/maxrd2/SubtitleComposer

Ah, no I'm blind , it was moved into KDE!

https://invent.kde.org/multimedia/subtitlecomposer/-/commits/master

So, some interesting findings, but making any of them to work (at least on my 
machine) will be ..non-trivial.









---
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] ffmpeg upgraded from 4.1 to 4.3 + Thirdparty libraries

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 12 July 2020 01:34:00 Phyllis Smith via Cin написал(а):
> Andrew, thanks for testing.  I have downloaded all of your patches in case
> GG ever gets the time and energy to absorb some of them.

Thanks!

> 
> >
> > I think you mean ffmpeg from 4.2 to 4.3?
> >
> Thanks for correcting the above; it was getting late at night for me.
> 
> >
> > I rebuild CinelerraGG git
> > ...
> > once again my X11R7 prefix bites me 
> >
> It is always something!
> 
> >
> > error: /usr/share/cin/lv2/lsp-plugins.lv2/spectrum_analyzer_x1.ttl:278:2:
> > missing ';' or '.'
> > error: /usr/share/cin/lv2/lsp-plugins.lv2/spectrum_analyzer_x1.ttl:278:2:
> > expected `]', not `l'
> > lilv_world_load_file(): error: Error loading file
> > `file:///usr/share/cin/lv2/lsp-plugins.lv2/spectrum_analyzer_x1.ttl'
> > lv2: lilv_plugin_instantiate failed
> >
> I wonder if we should add  "spectrum_analyzer_x1"  to l v2_blacklist.txt ,
> but I am not sure of the correct format.?

Do not worry, this error was fixed in lsp-plugins (external project), I just 
forgot to add new version 

https://lsp-plug.in/?page=news

> 
> >
> >
> >
> > Your system is too SLOW to play this!  
> >
> >
> > Possible reasons, problems, workarounds:
> > ...
> > - Slow CPU
> > ...
> > I have seamonkey and Cin running at the same time, so CPU usage is high!
> >
> Interesting -- I had to look up seamonkey to "sea" what it was!
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] FFmpeg 4.3 mpegts patch - questions ....

[Andrew Randrianasulu via Cin]

src on cgit:

https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/thirdparty/src/ffmpeg-4.3.patch2;h=81cae5e66d85d3c089603a5a6425cd165aa9f16e;hb=HEAD

Well, I don't understand it, just worried about GROWING diff between 
original ffmpeg and Cin's version of it in this area.

(added Marton as CC, as current maintainer of this area of code - sorry for my 
cont. ignorance, Marton!) 

@@ -76,11 +77,12 @@
 MpegTSSection pat; /* MPEG-2 PAT table */
 MpegTSSection sdt; /* MPEG-2 SDT table context */
 MpegTSService **services;
-int64_t sdt_period; /* SDT period in PCR time base */
-int64_t pat_period; /* PAT/PMT period in PCR time base */
+int64_t sdt_packet_timer, sdt_packet_period;
+int64_t pat_packet_timer, pat_packet_period;
 int nb_services;
-int64_t first_pcr;
-int64_t next_pcr;
+int onid;
+int tsid;

as far as I understand those  (onid, tsid) used donwstream:

@@ -259,7 +257,7 @@
 put16(, service->sid);
 put16(, 0xe000 | service->pmt.pid);
 }
-mpegts_write_section1(>pat, PAT_TID, ts->transport_stream_id, 
ts->tables_version, 0, 0,
+mpegts_write_section1(>pat, PAT_TID, ts->tsid, ts->tables_version, 0, 
0,


was it just for shortening typing time?

@@ -90,14 +92,14 @@
 int service_type;
 
 int pmt_start_pid;
+int pcr_start_pid;
 int start_pid;
 int m2ts_mode;
-int m2ts_video_pid;
-int m2ts_audio_pid;
-int m2ts_pgssub_pid;
-int m2ts_textsub_pid;
+int64_t ts_offset;


Hm, it think major point in 4.3 was exactly 

- Support for muxing pcm and pgs in m2ts 

? (PGS are Blu-Ray subtitle graphics - no encoder in ffmpeg yet. But probably 
you can remux the from existing track?)


@@ -217,14 +217,15 @@
 /* mpegts writer */
 
 #define DEFAULT_PROVIDER_NAME   "FFmpeg"
-#define DEFAULT_SERVICE_NAME"Service"
+#define DEFAULT_SERVICE_NAME"Service01"


Was it required from your Blu-Ray Disk player? May be it can be made
conditional on new m2ts_b  (say) mode?


-/* we retransmit the SI info at this rate */
+/* we retransmit the SI info at this rate (ms) */
 #define SDT_RETRANS_TIME 500
 #define PAT_RETRANS_TIME 100
-#define PCR_RETRANS_TIME 20
+#define PCR_RETRANS_TIME 50

may be comment improvement can be made into standalone patch?

@@ -281,148 +279,6 @@
 *q_ptr = q;
 }
 
-static int get_dvb_stream_type(AVFormatContext *s, AVStream *st)
[..]
-static int get_m2ts_stream_type(AVFormatContext *s, AVStream *st)

here whole two functions are gone ..

and probably replaced by homegrown one a bit downstream:

@@ -472,8 +320,72 @@
 err = 1;
 break;
 }
-
-stream_type = ts->m2ts_mode ? get_m2ts_stream_type(s, st) : 
get_dvb_stream_type(s, st);
+switch (st->codecpar->codec_id) {


any reason for this move?

@@ -736,7 +648,7 @@
 int i, running_status, free_ca_mode, val;
 
 q = data;
-put16(, ts->original_network_id);
+put16(, ts->onid);


again, just shorter to type?

@@ -802,49 +714,12 @@
 return 0;
 }
 
-static int64_t get_pcr(const MpegTSWrite *ts, AVIOContext *pb)

-static void write_packet(AVFormatContext *s, const uint8_t *packet)

-static void section_write_packet(MpegTSSection *s, const uint8_t *packet)

all three gone  can they stay ? :}
(for reducing diff size)

 static MpegTSService *mpegts_add_service(AVFormatContext *s, int sid,
- const AVDictionary *metadata,
- AVProgram *program)
+ const char *provider_name,
+ const char *name)
 {
 MpegTSWrite *ts = s->priv_data;
 MpegTSService *service;
-AVDictionaryEntry *title, *provider;
-char default_service_name[32];
-const char *service_name;
-const char *provider_name;
-
-title = av_dict_get(metadata, "service_name", NULL, 0);
-if (!title)
-title = av_dict_get(metadata, "title", NULL, 0);
-snprintf(default_service_name, sizeof(default_service_name), "%s%02d", 
DEFAULT_SERVICE_NAME, ts->nb_services + 1);
-service_name  = title ? title->value : default_service_name;
-provider  = av_dict_get(metadata, "service_provider", NULL, 0);
-provider_name = provider ? provider->value : DEFAULT_PROVIDER_NAME;


I think this one allowed more data passing from ...upper libavcodec layer?

-static void enable_pcr_generation_for_stream(AVFormatContext *s, AVStream 
*pcr_st)
+static void mpegts_prefix_m2ts_header(AVFormatContext *s)
 {
 MpegTSWrite *ts = s->priv_data;
-MpegTSWriteStream *ts_st = pcr_st->priv_data;
-
-if (ts->mux_rate > 1 || ts->pcr_period_ms >= 0) {
-int pcr_period_ms = ts->pcr_period_ms == -1 ? PCR_RETRANS_TIME : 
ts->pcr_period_ms;
-ts_st->pcr_period = av_rescale(pcr_period_ms, PCR_TIME_BASE, 1000);
-} else {
-/* By default, for VBR we select the highest multiple of frame 
duration which is less 

Re: [Cin] ffmpeg upgraded from 4.1 to 4.3 + Thirdparty libraries

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 11 July 2020 04:19:14 Phyllis Smith via Cin написал(а):
> CinelerraGG git checkin includes the following upgrades and a couple of
> fixes:
> 
> 1) fixed ffmpeg scan remap
> 2) BT 473 configure.ac patch (noted by ferdnyc with patch)
> 3) thirdparty libraries updated to include:
> 
> ffmpeg from 4.1 to 4.3
> turbo-jpeg
> vorbis
> x265
> vpx
> lv2
> aom
> dav1d
> nv-codec-headers

I think you mean ffmpeg from 4.2 to 4.3?

I rebuild CinelerraGG git 

commit d830901b11606a7838791bc45e39130329db99f0 (HEAD -> master, origin/master, 
origin/HEAD)
Author: Good Guy 
Date:   Fri Jul 10 18:58:35 2020 -0600

ffmpeg scan remap fix, configure.ac all or none fix, 3rd party libs: 
ffmpeg, turbo-jpeg, vorbis, x265, vpx, lv2, aom, dav1d, ffnvcodec


with ffmpeg.git:

commit 6f84e92172a12f14d24c4467b2e58611afd726bd (HEAD -> master, origin/master, 
origin/HEAD)
Author: Paul B Mahol 
Date:   Fri Jul 10 23:04:49 2020 +0200

avfilter/vf_chromanr: move thres calculation to filter_frame()


and it seems to work, with following local patches:


x11_nonstd_prefix_compile_fixes.diff
cinelerra_dir_fixes_4.diff
db_compile_fixes.diff

-- for my non-std X11 prefix - probably one day conigure logic will be updated  
for pkg-config's X11 detection?

dri3_disable_cin51.diff | patch -p0

not sure, I still use dri2, but it doesn't hurt...

force_libvpx.diff

probably can be replaced with configure switches .. for now upgraded to libvpx 
1.8.2

nasm_thirdparty_2.patch

# nasm
cp $CWD/nasm-2.14.02.tar.xz thirdparty/src

builds nasm as thirdparty lib, after moving nasm source into tree ..

libva_x11r7.diff | patch -p0
libvdpau_x11r7.diff | patch -p0

once again my X11R7 prefix bites me 

git apply -v  $CWD/I-only_files_reverse_play_speedup.diff

not sure if speedup still here - DV file plays backward at 2x, but uses a lot 
of CPU (for such old codec)

# tmp for broken dv avi type file
cp $CWD/avi_fix.patch thirdparty/src/ffmpeg.git.patch20

hack moving avi handling into same special category as mkv
(+.flags  = AVFMT_SEEK_NOSTREAMS,)

git apply -v $CWD/thirdparty_build_trim-full.diff

removes ffmpeg tools, docs, livaom/libvpx/opus tools building ...

# lame patches
cp $CWD/lame-3.100-fastcrc.diff thirdparty/src/lame-3.100.patch1
git apply -v $CWD/lame-make-opt-after-th.diff

lame fastcrc patch for 32-bit x86 build

git apply -v $CWD/openCV4-static-gcc5_more-disable-3.diff

disables more stuff in OpenCV static build 

#x265 multidepth .a lib
cp $CWD/x265_3.4.patch1 thirdparty/src
cp $CWD/x265_3.4.patch2 thirdparty/src
cp $CWD/x265_3.4.patch3 thirdparty/src
patch -p1 < $CWD/x265_makefile-3.patch

x265 muiltilib (8-10-12 bits per component encoding in x265/HEVC) patches - 
seems to work 

guest@slax:~$ cin
Cinelerra Infinity - built: Jul 11 2020 10:07:03
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG 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.

init plugin index: /usr/lib/cin/plugins
PluginFFilter::new_ffilter(overlay_opencl)
  err: Ошибка ввода/вывода
PluginFFilter::new_ffilter(xfade_opencl)
  err: Ошибка ввода/вывода
[openclsrc_724 @ 0xd7bcc40] OpenCL source requires output dimensions to be 
specified.
PluginFFilter::new_ffilter(openclsrc)
  err: Недопустимый аргумент
init lv2 index:
LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_mono
LOAD: http://lsp-plug.in/plugins/lv2/comp_delay_stereo
LOAD: http://lsp-plug.in/plugins/lv2/compressor_lr
LOAD: http://lsp-plug.in/plugins/lv2/compressor_mono
LOAD: http://lsp-plug.in/plugins/lv2/compressor_ms
LOAD: http://lsp-plug.in/plugins/lv2/compressor_stereo
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_lr
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_mono
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_ms
LOAD: http://lsp-plug.in/plugins/lv2/dyna_processor_stereo
LOAD: http://lsp-plug.in/plugins/lv2/expander_lr
LOAD: http://lsp-plug.in/plugins/lv2/expander_mono
LOAD: http://lsp-plug.in/plugins/lv2/expander_ms
LOAD: http://lsp-plug.in/plugins/lv2/expander_stereo
LOAD: http://lsp-plug.in/plugins/lv2/gate_lr
LOAD: http://lsp-plug.in/plugins/lv2/gate_mono
LOAD: http://lsp-plug.in/plugins/lv2/gate_ms
LOAD: http://lsp-plug.in/plugins/lv2/gate_stereo
LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x16_mono
LOAD: http://lsp-plug.in/plugins/lv2/graph_equalizer_x32_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_responses_stereo
LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_mono
LOAD: http://lsp-plug.in/plugins/lv2/impulse_reverb_stereo
LOAD: http://lsp-plug.in/plugins/lv2/latency_meter
LOAD: http://lsp-plug.in/plugins/lv2/limiter_mono
LOAD: http://lsp-plug.in/plugins/lv2/limiter_stereo
LOAD: 

Re: [Cin] Debate on batch render

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 12 January 2021 00:57:48 Rafa Mar Multimedia en 
Gnu\Linux via Cin написал(а):
> I have forwarded this valuable information to you, and I hope it is not too
> late.
> I understand that a programmer likes to play with the code and do wonders,
> but you should consider that a video application is focused on people who
> are NOT computer scientists and that their knowledge is very basic.

Well, unlike closed-source applications you also can disable (at least) buttons 
you do not like
_locally_. Yes, such patch may create inconvience later on, if there will be 
changes in this  area upstream.

Sorry, I'm puzzled by another crash (Audacity 2.3.3 crash on launch, while 
2.3.2 works ?! on my system),
so I'm a bit distracted from CinelerraGG hacking right now 


> And 
> these options "cheat" rather than facilitate the work they make it
> difficult. The audiovisual technicians must be given the simple tools. I do
> not know of any application that I work with in my audiovisual professional
> field that has the ability to step on a backup by user interaction.
> To justify this I would tell you an anecdote that happened during the
> production of "Finding Nemo" by Andrew Stanton at Pixar. But I think I bore
> you with my long writings and I don't see an initiative to correct these
> "traps" that Cinelerra contains. Rather the opposite, a strong attitude in
> maintaining them.
> Perhaps it could be done as in Kdenlive, Adobe etc.., which after a sudden
> shutdown at the next start gives the option to recover the file that was
> being worked with. But I usually go to practicality and if something is not
> useful I eliminate it, I think that eliminating these options (also the
> batch render option) is easier than making special menus for them or what I
> just mentioned from kdenlive, which is usually what What applications do
> after a sudden shutdown.
> Anyway, thank you very much for the information, I know that some time ago
> you mentioned this about the backup, but I did not remember very well what
> it was like, and this user I suppose that when he wrote to me he would have
> already done tests that they will have overwritten this .prev file
> Greetings Phyllis.
> 
> El lun, 11 ene 2021 a las 21:56, Phyllis Smith via Cin (<
> cin@lists.cinelerra-gg.org>) escribió:
> 
> > RafaMar:
> >
> >> gave the option "Save backup" instead of "Load backup" and the poor man
> >> was desperate wondering if there was any way to get his work back,
> >>
> >
> > from the Manual, section 4.4.3:
> >
> > *"There is still 1 more backup that may save you. If for some reason you
> > forgot to use Load backup immediately when restarting or you did a Load
> > with Replace current project in your current session, you have a second
> > chance to use File → Load and select $HOME/.bcast5/backup.prev as long as
> > you only loaded a different file and have performed no editing operations."*
> >
> > I just tested this to verify that it works as stated.
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Debate on batch render

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 12 January 2021 03:27:41 Rafa Mar Multimedia en 
Gnu\Linux via Cin написал(а):
> Thanks Andrew, I don't know how to deactivate these buttons, and it's not
> my place to deactivate them either, I simply recommend from my experience
> to improve Cinelerra and make it interesting and without kamikaze functions.

Well, at the beginning I also know nothing about this particular codebase :}
Try to look at code and guess what line does this or that  comment it out, 
recompile, try to launch 



> I have Audacity 2.4.2 backport from Debian upstream running perfectly on
> Linux Mint 19.3, the only drawback is that the Calf effects interfaces are
> not graphically pretty, but I don't care, they work just as well with its
> retro-style interface from the late 90s.

:}

Yeah, sometimes binary distributions are fine, but mostly when someone already 
solved little things like 

https://forum.audacityteam.org/viewtopic.php?t=105237
https://forum.audacityteam.org/viewtopic.php?f=19=104224
(I hit error related to re-building right in source tree, instead of 'build' 
directory)

The I realized portaudio was patched in Ubuntu/Debian etc:

https://portaudio.music.columbia.narkive.com/rju8OHIE/pa-getstreamhostapitype

then I realized audacity will not link until you apply

https://gitweb.gentoo.org/repo/gentoo.git/tree/media-sound/audacity/files/audacity-2.3.3-Fix-building-against-system-portaudio.patch

:}

so, a lot of adventuring, but at least you can see CinGG is not only software 
using custom/patched libs ...

> I don't know what distribution you use, and I'm sure you know 1000 times
> more about this than I do, but just in case, the repositories that have
> allowed me to have Audacity 2.4.2 working perfectly are the ones on this
> website:
> https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/audacity
> 
> El lun, 11 ene 2021 a las 23:51, Andrew Randrianasulu via Cin (<
> cin@lists.cinelerra-gg.org>) escribió:
> 
> > В сообщении от Tuesday 12 January 2021 00:57:48 Rafa Mar Multimedia en
> > Gnu\Linux via Cin написал(а):
> > > I have forwarded this valuable information to you, and I hope it is not
> > too
> > > late.
> > > I understand that a programmer likes to play with the code and do
> > wonders,
> > > but you should consider that a video application is focused on people who
> > > are NOT computer scientists and that their knowledge is very basic.
> >
> > Well, unlike closed-source applications you also can disable (at least)
> > buttons you do not like
> > _locally_. Yes, such patch may create inconvience later on, if there will
> > be changes in this  area upstream.
> >
> > Sorry, I'm puzzled by another crash (Audacity 2.3.3 crash on launch, while
> > 2.3.2 works ?! on my system),
> > so I'm a bit distracted from CinelerraGG hacking right now 
> >
> >
> > > And
> > > these options "cheat" rather than facilitate the work they make it
> > > difficult. The audiovisual technicians must be given the simple tools. I
> > do
> > > not know of any application that I work with in my audiovisual
> > professional
> > > field that has the ability to step on a backup by user interaction.
> > > To justify this I would tell you an anecdote that happened during the
> > > production of "Finding Nemo" by Andrew Stanton at Pixar. But I think I
> > bore
> > > you with my long writings and I don't see an initiative to correct these
> > > "traps" that Cinelerra contains. Rather the opposite, a strong attitude
> > in
> > > maintaining them.
> > > Perhaps it could be done as in Kdenlive, Adobe etc.., which after a
> > sudden
> > > shutdown at the next start gives the option to recover the file that was
> > > being worked with. But I usually go to practicality and if something is
> > not
> > > useful I eliminate it, I think that eliminating these options (also the
> > > batch render option) is easier than making special menus for them or
> > what I
> > > just mentioned from kdenlive, which is usually what What applications do
> > > after a sudden shutdown.
> > > Anyway, thank you very much for the information, I know that some time
> > ago
> > > you mentioned this about the backup, but I did not remember very well
> > what
> > > it was like, and this user I suppose that when he wrote to me he would
> > have
> > > already done tests that they will have overwritten this .prev file
> > > Greetings Phyllis.
> > >
> > > El lun, 11 ene 2021 a las 21:56, Phyllis Smith via Cin (<
> > > cin@lists.cinelerra

Re: [Cin] Debate on batch render

[Andrew Randrianasulu via Cin]

В сообщении от Tuesday 12 January 2021 11:13:56 Rafa Mar Multimedia en 
Gnu\Linux via Cin написал(а):
> Thanks again Andrew. I hardly know how to add a repository and if it
> doesn't work or doesn't work correctly I go back to the previous one.
> Regards.

Ok, I think I disabled them by just commenting out their initialization.
Button and checkbox disappeared, but probably some state still will be around, 
so this
is NOT for merging, just for testing by interested parties .


diff --git a/cinelerra-5.1/cinelerra/batchrender.C 
b/cinelerra-5.1/cinelerra/batchrender.C
index 6dcdbc62..35822142 100644
--- a/cinelerra-5.1/cinelerra/batchrender.C
+++ b/cinelerra-5.1/cinelerra/batchrender.C
@@ -792,8 +792,8 @@ void BatchRenderGUI::create_objects()
y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
x = x2;  y = y2;
-   add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, 
y));
-   y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+// add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, 
y));
+// y += update_selected_edl->get_h() + mwindow->theme->widget_border;
add_subwindow(use_current_edl = new BatchRenderCurrentEDL(thread, x, 
y));
y += use_current_edl->get_h() + mwindow->theme->widget_border;
if( !mwindow->edl || !mwindow->edl->path[0] ) 
use_current_edl->disable();
@@ -805,8 +805,8 @@ void BatchRenderGUI::create_objects()
x += savelist_batch->get_w() + mwindow->theme->widget_border;
add_subwindow(loadlist_batch = new BatchRenderLoadList(thread, x, y));
y += loadlist_batch->get_h() + mwindow->theme->widget_border;
-   add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
-   y2 = y + warning->get_h() + mwindow->theme->widget_border;
+// add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
+// y2 = y + warning->get_h() + mwindow->theme->widget_border;
if( y2 > y1 ) y1 = y2;
x = mwindow->theme->batchrender_x1, y = y1;
 
---

Does new window look safer? If you think so - patch sources and try your 
workflow
while I'm thinking/learning about how to add warnings or conditionally 
show/hide those :}

I think my tooltips patch still applicable because it touches different 
block of code
diff --git a/cinelerra-5.1/cinelerra/batchrender.C b/cinelerra-5.1/cinelerra/batchrender.C
index 6dcdbc62..35822142 100644
--- a/cinelerra-5.1/cinelerra/batchrender.C
+++ b/cinelerra-5.1/cinelerra/batchrender.C
@@ -792,8 +792,8 @@ void BatchRenderGUI::create_objects()
 	y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
 	x = x2;  y = y2;
-	add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, y));
-	y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+//	add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, y));
+//	y += update_selected_edl->get_h() + mwindow->theme->widget_border;
 	add_subwindow(use_current_edl = new BatchRenderCurrentEDL(thread, x, y));
 	y += use_current_edl->get_h() + mwindow->theme->widget_border;
 	if( !mwindow->edl || !mwindow->edl->path[0] ) use_current_edl->disable();
@@ -805,8 +805,8 @@ void BatchRenderGUI::create_objects()
 	x += savelist_batch->get_w() + mwindow->theme->widget_border;
 	add_subwindow(loadlist_batch = new BatchRenderLoadList(thread, x, y));
 	y += loadlist_batch->get_h() + mwindow->theme->widget_border;
-	add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
-	y2 = y + warning->get_h() + mwindow->theme->widget_border;
+//	add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
+//	y2 = y + warning->get_h() + mwindow->theme->widget_border;
 	if( y2 > y1 ) y1 = y2;
 	x = mwindow->theme->batchrender_x1, y = y1;
 
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] UPD: Re: Debate on batch render

[Andrew Randrianasulu via Cin]

OH, NO, this patch actually breaks batch render :/
some more thinking needed even just for hiding this element .

SORRY!

PS; I see you can use batch render window _without_ any project loaded on 
timeline 

--  Пересланное сообщение  --

Тема: Re: [Cin] Debate on batch render
Дата: Вторник 12 января 2021
Отправитель: Andrew Randrianasulu 
Получатель:  "Cinelerra.GG" 

В сообщении от Tuesday 12 January 2021 11:13:56 Rafa Mar Multimedia en 
Gnu\Linux via Cin написал(а):
> Thanks again Andrew. I hardly know how to add a repository and if it
> doesn't work or doesn't work correctly I go back to the previous one.
> Regards.

Ok, I think I disabled them by just commenting out their initialization.
Button and checkbox disappeared, but probably some state still will be around, 
so this
is NOT for merging, just for testing by interested parties .


diff --git a/cinelerra-5.1/cinelerra/batchrender.C 
b/cinelerra-5.1/cinelerra/batchrender.C
index 6dcdbc62..35822142 100644
--- a/cinelerra-5.1/cinelerra/batchrender.C
+++ b/cinelerra-5.1/cinelerra/batchrender.C
@@ -792,8 +792,8 @@ void BatchRenderGUI::create_objects()
y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
x = x2;  y = y2;
-   add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, 
y));
-   y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+// add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, 
y));
+// y += update_selected_edl->get_h() + mwindow->theme->widget_border;
add_subwindow(use_current_edl = new BatchRenderCurrentEDL(thread, x, 
y));
y += use_current_edl->get_h() + mwindow->theme->widget_border;
if( !mwindow->edl || !mwindow->edl->path[0] ) 
use_current_edl->disable();
@@ -805,8 +805,8 @@ void BatchRenderGUI::create_objects()
x += savelist_batch->get_w() + mwindow->theme->widget_border;
add_subwindow(loadlist_batch = new BatchRenderLoadList(thread, x, y));
y += loadlist_batch->get_h() + mwindow->theme->widget_border;
-   add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
-   y2 = y + warning->get_h() + mwindow->theme->widget_border;
+// add_subwindow(warning = new BatchRenderWarning(thread, x2, y));
+// y2 = y + warning->get_h() + mwindow->theme->widget_border;
if( y2 > y1 ) y1 = y2;
x = mwindow->theme->batchrender_x1, y = y1;
 
---

Does new window look safer? If you think so - patch sources and try your 
workflow
while I'm thinking/learning about how to add warnings or conditionally 
show/hide those :}

I think my tooltips patch still applicable because it touches different 
block of code

---
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Attempt at disabling 'Save to EDL' in batchrender GUI at compile-time

[Andrew Randrianasulu via Cin]

This one survived actual batch render - I forgot about enable/disable button 
calls 

so, if you set UNSAFE_BUTTON to 1 it will appear, if you leave it at 0 it will 
be hidden.
Now, if THIS patch actually works we can think about hooking it up to pref 
window .


---

diff --git a/cinelerra-5.1/cinelerra/batchrender.C 
b/cinelerra-5.1/cinelerra/batchrender.C
index 6dcdbc62..d85d0e8c 100644
--- a/cinelerra-5.1/cinelerra/batchrender.C
+++ b/cinelerra-5.1/cinelerra/batchrender.C
@@ -60,6 +60,8 @@
 #include "dvdcreate.h"
 #include "bdcreate.h"
 
+#define UNSAFE_BUTTON 0
+
 int BatchRenderThread::column_widths[] = { 42, 42, 42, 222, 222, 150 };
 const char *BatchRenderThread::column_titles[] = {
N_("Enabled"), N_("Labeled"), N_("Farmed"), N_("Output"), N_("EDL"), 
N_("Elapsed")
@@ -382,6 +384,7 @@ void BatchRenderThread::use_current_edl()
gui->edl_path_text->update(get_current_edl());
 }
 
+
 void BatchRenderThread::update_selected_edl()
 {
 FileXML xml_file;
@@ -396,6 +399,8 @@ void BatchRenderThread::update_selected_edl()
}
 }
 
+
+
 BatchRenderJob* BatchRenderThread::get_current_job()
 {
return current_job >= 0 && current_job < jobs.total ?
@@ -792,8 +797,11 @@ void BatchRenderGUI::create_objects()
y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
x = x2;  y = y2;
+   if (UNSAFE_BUTTON) {
add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, 
y));
y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+}
+
add_subwindow(use_current_edl = new BatchRenderCurrentEDL(thread, x, 
y));
y += use_current_edl->get_h() + mwindow->theme->widget_border;
if( !mwindow->edl || !mwindow->edl->path[0] ) 
use_current_edl->disable();
@@ -835,6 +843,7 @@ void BatchRenderGUI::button_disable()
new_batch->disable();
delete_batch->disable();
use_current_edl->disable();
+   if (UNSAFE_BUTTON)
update_selected_edl->disable();
 }
 
@@ -844,6 +853,7 @@ void BatchRenderGUI::button_enable()
delete_batch->enable();
if( mwindow->edl && mwindow->edl->path[0] )
use_current_edl->enable();
+   if (UNSAFE_BUTTON)
update_selected_edl->enable();
 }
 
@@ -876,8 +886,10 @@ int BatchRenderGUI::resize_event(int w, int h)
y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
x = x2;  y = y2;
+   if (UNSAFE_BUTTON) {
update_selected_edl->reposition_window(x, y);
y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+}
use_current_edl->reposition_window(x, y);
y += use_current_edl->get_h() + mwindow->theme->widget_border;
new_batch->reposition_window(x, y);
@@ -1236,6 +1248,7 @@ int BatchRenderCurrentEDL::handle_event()
return 1;
 }
 
+
 BatchRenderUpdateEDL::BatchRenderUpdateEDL(BatchRenderThread *thread,
int x,
int y)
@@ -1244,8 +1257,10 @@ 
BatchRenderUpdateEDL::BatchRenderUpdateEDL(BatchRenderThread *thread,
this->thread = thread;
 }
 
+
 int BatchRenderUpdateEDL::handle_event()
 {
+   if (UNSAFE_BUTTON)
thread->update_selected_edl();
return 1;
 }


diff --git a/cinelerra-5.1/cinelerra/batchrender.C b/cinelerra-5.1/cinelerra/batchrender.C
index 6dcdbc62..d85d0e8c 100644
--- a/cinelerra-5.1/cinelerra/batchrender.C
+++ b/cinelerra-5.1/cinelerra/batchrender.C
@@ -60,6 +60,8 @@
 #include "dvdcreate.h"
 #include "bdcreate.h"
 
+#define UNSAFE_BUTTON 0
+
 int BatchRenderThread::column_widths[] = { 42, 42, 42, 222, 222, 150 };
 const char *BatchRenderThread::column_titles[] = {
 	N_("Enabled"), N_("Labeled"), N_("Farmed"), N_("Output"), N_("EDL"), N_("Elapsed")
@@ -382,6 +384,7 @@ void BatchRenderThread::use_current_edl()
 	gui->edl_path_text->update(get_current_edl());
 }
 
+
 void BatchRenderThread::update_selected_edl()
 {
 FileXML xml_file;
@@ -396,6 +399,8 @@ void BatchRenderThread::update_selected_edl()
 	}
 }
 
+
+
 BatchRenderJob* BatchRenderThread::get_current_job()
 {
 	return current_job >= 0 && current_job < jobs.total ?
@@ -792,8 +797,11 @@ void BatchRenderGUI::create_objects()
 	y2 = y + edl_path_browse->get_h() + mwindow->theme->widget_border;
 
 	x = x2;  y = y2;
+	if (UNSAFE_BUTTON) {
 	add_subwindow(update_selected_edl = new BatchRenderUpdateEDL(thread, x, y));
 	y += update_selected_edl->get_h() + mwindow->theme->widget_border;
+}
+
 	add_subwindow(use_current_edl = new BatchRenderCurrentEDL(thread, x, y));
 	y += use_current_edl->get_h() + mwindow->theme->widget_border;
 	if( !mwindow->edl || !mwindow->edl->path[0] ) use_current_edl->disable();
@@ -835,6 +843,7 @@ void BatchRenderGUI::button_disable()
 	new_batch->disable();
 	delete_batch->disable();
 	use_current_edl->disable();
+	if (UNSAFE_BUTTON)
 	update_selected_edl->disable();
 }
 
@@ -844,6 +853,7 @@ void BatchRenderGUI::button_enable()
 	delete_batch->enable();
 	if( mwindow->edl && 

Re: [Cin] patch for 16:10 aspect ratio

[Andrew Randrianasulu via Cin]

В сообщении от Friday 27 November 2020 03:29:47 Phyllis Smith via Cin 
написал(а):
> Andrew,
> Also tested and checked into GIT, the 16_10_plus_formats patch to add the
> 16:10 aspect ratio and additional formats.  There are a LOT of formats now
> and it seems like the world keeps inventing new ones.  But at least you
> have got this updated for now.  Thanks.

Thank  *you*!

/me sends virtual hughs to Phyllis, of types she prefer/accept now.

> 
> On Sat, Oct 31, 2020 at 5:05 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > Spend some time looking at where exactly those settings were located.
> > Turned out in theme.C :}
> >
> > diff --git a/cinelerra-5.1/cinelerra/theme.C
> > b/cinelerra-5.1/cinelerra/theme.C
> > index d89c789f..ea96309c 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"));
> >
> > --
> >
> > Some presets in defaultformats.h may also benefit from upgrade?
> > But what kind of new formats we might want to add there? Just higher
> > resolution ones?
> >
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Use MAXCHANNELS define in mwindow.C

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 21 November 2020 14:06:48 Igor BEGHETTO via Cin 
написал(а):
> Andrew and all,
> Here an example because I think it was right as before.
> In the screencast I am using a video file by Pierre ( 
> http://www.gvgdevelopers.com/K2DevGuide/Clips2/NTSC_SD_DV25_colorbar.avi 
> ) to show what I said.
> The source video "NTSC_SD_DV25_colorbar.avi"  has 8 audio stereo 
> channels. So, with your change, Cinelerra-GG will create 16 audio 
> channels instead of 6, because MAXCHANNELS=32. IMHO, I think it would be 
> too much.

well, today you can hide/fold  them behind gang mode ...?

But yes, I did this change especially  due to this file.

Most of those channels in this specific file are empty (only 4 are carrying 
sound), but for me this showed fact files with more than 6 ch. exist, and so 
loading them will raise '?' in user 

I even saw talk about something like 20+ ch. surround audio at ffmpeg-devel 
(but I have no such file yet to test).

https://en.wikipedia.org/wiki/MPEG-H_3D_Audio
(I don't think Cin can do real 3d sound, it all confined  to single horizontal 
plane, yet  such strangeness [128 core + 64 loudspeakers max!] now exist .)

You always can delete unneeded tracks, but from what I recall loading 4ch audio 
+ 1 ch. video file to 1 vid ch/2 aud. ch project will result in some reposition 
of audio tracks, enlarging  project's total timeline  

But to be honest right now I'm unsure and much more concerned  about who will 
land any of those mods  this particular change can be dropped, but who will 
apply others 


> You can confirm or less if that code is for that feature.
> Screencast to https://streamable.com/woem2b
> Thanks!
> 
> IgorBeg
> 
> Il 19/11/2020 03:07, Andrew Randrianasulu via Cin ha scritto:
> > 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];
> >
> > =
> >
> >
> >


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Upd: I tried to run CinGG under valgrind, on application restart...

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 25 November 2020 22:01:06 Phyllis Smith via Cin 
написал(а):
> Andrew,
> The following does look like an un-intialized variable in Cinelerra the
> first time and then after that it is initialized.  Looks like a minor bug
> maybe.  Patch?

If only i was THAT good  but may be eventually I figure this out ..

> 
> On Tue, Nov 3, 2020 at 2:11 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > Also tried to remove one (video) track from (1+2) default project.
> > Then undo with 'z'
> >
> > ==18036== Conditional jump or move depends on uninitialised value(s)
> > ==18036==at 0x86FB8FB: Tracks::load(FileXML*, int&, unsigned int) (in
> > /usr/bin/cin)
> > ==18036==by 0x8552D4A: EDL::read_xml(FileXML*, unsigned int) (in
> > /usr/bin/cin)
> > ==18036==by 0x8552889: EDL::load_xml(FileXML*, unsigned int) (in
> > /usr/bin/cin)
> > ==18036==by 0x85E0E5D: MainUndo::load_from_undo(FileXML*, unsigned
> > int) (in /usr/bin/cin)
> > ==18036==by 0x85E0D04: MainUndo::undo() (in /usr/bin/cin)
> > ==18036==by 0x8603DEF: MWindow::undo_entry(BC_WindowBase*) (in
> > /usr/bin/cin)
> > ==18036==by 0x85D6D3D: Undo::handle_event() (in /usr/bin/cin)
> > ==18036==by 0x87ACE00: BC_MenuItem::dispatch_key_press() (in
> > /usr/bin/cin)
> > ==18036==by 0x87ADDC4: BC_MenuPopup::dispatch_key_press() (in
> > /usr/bin/cin)
> > ==18036==by 0x87AB7B6: BC_Menu::dispatch_keypress() (in /usr/bin/cin)
> > ==18036==by 0x87AC341: BC_MenuBar::keypress_event() (in /usr/bin/cin)
> > ==18036==by 0x87DCABE: BC_WindowBase::dispatch_keypress_event() (in
> > /usr/bin/cin)
> > ==18036==
> >
> > but this one  printed just once - I tried to 'remove track/undo by z'
> > second time and this message doesn't show up.
> >
> >
> > --  Пересланное сообщение  --
> >
> >
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] DNxHR presets

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 26 November 2020 01:20:14 Phyllis Smith via Cin 
написал(а):
> Andrew,  I have successfully tested these 3 + the 2 latest versions of LB
> and SQ from a subsequent email.  And also the 2 audio ones.  I would like
> to check them into GIT but was wondering if it would not be more consistent
> to use all lowercase letters instead of capital letters for file names?
> What do you think?  So instead of DNxHR_HQ.mov it would be dnxhr_hq.mov.
> All of the other formats (with one exception) seem to be lower case.

I just keep them named like they were named initially, but I agree making 
naming consistent is good. Go for lowercase!

> 
> On Mon, Nov 9, 2020 at 9:52 AM Andrew Randrianasulu via Cin <
> cin@lists.cinelerra-gg.org> wrote:
> 
> > 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 0x63:
> >   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 0x63:
> >   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)
> > --
> > Cin mailing list
> > Cin@lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Not quite correct patch for toggling various windows from mainmenu->window submenu

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 02 December 2020 06:24:15 Phyllis Smith via Cin 
написал(а):
> Andrew,
> This patch has been tested on my laptop and I did not encounter a problem.
> Is there still a problem with this "Not quite correct patch"? so that it
> should not be checked into GIT?

I dunno. I most afraid of hidden memleak/reference counting problem ..try few 
cinGG instances at once?

> 
> Well, I'm fairly sure
> >
> > void MWindow::hide_vwindow() kinda wrong (because copypasta!)
> >
> > but it seems to work for single viewer window I wanted to hide via  this
> > menu.
> >
> >
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Interlace driving me mad .....

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 02 December 2020 02:27:43 Phyllis Smith via Cin 
написал(а):
> Andrew,
> I could not reproduce the crash I got the other day so have finally *checked
> into GIT interlace_aspect_autodetect-12.patch *(from the ru download
> site).  I tested and saw the correct interlace mode in the Resources window
> media folder "info" and under Settings->Format.  Also looked at the code
> but I do not know much about C++.  But the one thing that I for sure do not
> comprehend in the patch is the section in fileffmpeg.C about the Fixups
> (maybe this was explained in a different email though):

Well, if you try to bring up 'format options' for say mkv or qt format CinGG 
will complain without this patch
Just names used  for format (container) not always match what 
libavcodec/libavformat use ...
This code tries to fix up difference, so you can set some of container options 
via GUI now.

> 
> Asset *asset = fmt_config->asset;
> char *format_name = asset->fformat;
> +   char *replace_name0 = "mov";
> +   char *replace_name1 = "mpegts";
> +   char *replace_name2 = "matroska";
> +   if (!strcmp(format_name, "qt"))
> +   format_name = replace_name0; // fixup
> +   if (!strcmp(format_name, "m2ts"))
> +   format_name = replace_name1; // fixup
> +   if (!strcmp(format_name, "mkv"))
> +   format_name = replace_name2; // fixup
> 
> And in mwindow.C, why is it needed to specifically add the following?:

well, in theory  this must be function, not code duplication ..
this just sets session (display) aspect ratio   (so if you bring up 'mainwindow 
menu->Format' you 
will see correcty-picked up values, not default 4:3)

I'm a bit confused between session vs asset, because encoding for example seems 
to use 
asset's parameters (or may be they just stored there).

> 
> +   float ar = asset->aspect_ratio;
> +   if (ar) {
> +   //printf ("Aspect ratio from asset: %f \n", ar);
> +   if( EQUIV(ar, 1.) ) { session->aspect_w = 4;  session->aspect_h
> = 3;  }
> +   if( EQUIV(ar, 1.) ) { session->aspect_w = 16; session->aspect_h
> = 9;   }
> +   if( EQUIV(ar, 2.) ) { session->aspect_w = 19; session->aspect_h
> = 9;  }
> +   if( EQUIV(ar, 2.) ) { session->aspect_w = 20; session->aspect_h
> = 9;   }
> +   if( EQUIV(ar, 2.) ) { session->aspect_w = 21; session->aspect_h
> = 9;   }
> +   if( EQUIV(ar, 2.370370) ) { session->aspect_w = 64;
> session->aspect_h = 27; }
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Missing plugin MOTION CV caused heavy error

[Andrew Randrianasulu via Cin]

В сообщении от Monday 07 December 2020 19:07:35 August Geyler via Cin 
написал(а):
> Hello everyone,
> 
> I need your support for making the Motion CV plugin usable for me again. 
> The background: I started working on a huge project in April this year 
> with my team. We made heavy use of motion tracking. To achieve this we 
> made several tests with all available motion plugins in April 2020 and 
> decided to only use "Motion CV". Nobody knew, we chose an effect which 
> would deleted only few month later. I couldn't even imagine something 
> like this happening.
> 
> We worked on our project for more than a month. Due to the pandemic it 
> came to a sudden hold in May. Today we wanted to start finishing the 
> project. When I opened the file in Cinelerra I surprisingly got the 
> massage that the effect "Motion CV" was unknown. As I figured out, you 
> deleted this plugin in September. I am happy to hear that the new motion 
> plugin is much better and I will use it in the future. But now I need to 
> render my project from April exactly in the way it was made. But this is 
> impossible now due to the disappearance of our most used effect. I 
> checked the syntax in the project XML. There are several differences 
> between "Motion" and "Motion CV" so that just renaming the effect in the 
> file did not work.
> 
> I red that the old motion cv plugin is still in the libraries and 
> downloaded it. But as I have no clue how to reinstall this into my 
> running system I need your support. The handbook is not describing how 
> to reinstall deleted plugins.

I think you can rebuild CinGG with this part of patch reverted:

https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blobdiff;f=cinelerra-5.1/plugins/Makefile;h=178e0ef210f49b3f291973efc9194b71d373d43b;hp=05323bb86c1fea75ec73a91ef63a24e9363f74ef;hb=abdff69b9309c7d5cd2ed6ce17dd2e0d85aef9a1;hpb=0b751b07a28e84a721b2bb76083db6629aa26d73

diff --git a/cinelerra-5.1/plugins/Makefile b/cinelerra-5.1/plugins/Makefile
 index 
05323bb86c1fea75ec73a91ef63a24e9363f74ef..178e0ef210f49b3f291973efc9194b71d373d43b
 100644 (file)
 
--- a/cinelerra-5.1/plugins/Makefile
+++ b/cinelerra-5.1/plugins/Makefile
@@ -101,8 +101,6 @@ DIRS = $(OPENCV_OBJS) \
loopvideo \
motion \
motion51 \
-   motion-cv \
-   motion-hv \
motion2point \
motionblur \
normalize \
@@ -171,6 +169,9 @@ DIRS = $(OPENCV_OBJS) \
theme_unflat \
theme_cakewalk \
 
+# not maintained
+#  motion-cv \
+#  motion-hv \
 # too costly
 #  findobject \
 #  greycstoration \


basically remove "#" before motion-cv line, and build as usual

Installed plugins on 32-bit system live (by default) in /usr/lib/cin/plugins,

for 64-bit look at /usr/lib64/cin/plugins

i think 

not sure if binary plugins from older version of CinGG will work in new :/

> 
> Is it possible to reinstall the plugin by myself? Or can you provide the 
> plugin again with the next update?
> 
> I'm looking forward hearing from you to save all the work we had with 
> our project.
> 
> Best regards,
> 
> August
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Interlace driving me mad .....

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 02 December 2020 13:02:56 Andrea paz via Cin 
написал(а):
> With the last git I can no longer see the png. Both in resources and
> timeline are not seen. In the terminal I have the following messages:
> 
> Cinelerra Infinity - built: Dec  2 2020 10:36:34
> git://git.cinelerra-gg.org/goodguy/cinelerra.git
> (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> 2007-2020 mods for Cinelerra-GG 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.
> 
> sample_aspect_ratio, 1.00
> display_aspect_ratio, 1.78
> ff_aspect_ratio, 1.78
> interlace from demux: 0
> sample_aspect_ratio, 1.00
> display_aspect_ratio, 1.78
> ff_aspect_ratio, 1.78
> interlace from demux: 0
> sample_aspect_ratio, 1.00
> display_aspect_ratio, 1.78
> ff_aspect_ratio, 1.78
> FFMPEG::open_decoder: some stream have bad times:
> /home/paz/video_editing/prova/1080/0003.png
> ff_aspect_ratio, 0.00
> interlace from demux: 0
> FFMPEG::open_decoder: some stream have bad times:
> /home/paz/video_editing/prova/1080/0004.png
> ff_aspect_ratio, 0.00
> interlace from demux: 0
> sample_aspect_ratio, 1.00
> display_aspect_ratio, 1.78
> ff_aspect_ratio, 1.78
> interlace from demux: 0
> sample_aspect_ratio, 1.00
> display_aspect_ratio, 1.78
> ff_aspect_ratio, 1.78
> 
> 
> The error "some stream have bad times:" always gave it to me, but the
> pngs saw the same.
> 
> 
> EDIT: the same problem with jpg. An animated gif works.
> 

Yeah, for some reason it doesn't work with images-as-decoded-via-ffmpeg

Try attached patch?

diff --git a/cinelerra-5.1/cinelerra/fileffmpeg.C 
b/cinelerra-5.1/cinelerra/fileffmpeg.C
index eed14f20..387c0f69 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -342,11 +342,13 @@ int FileFFMPEG::open_file(int rd, int wr)
int video_layers = ff->ff_total_video_layers();
if( video_layers > 0 ) {
asset->video_data = 1;
+   if ((ff->ff_video_codec(0) != "png" || 
(ff->ff_video_codec(0) != "mjpeg")) && (ff->ff_video_frames(0) > 1 )) {
asset->aspect_ratio = ff->ff_aspect_ratio(0);
printf("ff_aspect_ratio, %f \n", 
asset->aspect_ratio);
if (!asset->interlace_mode) 
asset->interlace_mode = ff->ff_interlace(0);
ff->video_probe(1);
 if (!asset->interlace_mode && 
(ff->interlace_from_codec) ) asset->interlace_mode = ff->video_probe(1); 
+   }
if( !asset->layers ) asset->layers = 
video_layers;
asset->actual_width = ff->ff_video_width(0);
asset->actual_height = ff->ff_video_height(0);


I dunno how it should react to, say, interlaced png wrapped in mov  
Hopefully just skip ar/interlace setup, as it did before.
(but at least you will have image visible)
diff --git a/cinelerra-5.1/cinelerra/fileffmpeg.C b/cinelerra-5.1/cinelerra/fileffmpeg.C
index eed14f20..387c0f69 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -342,11 +342,13 @@ int FileFFMPEG::open_file(int rd, int wr)
 			int video_layers = ff->ff_total_video_layers();
 			if( video_layers > 0 ) {
 asset->video_data = 1;
+if ((ff->ff_video_codec(0) != "png" || (ff->ff_video_codec(0) != "mjpeg")) && (ff->ff_video_frames(0) > 1 )) {
 asset->aspect_ratio = ff->ff_aspect_ratio(0);
 printf("ff_aspect_ratio, %f \n", asset->aspect_ratio);
 if (!asset->interlace_mode) asset->interlace_mode = ff->ff_interlace(0);
 ff->video_probe(1);
  if (!asset->interlace_mode && (ff->interlace_from_codec) ) asset->interlace_mode = ff->video_probe(1); 
+}
 if( !asset->layers ) asset->layers = video_layers;
 asset->actual_width = ff->ff_video_width(0);
 asset->actual_height = ff->ff_video_height(0);
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Interlace driving me mad .....

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 02 December 2020 16:47:05 Georgy Salnikov via Cin 
написал(а):
> On Wed, 2 Dec 2020, Andrew Randrianasulu via Cin wrote:
> 
> > > With the last git I can no longer see the png. Both in resources and
> > > timeline are not seen. In the terminal I have the following messages:
> 
> Must PNG work under ffmpeg at all? I think, I have seen somewhere in CGG
> manual that ffmpeg did not work with picture files (picture series?), so I
> loaded them always switching to 'try ffmpeg last' not testing the opposite.

I think it still works with single images, because my fiddling with 
fileffmpeg.C changes result (works/not) 

I narrowed failure to my probe function, it doesn't like single images, so I 
if'ed them away 
(and not png/mjpeg codecs *plus* ff_video_frames >1  conditional as in my prev. 
patch)

New patch attached

===

diff --git a/cinelerra-5.1/cinelerra/fileffmpeg.C 
b/cinelerra-5.1/cinelerra/fileffmpeg.C
index eed14f20..43ed758b 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -345,8 +345,10 @@ int FileFFMPEG::open_file(int rd, int wr)
asset->aspect_ratio = ff->ff_aspect_ratio(0);
printf("ff_aspect_ratio, %f \n", 
asset->aspect_ratio);
if (!asset->interlace_mode) 
asset->interlace_mode = ff->ff_interlace(0);
+   if ( ff->ff_video_frames(0) > 1 ) {
ff->video_probe(1);
 if (!asset->interlace_mode && 
(ff->interlace_from_codec) ) asset->interlace_mode = ff->video_probe(1); 
+   }
if( !asset->layers ) asset->layers = 
video_layers;
asset->actual_width = ff->ff_video_width(0);
asset->actual_height = ff->ff_video_height(0);



But yes, loading jpegs/pngs with 'try ffmpeg last' also workaround my bug 

This hopefully still gives interlace/aspect autodetection (tested with m2t 
file), yet images should 
work as before ...


Sorry!

> 
> ___
> 
> Georgy Salnikov
> NMR Group
> Novosibirsk Institute of Organic Chemistry
> Lavrentjeva, 9, 630090 Novosibirsk, Russia
> Phone   +7-383-3307864
> Email   s...@nmr.nioch.nsc.ru
> ___
> 


diff --git a/cinelerra-5.1/cinelerra/fileffmpeg.C b/cinelerra-5.1/cinelerra/fileffmpeg.C
index eed14f20..43ed758b 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -345,8 +345,10 @@ int FileFFMPEG::open_file(int rd, int wr)
 asset->aspect_ratio = ff->ff_aspect_ratio(0);
 printf("ff_aspect_ratio, %f \n", asset->aspect_ratio);
 if (!asset->interlace_mode) asset->interlace_mode = ff->ff_interlace(0);
+if ( ff->ff_video_frames(0) > 1 ) {
 ff->video_probe(1);
  if (!asset->interlace_mode && (ff->interlace_from_codec) ) asset->interlace_mode = ff->video_probe(1); 
+}
 if( !asset->layers ) asset->layers = video_layers;
 asset->actual_width = ff->ff_video_width(0);
 asset->actual_height = ff->ff_video_height(0);
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Sad news: Our developer Good Guy has passed away

[Andrew Randrianasulu via Cin]

В сообщении от Monday 09 November 2020 22:57:29 Sam via Cin написал(а):
> 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.


Oh shit, this is ..one of the worst kind of surprizes to get via email update 


I'm speechless too.

> 
> 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.

Absolutely agree!

> 
> 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.

Thanks for staying up with us..
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] UPD: Re: DNxHR presets

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 11 November 2020 13:28:21 Andrea paz via Cin 
написал(а):
> 1- I compiled from root, but the result doesn't change: your presets
> don't work in my CinGG; it only offers the yuv420p option which, not
> being supported, produces error.
> 
> 2- I compiled from root with the ./build.sh provided by GG but the
> result is the same as point 1-
> 
> 3- I compiled with ffmpeg-git --> compile error

yeah, I removed bigger patch (it basically adds fixes for blu-ray creation - I 
have no such device):

mv thirdparty/src/ffmpeg.git.patch2  thirdparty/src/_ffmpeg.git.patch2

this way it really not picked up by build.

> 
> The trouble is that I compile with the copy and paste, without knowing
> what I do.
> The steps I use are:
> 
> $ git clone --depth 1
> "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5
> 
> $ cd /home/paz/cinelerra5/cinelerra-5.1
> 
> $ ./autogen.sh
> 
> $ ./configure --without-oss --with-single-user --with-booby
> --with-opencv=sta,tar=http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz


Most bigger difference is "--with-single-user", as far as I can see... I do 
system-build

May be some pathes are too long?
Where exactly you put those profile files?

/home/paz/cinelerra5/cinelerra-5.1/bin something ?

I'll try --single-user somemoment later.


> 
> $ make 2>&1 | tee /tmp/cin5.log && make install
> 
> All this without being Root.
> 
> Do you think I'm wrong? Should I try your ./configure? (but most of
> the strings I don't understand them!)


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] UPD: Re: DNxHR presets

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 11 November 2020 17:03:46 Andrea paz via Cin 
написал(а):
> >
> > May be some pathes are too long?
> > Where exactly you put those profile files?
> >
> 
> /home/paz/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/DNxHR_444.mov
> 
> about 70 characters.

Just compiled Cin with just one switch:

 ./configure --with-single-use

it worked with some local hacks (/usr/X11R7 for X libs, disabling swscale 
integration in x264 snapshot)

I can load my profile to

/dev/shm/cinelerra/cinelerra-5.1$ ls bin/ffmpeg/video/
DNxHR_HQX.mov

and it show up correctly and let me render.

Does your build enable vdpau/vaapi? As far as I can see those options loaded in

https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/cinelerra/ffmpeg.C;h=97b6698acbb2ffc342f93049dbd54537d0a39235;hb=HEAD

2081 
2082 void FFMPEG::scan_video_options(Asset *asset, EDL *edl)
2083 {
2084 char cin_pix_fmt[BCSTRLEN];
2085 int cin_fmt = AV_PIX_FMT_NONE;
2086 const char *options = asset->ff_video_options;
2087 if( !get_ff_option("cin_pix_fmt", options, cin_pix_fmt) )
2088 cin_fmt = (int)av_get_pix_fmt(cin_pix_fmt);
2089 if( cin_fmt < 0 ) {
2090 char video_codec[BCSTRLEN];  video_codec[0] = 0;
2091 AVCodec *av_codec = !get_codec(video_codec, "video", 
asset->vcodec) ?
2092 avcodec_find_encoder_by_name(video_codec) : 0;
2093 if( av_codec && av_codec->pix_fmts ) {
2094 if( 0 && edl ) { // frequently picks a bad answer
2095 int color_model = 
edl->session->color_model;
2096 int max_bits = 
BC_CModels::calculate_pixelsize(color_model) * 8;
2097 max_bits /= 
BC_CModels::components(color_model);
2098 cin_fmt = 
avcodec_find_best_pix_fmt_of_list(av_codec->pix_fmts,
2099 (BC_CModels::is_yuv(color_model) ?
2100 (max_bits > 8 ? 
AV_PIX_FMT_AYUV64LE : AV_PIX_FMT_YUV444P) :
2101 (max_bits > 8 ? 
AV_PIX_FMT_RGB48LE : AV_PIX_FMT_RGB24)), 0, 0);
2102 }
2103 else
2104 cin_fmt = av_codec->pix_fmts[0];
2105 }
2106 }
2107 if( cin_fmt < 0 ) cin_fmt = AV_PIX_FMT_YUV420P;


search for 'cin_pix_fmt'

so for some reason it fails to find best format via 
avcodec_find_best_pix_fmt_of_list ?

Also, I tried with default RGBA-8 colormodel . may be it fails with 
YUV/RGBA-float?

no, seems to work too 

You can try and add printf("doing X \n"); in this function and see that branch 
it takes :} and also print out exact value of  cin_fmt

printf("cin_fmt= %i \n", cin_fmt);

something like this ...

> 
> @MatN
> can you try to put Andrew's presets in your CinGG to see if they work for you?
> The path should be:
> 
> /home/USER/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] actually, added few more formats to theme.C

[Andrew Randrianasulu via Cin]

В сообщении от Wednesday 11 November 2020 20:12:44 Terje J. Hanssen via Cin 
написал(а):
> I will just add that the HDV format consist of three versions:
> https://en.wikipedia.org/wiki/HDV#Specifications
> 
> HDV 720p
> 720p/60, 720p/30, 720p/24, 720p/50, 720p/25

but may be those can be already selected, just not as preset with HDV in name?

> 
> HDV 1080i
> 1080i/30 (29.97), 1080i/25
> 
> HDV 1080p
> 1080p/30 (29.97), 1080p/24 (23.98), 1080p/25

Those seems  to be more tricky, because I still not sure how they should show 
up in Compositor and Viewer. With correct-for-display aspect ratio? But then 
how masks/titles will work?

> 
> 
> At the same time I will also suggest to consistently use lower case "i" 
> for all interlaced HDV and HD formats like that on the SD formats.
> Attached screen shots from the Set_Format_Preset menue.

ok 
> 
> 
> Terje J. H
> 
> 
> 
> 
> Den 01.11.2020 19:35, skrev Pierre autourduglobe via Cin:
> > Yes it's clear
> > HDV 1080i "Top field first"
> > and DV "Bottom field first"
> >
> > In my case I can verify this with my old HDV camera HVR-Z1U, which can 
> > record and transfer either in HDV or DV (ntsc).
> >
> > Here is what mediainfo says about the material shot:
> >
> >
> > An example of HDV material
> >
> > General
> > ID   : 255 (0xFF)
> > Complete name    : exemple.m2t
> > Format   : MPEG-TS
> > Commercial name  : HDV 1080i
> > File size    : 30.2 MiB
> > Duration : 10s 878ms
> > Start time   : UTC 2016-01-11 11:15:03
> > End time : UTC 2016-01-11 11:15:14
> > Overall bit rate mode    : Variable
> > Overall bit rate : 23.2 Mbps
> > Maximum Overall bit rate : 33.0 Mbps
> > Encoded date : UTC 2016-01-11 11:15:03
> >
> > Video
> > ID   : 2064 (0x810)
> > Menu ID  : 100 (0x64)
> > Format   : MPEG Video
> > Commercial name  : HDV 1080i
> > Format version   : Version 2
> > Format profile   : Main@High 1440
> > Format settings, BVOP    : Yes
> > Format settings, Matrix  : Default
> > Format settings, GOP : M=3, N=15
> > Format settings, picture structure   : Frame
> > Codec ID : 2
> > Duration : 10s 544ms
> > Bit rate : 21.7 Mbps
> > Maximum bit rate : 25.0 Mbps
> > Width    : 1 440 pixels
> > Height   : 1 080 pixels
> > Display aspect ratio : 16:9
> > Frame rate   : 29.970 (3/1001) fps
> > Standard : Component
> > Color space  : YUV
> > Chroma subsampling   : 4:2:0
> > Bit depth    : 8 bits
> > Scan type    : Interlaced
> > Scan order   : Top Field First
> > Compression mode : Lossy
> > Bits/(Pixel*Frame)   : 0.466
> > Stream size  : 27.3 MiB (90%)
> > Color primaries  : BT.709
> > Transfer characteristics : BT.709
> > Matrix coefficients  : BT.709
> >
> > Audio
> > ID   : 2068 (0x814)
> > Menu ID  : 100 (0x64)
> > Format   : MPEG Audio
> > Format version   : Version 1
> > Format profile   : Layer 2
> > Codec ID : 3
> > Duration : 10s 584ms
> > Bit rate mode    : Constant
> > Bit rate : 384 Kbps
> > Channel(s)   : 2 channels
> > Sampling rate    : 48.0 KHz
> > Compression mode : Lossy
> > Delay relative to video  : -252ms
> > Stream size  : 496 KiB (2%)
> >
> > Menu
> > ID   : 129 (0x81)
> > Menu ID  : 100 (0x64)
> > List : 2064 (0x810) (MPEG Video) / 
> > 2068 (0x814) (MPEG Audio) / 2069 (0x815) () / 2065 (0x811) ()
> >
> >
> >
> > An example of DV material (ntsc)
> >
> > General
> > Complete name    : exemple.avi
> > Format   : AVI
> > Format/Info   

Re: [Cin] actually, added few more formats to theme.C

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 12 November 2020 21:41:47 Terje J. Hanssen via Cin 
написал(а):
> 
> Den 12.11.2020 12:00, skrev Andrew Randrianasulu via Cin:
> > В сообщении от Thursday 12 November 2020 04:00:14 Terje J. Hanssen via Cin 
> > написал(а):
> >> Firstly, I'm not a programmer, but as I'm retired and hope to spend some
> >> time forward to learn Cin-GG to edit my hobby recorded and archived SD
> >> and HDV.
> >>
> >> In general, the most user friendly would be if the automatic selected
> >> Preset format fits correctly to each loaded standard video w/audio file
> >> format. For unknown formats, PAL vs NTSC should preferably be choosed
> >> based on the actual time zone (CGG manual page 416, above  Figure 13.1).
> >>
> >> *) User custom verification and selection of presets or video technical
> >> details, assume the user is skilled on the video format in use.
> >>
> >>
> >> Den 11.11.2020 18:54, skrev Andrew Randrianasulu via Cin:
> >>> В сообщении от Wednesday 11 November 2020 20:12:44 Terje J. Hanssen via 
> >>> Cin написал(а):
> >>>> I will just add that the HDV format consist of three versions:
> >>>> https://en.wikipedia.org/wiki/HDV#Specifications
> >>>>
> >>>> HDV 720p
> >>>> 720p/60, 720p/30, 720p/24, 720p/50, 720p/25
> >>> but may be those can be already selected, just not as preset with HDV in 
> >>> name?
> >> 720p/60 is the only 720p preset available.
> >> *) Each details can be custom selected, although not ideally?
> > Yes, I was reluctant to add ALL variations because they will make list 
> > longer.
> > But I can do this.
> 
> A sub-menu next for each of the three HDV groups seems to be even 
> better, though more complicated(?)

For me, I don't know how to make sub-menus yet :D

> 
> >> According to the Wikipedia HDV specifications:
> >>    720p: Pixel aspect ratio 1.00 (PAR),  Frame size in pixels 1280x720,
> >> Frame aspect ratio 16:9 (DAR),   MPEG2 Video compr. (profile & level:
> >> MP@H-14/HL)
> >> 1080i: Pixel aspect ratio 1.33 (PAR),  Frame size in pixels 1440x1080,
> >> Frame aspect ratio 16:9 (DAR),  MPEG2 Video compr. (profile & level:
> >> MP@H-14)
> >>
> >>   From the Cin Preset Canvas size I noticed the following proportions can
> >> be derived, in case they tell something .
> >>    720p: W Ratio/H Ratio=0.8889/0.6667=1.33,  Width/W
> >> Ratio=1280/0.8889=1440,  Height/H Ratio=720/0.6667=1080
> >> 1080i: W Ratio/H Ratio=1./1.=1.33,  Width/W
> >> Ratio=1920/1.=1440,  Height/H Ratio=1080/1.000=1080
> >>
> >>
> >>>> HDV 1080i
> >>>> 1080i/30 (29.97), 1080i/25
> >>>>
> >>>> HDV 1080p
> >>>> 1080p/30 (29.97), 1080p/24 (23.98), 1080p/25
> >>> Those seems  to be more tricky, because I still not sure how they should 
> >>> show up in Compositor and Viewer. With correct-for-display aspect ratio? 
> >>> But then how masks/titles will work?
> 
> I'm not sure about all other HD-video formats, but the HDV formats seems 
> to be supported HDTV formats (broadcast standards) and supported Blu-ray 
> video formats
> 1280x720 (HD-1) HD ready or Standard HD
> 1440x1080 (HD-2) and 1920x1080, (Full HD, FHD)
> 
> https://en.wikipedia.org/wiki/High-definition_television#Display_resolutions
> https://en.wikipedia.org/wiki/List_of_common_resolutions#Digital_TV_standards
> https://en.wikipedia.org/wiki/High-definition_video#Common_high-definition_video_modes
> https://en.wikipedia.org/wiki/Blu-ray#Video
> 
> >> In case you have not seen it, the replies to my related mail request on
> >> the old CinCVS mail list might have some more information:
> >> https://www.mail-archive.com/cinelerra@skolelinux.no/msg05573.html
> > Yes, I see
> >
> > https://www.mail-archive.com/cinelerra%40skolelinux.no/msg05582.html
> >
> > this one not very encouraging:
> >
> > ==
> > Note that Cinelerra does two tasks: render and display.
> >
> > To render, Cinelerra treats the 1440:1080 as square pixels. This is not
> > optimal if something you render has both horizontal and vertical extent, but
> > is driven by only one parameter, like the radius of the radial grandient, a
> > radial blur, or the 'feather' radius of the masks. Such things will turn 
> > into
> > ellipses because:
> >
> > To display, Cinelerra simply

Re: [Cin] UPD: Re: DNxHR presets

[Andrew Randrianasulu via Cin]

В сообщении от Thursday 12 November 2020 23:53:40 MatN via Cin написал(а):
> On Thu, 12 Nov 2020 21:41:20 +0100 (CET), MatN via Cin wrote:
> 
> >On Wed, 11 Nov 2020 23:47:17 +0100, Andrea paz via Cin wrote:
> >
> >>I think you need to copy Andrew's presets to ".../bin/ffmpeg/video"
> >>after compilation. At least that's what I do. If you want to do it
> >>before compiling then you have to copy the presets to
> >>".../ffmpeg/video", which is in the main directory, without entering
> >>"/bin". But I don't understand the code at all, sorry.
> >>In this way DNxHR.mov. are also displayed. To me only the 420 appears
> >>without other options. Since the 420 is not supported by DNxHR then
> >>the render fails. For Andrew it works fine.
> >
> >@Andrea,
> >
> >Ok, got it. The .mov files need to be in the cinelerra5.1/ffmpeg/video
> >directory, and the "make install" copies that ffmpeg directory to the bin
> >directory (a "make clean" removes that and some other subdirectories of bin).
> >
> >Now if in the render window I choose file format ffmpeg.mov, then open the
> >video options, I get the 7 extra options DnxHR options in the 'compression"
> >dropdown. I presume you get this far too?
> >Then if I select e.g. DNxHR_HQ, the Pixels dropdown has extra entries like
> >yuv422p . Do you get this?
> 
> I can render a file with DNxHR_HQ pixel yuv422p fine, but it expands
> enormously. The source Jellyfish .MP4 file was 35 MB, the .mov file 787 Mb.
> VLC's codec info on that file shows indeed dnxhr yuv422p .
> 
> So what is the advantage of these DNxHR formats?

According to this:
https://www.mainconcept.com/fileadmin/user_upload/datasheets/DNxHD-DNxHR_SDK_DATASHEET.pdf

The MainConcept VC-3 SDK Packages for Avid DNxHD and Avid DNxHR are 
software-only solutions which enable application developers to integrate with 
production tools like Avid Media Composer and Avid Interplay storage solutions
or cameras which store media in either of these formats. Avid DNxHD and DNxHR 
are based on the SMPTE 2019-2006 (VC-3) specification.
-

so, basically standard codec  for exchange with Big Boys (AVID, etc)
Better to be put on fast storage.

Try to play it back/forward, framestep, fastforward, and randomly hit various 
places on relatively long timeline, notice if there any difference in 
responsiveness with h264.


> 
> MatN
> 
> 
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Friday 13 November 2020 07:05:19 вы написали:
> 
> Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
> > For cinelerra/defaultformats.h
> >
> > I de-capitalized "I" in presets, but I'm not sure about overall aesthetics 
> > of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 
> > 720p presets can be used outside of HDV material?)
> >
> > Terje, can you try to pull cinGG sources from git, apply my patch
> > (git apply PATCH from source tree) and build with "--with-single-user", so 
> > there will be no danger to your Cin isntallation and see if patch actually 
> > gives workable settings for your real footage?
> 
> Here I reach my limit :
> Though I've worked with civil engineering, I'm not familiar with 
> building, compiling and patching computer software :)
> Actually, almost five years ago, GG guided me step by step by email to 
> compile my first Cin5.0 on openSUSE 42.1.
> Since then I've just installed pre-build rpm packages, included the 
> current Cin-GG 5.1 on Leap 15.2.
> 
> So to do it now, I will need the detailed command procedure, step by 
> step again ;)

:}

there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh

I'll copy-paste part of it so you can copy/paste it into terminal (konsole, 
xterm ..) and execute as root (or use gui for isntalling all those packages, 
but I think it will be more time consuming):

zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \
freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \
libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \
bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \
openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \
libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \
ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \
libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \
yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \
gtk2-devel libusb-1_0-devel libpulse-devel libtool python

after this you should have 'git' command available.

as user:

create some dir, I usually create src/ in my home and then add 
software-specific dirs there.

You can use your GUI filemanager for this task or in terminal:

$ mkdir src
$ cd src
$ mkdir cin5
$ cd cin5

"$" indicates user-level shell, as opposed to root shell ending with "#"

 now git clone  git://git.cinelerra-gg.org/goodguy/cinelerra.git

you can add --depth 1 if you want only last commit and not whole tree with 
history. But I hope you have anough hdd space.

my build takes 2692M without OpenCV plugins.

when this step finished you must have cinelerra tree cloned. Go to 
cinelerra-5.1 (should be alongside CineRmt, you can use 'ls' to look around - 
it prints list of files  and directories) using 'cd' comman (cd stands for 
'change directory')

apply my patch:
git apply DEFAULT_FORMATS-2.patch if you saved it under this name. This 
psecific form looks for file in current dir, so place it there, or use 

git apply /path/to/some/place/DEFAULT_FORMATS-2.patch

hopefully this step shouldn't give you errors.

and from there execute ./autogen.sh

when this finishes correctly run

./configure --with-single-user

autogen script calls various autotools to generate configure script, you can 
look (with mcedit/nano/kate) into each script but configure will be rather 
large. I hope there will be no need  to mess with them.

now you should see summary of things configure found on your system. If it 
looks ok then just type make and look at all those lines scrolling past :} (you 
may use this trick with tee and log file redirection, but I just watch lines 
scroll)

if everything finishes without error - then run make install (as user) . It 
will give you 'bin' directory inside source tree to run ./cin from

> 
> >
> >  From dialogs it seems Aspect Ratio at the bottom of format window IS 
> > Screen/Display aspect ration, and W/H ratio is about non-square pixels.
> >
> > But I wonder how it supposed to work for rendering back into HDV?
> > If your pipeline set to 1440x1080, and you encode just with special flag 
> > set - all movements and graphics and text and masked effects you added must 
> > be somewhat scaled horizontally up and down? (because if Compositor shows 
> > 1920x1080 image, and you draw nice square with Sketcher there - how those 
> > pixels will be drawn on top of project size sized frame? Or you must have 
> > special overlay track set to 1920x1080 where you draw, and then just let 
> > Cin  mix two?)
> >
> > NOTE: I don't think this will adds autodetect-on-load but at least having 
> > correct profiles somewhere might be 0.2 step in this direction.
> 
> However, via a previous mail thread with url to a small hdv video clip, 
> this file can be downloaded and tested:
> CinCV TNG] Setting up a Project
> 

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Friday 13 November 2020 22:39:24 Terje J. Hanssen написал(а):
[skip]
> >
> > Andrew,
> >
> > There was something above that put a 'c' and 'cr' at the end, and 
> > exited to the prompt as shown above.
> > I had to install several packages Solution 1 from the open build 
> > service obs://...
> > before the build script ran through and installed 2321 packages.
> >
> > Now I'm here :
> >
> > terje@alfa:~/src/cin5>
> > terje@alfa:~/src/cin5> du -sh
> > 546M    .
> > terje@alfa:~/src/cin5>
> >
> > Could you add the command "to pull cinGG sources from git, apply my 
> > patch"
> >
> > (git apply PATCH from source tree) and build with 
> > "--with-single-user", so there will be no danger to your Cin 
> > isntallation and see if patch actually gives workable settings for 
> > your real footage?

in theory if you already have 546M of it - sources must be ok 

I usually attach patch to email, so you can check now your email client/web 
interface shows attachments, and download it from there...

Yes, I can't see it via web interface to mail archive.

I put some patches in web folder:

https://cloud.mail.ru/public/2ceA/4exRtrswu

double-click on patch name and then hit Скачать





> >
> >
> > =
> >
> > Terje J. H
> >
> 
> including download the patch
> 
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu

now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get 
lowercase "p/i" in presets.

You can undo patch with 'cat patch.patch | patch -R -p1'

It will be useful if you also test interlace_aspect_autodetect-2.patch
I hope it will work for mixed-type files in same project.

PS: I solved my little black screen problem - just missed dri3_disable patch 
for this build :}

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 14 November 2020 01:14:24 вы написали:
> 
> Den 13.11.2020 21:02, skrev Andrew Randrianasulu:
> > В сообщении от Friday 13 November 2020 22:39:24 Terje J. Hanssen написал(а):
> > [skip]
> >>> Now I'm here :
> >>>
> >>> terje@alfa:~/src/cin5>
> >>> terje@alfa:~/src/cin5> du -sh
> >>> 546M    .
> >>> terje@alfa:~/src/cin5>
> >>>
> >>> Could you add the command "to pull cinGG sources from git, apply my
> >>> patch"
> >>>
> >>> (git apply PATCH from source tree) and build with
> >>> "--with-single-user", so there will be no danger to your Cin
> >>> isntallation and see if patch actually gives workable settings for
> >>> your real footage?
> > in theory if you already have 546M of it - sources must be ok 
> >
> > I usually attach patch to email, so you can check now your email client/web 
> > interface shows attachments, and download it from there...
> >
> > Yes, I can't see it via web interface to mail archive.
> >
> > I put some patches in web folder:
> >
> > https://cloud.mail.ru/public/2ceA/4exRtrswu
> >
> > double-click on patch name and then hit Скачать
> >
> >
> >
> >
> 
> Yup, thank you - that worked :)
> 
> Tested Cin-GG and loaded the hdv m2t file;
> 
> ./cin
> Cinelerra Infinity - built: Nov 13 2020 22:08:49
> git://git.cinelerra-gg.org/goodguy/cinelerra.git
> (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
> 2007-2020 mods for Cinelerra-GG 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.
> 
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> [W][17893.443208][remote-node.c:632 client_node_port_use_buffers()] 
> Failed to mlock memory 0x7fd337f04000 32832: This is not a problem but 
> for best performance, consider increasing RLIMIT_MEMLOCK
> FFMPEG::open_decoder: some stream times estimated: 
> /data/video/Diverse/20081103140154.m2t
> Session time: 0:19:47
> Cpu time: user: 0:00:07.198 sys: 0:00:02.003
> ===
> 
> Attach two compressed screen shots:
> 
> hdv-m2t_Cin-GG_4x3.jpg
> shows the Format default preset and the new selected 1080i/25 preset
> (would next suggest to change the upper "P"s to lower case "p")
> Not sure about the W.Ratio=1 and H.Ratio=1, as the Cin Viewer still 
> playback the hdv video image with Aspect 4x3 ?

Not sure too, those fields tend to change their value wildly as I select 
various presets.

Did you load video with default 'create new resources only' strategy, or with 
'replace current project'?

'Replace' indeed not autodetect Display Aspect Ratio.
Try with 'Create reources only' and then drag your video into tracks on 
timeline... (after you set Project preset correctly). Or just select correct 
profile in Format after loading - it should  set things correctly.

I tried rendering it into h264 with correct profile - and output file comes as

   Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, 
smpte170m/unknown/unknown), 1440x1080 [SAR 4:3 DAR 16:9], 5239 kb/s, 25 fps, 25 
tbr, 12800 tbn, 50 tbc (default)

plays as 
VO: [vdpau] 1440x1080 => 1920x1080 Planar YV12  [fs]


Also, when I tried to set project preferences to something else (like, preset 
Internet - 320x240x15 fps) and load your file - there was black screen in 
Compositor with Video output driver X11-OpenGL. It showed some image with 
X11/X11-xv ..

> 
> hdv-m2t_VLC_16x9.jpg
> Playback the same hdv m2t file in VLC with its Codec info.
> Playback the video with correct aspect 16x9
> =
> 
> Terje J. H
> 
> 
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Partial patch for detecting SAR/DAR and interlace.

[Andrew Randrianasulu via Cin]

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.33
display_aspect_ratio, 1.78
interlace: 2

for HDV 1080i file and 

interlace: 1
sample_aspect_ratio, 1.00
display_aspect_ratio, 1.78

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(, ,
+  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);

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(, ,
+  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;
+	

[Cin] Even more updated interlace/aspect ratio autodetection patch

[Andrew Randrianasulu via Cin]

It basically forces project to take first asset's interlace mode, but of course 
you still can change settings manually




diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C
index 97b6698a..9eabe9bd 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(, ,
+  par->width  * sar.num,
+  par->height * sar.den,
+  1024*1024);
+  printf("display_aspect_ratio, %f \n", av_q2d(dar));
+  return av_q2d(dar);
+  }
+return ffvideo[stream]->aspect_ratio;
 }
 
 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..f8567adf 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -342,6 +342,9 @@ 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);
+   printf("ff_aspect_ratio, %f \n", 
asset->aspect_ratio);
+   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);
diff --git a/cinelerra-5.1/cinelerra/mwindow.C 
b/cinelerra-5.1/cinelerra/mwindow.C
index f245018a..a7c0efab 100644
--- a/cinelerra-5.1/cinelerra/mwindow.C
+++ b/cinelerra-5.1/cinelerra/mwindow.C
@@ -4493,11 +4493,14 @@ static inline int gcd(int m, int n)
 int MWindow::create_aspect_ratio(float , float , int width, int height)
 {
w = 1;  h = 1;
+   double ar;
+   
if(!width || !height) return 1;
if( width == 720 && (height == 480 || height == 576) ) {
w = 4;  h = 3;  return 0; // for NTSC and PAL
}
-   double ar = (double)width / height;
+   
+   ar = (double)width / height;
 // square-ish pixels
if( EQUIV(ar, 1.) ) return 0;
if( EQUIV(ar, 1.) ) { w = 4;  h = 3;  return 0; }
@@ -4505,6 +4508,7 @@ int MWindow::create_aspect_ratio(float , float , int 
width, int height)
if( EQUIV(ar, 2.) ) { w = 19; h = 9;  return 0; }
if( EQUIV(ar, 2.) ) { w = 20; h = 9;  return 0; }
if( EQUIV(ar, 2.) ) { w = 21; h = 9;  return 0; }
+
int ww = width, hh = height;
// numerator, denominator must be under mx
int mx = 255, n = gcd(ww, hh);
@@ -5048,12 +5052,25 @@ int MWindow::select_asset(Asset *asset, int vstream, 
int astream, int delete_tra
session->output_w = width;
session->output_h = height;
session->frame_rate = framerate;
+   session->interlace_mode = asset->interlace_mode;
// not, 

[Cin] slightly better interlace/aspect ratio autodetect patch

[Andrew Randrianasulu via Cin]

This one sets things correctly (?) for Terje's HDV file, but interlace 
auto-setting still not setting _project's_ interlace  mode

It still prints a lot of debug lines


diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C
index 97b6698a..9eabe9bd 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(, ,
+  par->width  * sar.num,
+  par->height * sar.den,
+  1024*1024);
+  printf("display_aspect_ratio, %f \n", av_q2d(dar));
+  return av_q2d(dar);
+  }
+return ffvideo[stream]->aspect_ratio;
 }
 
 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..f8567adf 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ -342,6 +342,9 @@ 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);
+   printf("ff_aspect_ratio, %f \n", 
asset->aspect_ratio);
+   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);
diff --git a/cinelerra-5.1/cinelerra/mwindow.C 
b/cinelerra-5.1/cinelerra/mwindow.C
index f245018a..cac84d10 100644
--- a/cinelerra-5.1/cinelerra/mwindow.C
+++ b/cinelerra-5.1/cinelerra/mwindow.C
@@ -4493,11 +4493,14 @@ static inline int gcd(int m, int n)
 int MWindow::create_aspect_ratio(float , float , int width, int height)
 {
w = 1;  h = 1;
+   double ar;
+   
if(!width || !height) return 1;
if( width == 720 && (height == 480 || height == 576) ) {
w = 4;  h = 3;  return 0; // for NTSC and PAL
}
-   double ar = (double)width / height;
+   
+   ar = (double)width / height;
 // square-ish pixels
if( EQUIV(ar, 1.) ) return 0;
if( EQUIV(ar, 1.) ) { w = 4;  h = 3;  return 0; }
@@ -4505,6 +4508,7 @@ int MWindow::create_aspect_ratio(float , float , int 
width, int height)
if( EQUIV(ar, 2.) ) { w = 19; h = 9;  return 0; }
if( EQUIV(ar, 2.) ) { w = 20; h = 9;  return 0; }
if( EQUIV(ar, 2.) ) { w = 21; h = 9;  return 0; }
+
int ww = width, hh = height;
// numerator, denominator must be under mx
int mx = 255, n = gcd(ww, hh);
@@ -5052,8 +5056,20 @@ int MWindow::select_asset(Asset *asset, int vstream, int 
astream, int delete_tra
asset->width = session->output_w;
asset->height = session->output_h;
asset->frame_rate = session->frame_rate;
+   

[Cin] Interlace/aspect autodetect patch (incomplete)

[Andrew Randrianasulu via Cin]

So, I found way to get interlace info out of codec, but sadly only at 
FFVideoStream::load() time (so, it still just print info to terminal, and do 
not use it in asset/project)

Unfortunately at FileFFMPEG::open_file time this functon still not called yet.

=

diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C
index 97b6698a..55e94e4b 100644
--- a/cinelerra-5.1/cinelerra/ffmpeg.C
+++ b/cinelerra-5.1/cinelerra/ffmpeg.C
@@ -1226,6 +1226,17 @@ int FFVideoStream::load(VFrame *vframe, int64_t pos)
while( ret>=0 && !flushed && curr_pos<=pos && --i>=0 ) {
ret = read_frame(frame);
if( ret > 0 ) {
+   //printf("codec interlace: %i 
\n",frame->interlaced_frame);
+   //printf("codec tff: %i \n",frame->top_field_first);
+
+   if (!frame->interlaced_frame)
+   ffmpeg->interlace_from_codec = 
AV_FIELD_PROGRESSIVE;
+   if ((frame->interlaced_frame) && 
(frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_TT;
+   if ((frame->interlaced_frame) && 
(!frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_BB;
+   printf("Interlace mode from codec: %i\n", 
ffmpeg->interlace_from_codec);
+
if( frame->key_frame && seeking < 0 ) {
int use_cache = ffmpeg->get_use_cache();
if( use_cache < 0 ) {
@@ -2411,6 +2422,8 @@ int FFMPEG::info(char *text, int len)
AVPixelFormat pix_fmt = (AVPixelFormat)st->codecpar->format;
const char *pfn = av_get_pix_fmt_name(pix_fmt);
report(" pix %s\n", pfn ? pfn : unkn);
+   int interlace = st->codecpar->field_order;
+   report("  interlace (container level): %i\n", interlace ? 
interlace : -1);
enum AVColorSpace space = st->codecpar->color_space;
const char *nm = av_color_space_name(space);
report("color space:%s", nm ? nm : unkn);
@@ -3468,7 +3481,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(, ,
+  par->width  * sar.num,
+  par->height * sar.den,
+  1024*1024);
+  printf("display_aspect_ratio, %f \n", av_q2d(dar));
+  return av_q2d(dar);
+  }
+return ffvideo[stream]->aspect_ratio;
 }
 
 const char* FFMPEG::ff_video_codec(int stream)
@@ -3509,6 +3537,31 @@ 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)
+{
+// https://ffmpeg.org/doxygen/trunk/structAVCodecParserContext.html
+/* reads from demuxer because codec frame not ready */
+   int interlace = ffvideo[stream]->st->codecpar->field_order;
+   printf("interlace from demux: %i\n", interlace);
+
+   switch (interlace)
+   {
+   case AV_FIELD_TT:
+   case AV_FIELD_TB:
+   return ILACE_MODE_TOP_FIRST;
+   case AV_FIELD_BB:
+   case AV_FIELD_BT:
+   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..53efca66 100644
--- a/cinelerra-5.1/cinelerra/ffmpeg.h
+++ b/cinelerra-5.1/cinelerra/ffmpeg.h
@@ -434,6 +434,7 @@ public:
 
int decoding, encoding;
int has_audio, has_video;
+   int interlace_from_codec;
 
FFMPEG(FileBase *file_base=0);
~FFMPEG();
@@ -463,6 +464,7 @@ public:
float ff_aspect_ratio(int stream);
int ff_color_range(int stream);
int ff_color_space(int stream);
+   int ff_interlace(int stream);
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..f30e1b8a 100644
--- a/cinelerra-5.1/cinelerra/fileffmpeg.C
+++ b/cinelerra-5.1/cinelerra/fileffmpeg.C
@@ 

[Cin] upd: Interlace/aspect autodetect patch (incomplete)

[Andrew Randrianasulu via Cin]

Moved this functionality to its own function, still not sure how to call it ... 
at fileffmpeg::open time

https://cloud.mail.ru/public/4x2q/4pmnbbhCw



diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C
index 97b6698a..42b91212 100644
--- a/cinelerra-5.1/cinelerra/ffmpeg.C
+++ b/cinelerra-5.1/cinelerra/ffmpeg.C
@@ -1213,6 +1213,37 @@ int FFVideoStream::decode_frame(AVFrame *frame)
return 1;
 }
 
+int FFVideoStream::probe(int64_t pos)
+{
+   int ret = video_seek(pos);
+   if( ret < 0 ) return -1;
+   if( !frame && !(frame=av_frame_alloc()) ) {
+   fprintf(stderr, "FFVideoStream::probe: av_frame_alloc 
failed\n");
+   return -1;
+   }
+
+   ret = read_frame(frame);
+   if( ret > 0 ) {
+   //printf("codec interlace: %i 
\n",frame->interlaced_frame);
+   //printf("codec tff: %i \n",frame->top_field_first);
+
+   if (!frame->interlaced_frame)
+   ffmpeg->interlace_from_codec = 
AV_FIELD_PROGRESSIVE;
+   if ((frame->interlaced_frame) && 
(frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_TT;
+   if ((frame->interlaced_frame) && 
(!frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_BB;
+   printf("Interlace mode from codec: %i\n", 
ffmpeg->interlace_from_codec);
+
+   }
+
+   if( frame->format == AV_PIX_FMT_NONE || frame->width <= 0 || 
frame->height <= 0 )
+   ret = -1;
+
+   ret = ret > 0 ? 1 : ret < 0 ? -1 : 0;
+   return ret;
+}
+
 int FFVideoStream::load(VFrame *vframe, int64_t pos)
 {
int ret = video_seek(pos);
@@ -1221,6 +1252,9 @@ int FFVideoStream::load(VFrame *vframe, int64_t pos)
fprintf(stderr, "FFVideoStream::load: av_frame_alloc failed\n");
return -1;
}
+   
+   probe(pos); 
+
int i = MAX_RETRY + pos - curr_pos;
int64_t cache_start = 0;
while( ret>=0 && !flushed && curr_pos<=pos && --i>=0 ) {
@@ -1391,6 +1425,7 @@ int FFVideoStream::encode(VFrame *vframe)
 
 int FFVideoStream::drain()
 {
+
return 0;
 }
 
@@ -2411,6 +2446,8 @@ int FFMPEG::info(char *text, int len)
AVPixelFormat pix_fmt = (AVPixelFormat)st->codecpar->format;
const char *pfn = av_get_pix_fmt_name(pix_fmt);
report(" pix %s\n", pfn ? pfn : unkn);
+   int interlace = st->codecpar->field_order;
+   report("  interlace (container level): %i\n", interlace ? 
interlace : -1);
enum AVColorSpace space = st->codecpar->color_space;
const char *nm = av_color_space_name(space);
report("color space:%s", nm ? nm : unkn);
@@ -3468,7 +3505,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(, ,
+  par->width  * sar.num,
+  par->height * sar.den,
+  1024*1024);
+  printf("display_aspect_ratio, %f \n", av_q2d(dar));
+  return av_q2d(dar);
+  }
+return ffvideo[stream]->aspect_ratio;
 }
 
 const char* FFMPEG::ff_video_codec(int stream)
@@ -3509,6 +3561,31 @@ 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)
+{
+// https://ffmpeg.org/doxygen/trunk/structAVCodecParserContext.html
+/* reads from demuxer because codec frame not ready */
+   int interlace = ffvideo[stream]->st->codecpar->field_order;
+   printf("interlace from demux: %i\n", interlace);
+
+   switch (interlace)
+   {
+   case AV_FIELD_TT:
+   case AV_FIELD_TB:
+   return ILACE_MODE_TOP_FIRST;
+   case AV_FIELD_BB:
+   case AV_FIELD_BT:
+   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..a34a9d81 100644
--- a/cinelerra-5.1/cinelerra/ffmpeg.h
+++ b/cinelerra-5.1/cinelerra/ffmpeg.h
@@ 

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen написал(а):
> 
> Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
> > В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen 
> > написал(а):
> >> Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
> >>> I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
> >>>
> >>> now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should 
> >>> get lowercase "p/i" in presets.
> >>>
> >>> You can undo patch with 'cat patch.patch | patch -R -p1'
> >>>
> >>> It will be useful if you also test interlace_aspect_autodetect-2.patch
> >>> I hope it will work for mixed-type files in same project.
> >>>
> >>> PS: I solved my little black screen problem - just missed dri3_disable 
> >>> patch for this build :}
> >>>
> >> I saved the updated and new patches in
> >>
> >> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch
> >> DEFAULT_FORMATS-2.patch
> >> interlace_aspect_autodetect-2.patch
> >>
> >> and then tried to apply the first updated patch:
> >>
> >> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply
> >> DEFAULT_FORMATS-2.patch
> >> error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39
> >> error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
> >>
> >>
> >> Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first?
> > Sadly, yes.
> >
> 
> Sorry, I try to understand what to do with the mentioned undo patch command
> 
> cat patch.patch | patch -R -p1
> 
> What I have saved are
> 
> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT*
> DEFAULT_FORMATS-2.patch
> DEFAULT_FORMATS-2.patch_old
> 
> where the first one listed is the new patch, the latter is the renamed, 
> already installed version
> (I did rename it to keep it without overwriting of the new patch with 
> the same name and version)
> 
> Before doing anything wrong, what should the undo command line be?
> Possibly I have to rename the new patch first, 
> DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch
> before running the undo command?

I think exact patch name is not important, as long as you remember old vs new.

In my case I reverted patch like this

guest@slax:/dev/shm/cinelerra$ cat 
~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1
patching file cinelerra-5.1/cinelerra/defaultformats.h
guest@slax:/dev/shm/cinelerra$ 

when I did it wrong (from wrong point in tree) it complained like this:

 guest@slax:/dev/shm/cinelerra$ cat 
~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|diff --git a/cinelerra-5.1/cinelerra/defaultformats.h 
b/cinelerra-5.1/cinelerra/defaultformats.h
|index 61bd2165..b963decd 100644
|--- a/cinelerra-5.1/cinelerra/defaultformats.h
|+++ b/cinelerra-5.1/cinelerra/defaultformats.h
--
File to patch: ^C

I ctrl-c (interrupted) it.

with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' but 
this will wipe out anything from your working tree (not in git index), so use 
with extreme  caution  

   https://git-scm.com/docs/git-clean/2.23.0
  

> 
> Terje J. H
> 
> 
> 
> 
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Getting field_order in dv demuxer early?

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 15 November 2020 00:07:27 Andrea paz via Cin написал(а):
> Stupid idea from an ignorant person (definitely wrong):
> It seems to me that GG has implemented media autorotation and timecode
> reading them in the metadata and then rotating or aligning them. Maybe
> also the aspect ratio or other can be read/put in the metadata?
> Excuse me for talking about things I don't know...

In my case I probably don't know how to fully initialize those structures, so 
only this partial form of extracting field_order from container/stream works.

(I tried few other forms of accesing frame data, but they resulted in Cin 
segfaulting)

dv codec (decoder) itself sets 

frame.f->interlaced_frame 
and  
frame.f->top_field_first 

But by time this data become avilable CinGG already probed streams and set 
default field order 'UNKNOW' (I think this is safe default?)

I'm not sure how to force re-probing or hold filling those field until all data 
from decoder will be ready.

I found libopenshot, it probably shows how I can improve setting our flags from 
libavcodec's ones (I missed two cases), but their internal organization a bit 
different from Cin 

http://openshot.org/files/libopenshot/FFmpegReader_8cpp_source.html

 // Get scan type and order from codec context/params
  730 if (!check_interlace) {
  731 check_interlace = true;
  732 AVFieldOrder field_order = 
AV_GET_CODEC_ATTRIBUTES(pStream, pCodecCtx)->field_order;
  733 switch(field_order) {
  734 case AV_FIELD_PROGRESSIVE:
  735 info.interlaced_frame = false;
  736 break;
  737 case AV_FIELD_TT:
  738 case AV_FIELD_TB:
  739 info.interlaced_frame = true;
  740 info.top_field_first = true;
  741 break;
  742 case AV_FIELD_BT:
  743 case AV_FIELD_BB:
  744 info.interlaced_frame = true;
  745 info.top_field_first = false;
  746 break;
  747 case AV_FIELD_UNKNOWN:
  748 // Check again later?
  749 check_interlace = false;
  750 break;
  751 }


In my patch I omitted AV_FIELD_BT / AV_FIELD_TB (those exist because apparently 
fields can be coded and displayed in different order!)

Code in ffprobe was:

static int show_stream(WriterContext *w, AVFormatContext *fmt_ctx, int 
stream_idx, InputStream *ist, int in_program)
{
AVStream *stream = ist->st;
AVCodecParameters *par;
AVCodecContext *dec_ctx;
char val_str[128];
const char *s;
AVRational sar, dar;
AVBPrint pbuf;
const AVCodecDescriptor *cd;
int ret = 0;
const char *profile = NULL;
par = stream->codecpar;

[skip a lot]

if (par->field_order == AV_FIELD_PROGRESSIVE)
print_str("field_order", "progressive");
else if (par->field_order == AV_FIELD_TT)
print_str("field_order", "tt");
else if (par->field_order == AV_FIELD_BB)
print_str("field_order", "bb");
else if (par->field_order == AV_FIELD_TB)
print_str("field_order", "tb");
else if (par->field_order == AV_FIELD_BT)
print_str("field_order", "bt");
else
print_str_opt("field_order", "unknown");

BUT there was another isntance of field reporting:

static void show_frame(WriterContext *w, AVFrame *frame, AVStream *stream,
   AVFormatContext *fmt_ctx)
{
AVBPrint pbuf;
char val_str[128];
const char *s;
int i;

[skip]

   case AVMEDIA_TYPE_VIDEO:
print_int("width",  frame->width);
print_int("height", frame->height);
s = av_get_pix_fmt_name(frame->format);
if (s) print_str("pix_fmt", s);
else   print_str_opt("pix_fmt", "unknown");
sar = av_guess_sample_aspect_ratio(fmt_ctx, stream, frame);
if (sar.num) {
print_q("sample_aspect_ratio", sar, ':');
} else {
print_str_opt("sample_aspect_ratio", "N/A");
}
print_fmt("pict_type",  "%c", 
av_get_picture_type_char(frame->pict_type));
print_int("coded_picture_number",   frame->coded_picture_number);
print_int("display_picture_number", frame->display_picture_number);
print_int("interlaced_frame",   frame->interlaced_frame);
print_int("top_field_first",frame->top_field_first);
print_int("repeat_pict",frame->repeat_pict);

BUT I currently have no  idea  how to say Cin to not fill interlacing type 
after stream probe says 'unknown' and wait until 

[Cin] Getting field_order in dv demuxer early?

[Andrew Randrianasulu via Cin]

Hello, all!

I was trying to get field order autodetection working in CinelerraGG (our 
developer sadly died, so I can't ask him anymore ...)

I get field_order like this:

int FFMPEG::ff_interlace(int stream)
{
/* reads from demuxer because codec frame not ready */
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;
}

}

Unfortunately, this only work for mpegts streams and not for, say, dv.

I tried to add some code in libavformat/dv.c, and while it sort-of working, it 
apparently doesn't work early enough (at stream probe time?)

in cinelerra/cinelerra-5.1/thirdparty/ffmpeg-4.3/libavformat/dv.c 

in function dv_extract_video_info() I added those lines (logic might be wrong, 
but I can fix it later, I used libavcodec/dvdec.c as example):


if (c->sys->height == 720) {
par->field_order = AV_FIELD_PROGRESSIVE;}
else if (c->sys->height == 1080) {
int ilaced = 1;
int tff  = (vsc_pack[3] & 0x40) == 0x40;
par->field_order = tff ? AV_FIELD_TT : 0; }
else {
int ilaced = (vsc_pack[3] & 0x10) == 0x10;
int tff  = !(vsc_pack[3] & 0x40) == 0x40;
par->field_order = tff ? 0 : AV_FIELD_BB;
}
//printf("Field order: %i \n", par->field_order);


It prints 'field order: 3" for usual pal DV example, but ffprobe (from where I 
get my logic for extracting field_order) still says:

/dev/shm/cinelerra/cinelerra-5.1/thirdparty/ffmpeg-4.3/ffprobe -show_streams 
/dev/shm/qt_dv_pal_test.mov
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Field order: 3
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/dev/shm/qt_dv_pal_test.mov':
  Metadata:
creation_time   : 2002-10-04T18:46:28.00Z
  Duration: 00:00:04.45, start: 0.00, bitrate: 57948 kb/s
Stream #0:0(eng): Video: dvvideo (dvcp / 0x70637664), yuv420p, 720x576 [SAR 
16:15 DAR 4:3], 28800 kb/s, 25 fps, 25 tbr, 600 tbn, 25 tbc (default)
Metadata:
  creation_time   : 2002-10-04T18:46:28.00Z
  handler_name: Apple Video Media Handler
  encoder : DV - PAL
Stream #0:1(eng): Audio: pcm_s16le (dvca / 0x61637664), 48000 Hz, 2 
channels, s16, 1536 kb/s (default)
Metadata:
  creation_time   : 2002-10-04T18:46:28.00Z
  handler_name: Apple Sound Media Handler
[STREAM]
index=0
codec_name=dvvideo
codec_long_name=DV (Digital Video)
profile=unknown
codec_type=video
codec_time_base=1/25
codec_tag_string=dvcp
codec_tag=0x70637664
width=720
height=576
coded_width=720
coded_height=576
closed_captions=0
has_b_frames=0
sample_aspect_ratio=16:15
display_aspect_ratio=4:3
pix_fmt=yuv420p
level=-99
color_range=unknown
color_space=unknown
color_transfer=unknown
color_primaries=unknown
chroma_location=topleft
field_order=unknown
timecode=N/A

[a lot more skiped]

I tried to add same logic into  dv_read_header(), but dv_extract_pack(frame, 
dv_video_control); wants 'frame' and I have no idea from where to plug it.

Idea about putting this in header reading code come from 
libavformat/yuv4mpegdec.c

Any ideas?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
> 
> Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
> >
> > I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
> >
> > now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should 
> > get lowercase "p/i" in presets.
> >
> > You can undo patch with 'cat patch.patch | patch -R -p1'
> >
> > It will be useful if you also test interlace_aspect_autodetect-2.patch
> > I hope it will work for mixed-type files in same project.
> >
> > PS: I solved my little black screen problem - just missed dri3_disable 
> > patch for this build :}
> >
> 
> I saved the updated and new patches in
> 
> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch
> DEFAULT_FORMATS-2.patch
> interlace_aspect_autodetect-2.patch
> 
> and then tried to apply the first updated patch:
> 
> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply 
> DEFAULT_FORMATS-2.patch
> error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39
> error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
> 
> 
> Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first?

Sadly, yes.

> 
> --
> 
> Terje J. H
> 
> 
> 
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] HDV formats patch

[Andrew Randrianasulu via Cin]

В сообщении от Sunday 15 November 2020 02:53:28 Terje J. Hanssen написал(а):
> 
> Den 14.11.2020 22:56, skrev Andrew Randrianasulu:
> > В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen 
> > написал(а):
> >> Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
> >>> В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen 
> >>> написал(а):
>  Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
> > I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
> >
> > now if you apply DEFAULT_FORMATS-2.patch to clean source tree you 
> > should get lowercase "p/i" in presets.
> >
> > You can undo patch with 'cat patch.patch | patch -R -p1'
> >
> > It will be useful if you also test interlace_aspect_autodetect-2.patch
> > I hope it will work for mixed-type files in same project.
> >
> > PS: I solved my little black screen problem - just missed dri3_disable 
> > patch for this build :}
> >
>  I saved the updated and new patches in
> 
>  terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch
>  DEFAULT_FORMATS-2.patch
>  interlace_aspect_autodetect-2.patch
> 
>  and then tried to apply the first updated patch:
> 
>  terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply
>  DEFAULT_FORMATS-2.patch
>  error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39
>  error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
> 
> 
>  Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first?
> >>> Sadly, yes.
> >>>
> >> Sorry, I try to understand what to do with the mentioned undo patch command
> >>
> >> cat patch.patch | patch -R -p1
> >>
> >> What I have saved are
> >>
> >> terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT*
> >> DEFAULT_FORMATS-2.patch
> >> DEFAULT_FORMATS-2.patch_old
> >>
> >> where the first one listed is the new patch, the latter is the renamed,
> >> already installed version
> >> (I did rename it to keep it without overwriting of the new patch with
> >> the same name and version)
> >>
> >> Before doing anything wrong, what should the undo command line be?
> >> Possibly I have to rename the new patch first,
> >> DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch
> >> before running the undo command?
> > I think exact patch name is not important, as long as you remember old vs 
> > new.
> >
> > In my case I reverted patch like this
> >
> > guest@slax:/dev/shm/cinelerra$ cat 
> > ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1
> > patching file cinelerra-5.1/cinelerra/defaultformats.h
> > guest@slax:/dev/shm/cinelerra$
> >
> > when I did it wrong (from wrong point in tree) it complained like this:
> >
> >   guest@slax:/dev/shm/cinelerra$ cat 
> > ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0
> > can't find file to patch at input line 5
> > Perhaps you used the wrong -p or --strip option?
> > The text leading up to this was:
> > --
> > |diff --git a/cinelerra-5.1/cinelerra/defaultformats.h 
> > b/cinelerra-5.1/cinelerra/defaultformats.h
> > |index 61bd2165..b963decd 100644
> > |--- a/cinelerra-5.1/cinelerra/defaultformats.h
> > |+++ b/cinelerra-5.1/cinelerra/defaultformats.h
> > --
> > File to patch: ^C
> >
> > I ctrl-c (interrupted) it.
> >
> > with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' 
> > but this will wipe out anything from your working tree (not in git index), 
> > so use with extreme  caution 
> >
> > https://git-scm.com/docs/git-clean/2.23.0
> >
> 
> First I got the same complaint as above. Possibly I had moved the 
> patches on level down to /src/cin5/cinelerra/cinelerra-5.1 after patching.
> Moved it up one level again and tried to undo the old and apply the new.
> 
> This time undo and apply seemed to work, and configured again (... 
> should I configure ?).

I think 'git apply -v' is more useful - it will tell you if it skipped patch 
(did this for me few times)

I also think you forgot 'make'. Depend on specific files you changed  'make' 
may rebuild them, or I was forced to do this in cinelerra:

guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ setarch i686 make clean 
&& make -j 5  

'setarch i686' because I build x86 program on system running x86_64 kernel, you 
can omit this.

You can run cin from there. I found it slightly easier for console-based 
editing to just 'mcedit file', rerun this 'make clean /make' route, and launch

../bin/cin

Of course I think multi-document editor (like kate from KDE) is better because 
you can have few files open at once, but it seems I slip back to old DOS habits 
often 

> 
> But after starting ./cin again, the Format Preset menu did still show 
> uppercase "P".
> 
> Could you possibly have a look in my attached file, 
> Patching_term_output, in case there is something wrong?
> 
> The initial 

[Cin] Interlace/aspect autodetect patch, hopefully this time working.

[Andrew Randrianasulu via Cin]

I tested it with wmv, mpeg, mov, mp4 files.

interlace_from_codec in asset info still doesn't work, but I'll leave  this for 
later



https://cloud.mail.ru/public/3PXB/4e5HRYTd8

=

diff --git a/cinelerra-5.1/cinelerra/ffmpeg.C b/cinelerra-5.1/cinelerra/ffmpeg.C
index 97b6698a..5165d25d 100644
--- a/cinelerra-5.1/cinelerra/ffmpeg.C
+++ b/cinelerra-5.1/cinelerra/ffmpeg.C
@@ -1213,6 +1213,40 @@ int FFVideoStream::decode_frame(AVFrame *frame)
return 1;
 }
 
+int FFVideoStream::probe(int64_t pos)
+{
+   int ret = video_seek(pos);
+   if( ret < 0 ) return -1;
+   if( !frame && !(frame=av_frame_alloc()) ) {
+   fprintf(stderr, "FFVideoStream::probe: av_frame_alloc 
failed\n");
+   return -1;
+   }
+   
+   if (ffmpeg->interlace_from_codec)
+   return 1;
+
+   ret = read_frame(frame);
+   if( ret > 0 ) {
+   //printf("codec interlace: %i 
\n",frame->interlaced_frame);
+   //printf("codec tff: %i \n",frame->top_field_first);
+
+   if (!frame->interlaced_frame)
+   ffmpeg->interlace_from_codec = 
AV_FIELD_PROGRESSIVE;
+   if ((frame->interlaced_frame) && 
(frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_TT;
+   if ((frame->interlaced_frame) && 
(!frame->top_field_first))
+   ffmpeg->interlace_from_codec = AV_FIELD_BB;
+   //printf("Interlace mode from codec: %i\n", 
ffmpeg->interlace_from_codec);
+
+   }
+
+   if( frame->format == AV_PIX_FMT_NONE || frame->width <= 0 || 
frame->height <= 0 )
+   ret = -1;
+
+   ret = ret > 0 ? 1 : ret < 0 ? -1 : 0;
+   return ret;
+}
+
 int FFVideoStream::load(VFrame *vframe, int64_t pos)
 {
int ret = video_seek(pos);
@@ -1221,6 +1255,8 @@ int FFVideoStream::load(VFrame *vframe, int64_t pos)
fprintf(stderr, "FFVideoStream::load: av_frame_alloc failed\n");
return -1;
}
+   
+
int i = MAX_RETRY + pos - curr_pos;
int64_t cache_start = 0;
while( ret>=0 && !flushed && curr_pos<=pos && --i>=0 ) {
@@ -1391,6 +1427,7 @@ int FFVideoStream::encode(VFrame *vframe)
 
 int FFVideoStream::drain()
 {
+
return 0;
 }
 
@@ -1776,6 +1813,7 @@ FFMPEG::FFMPEG(FileBase *file_base)
flow = 1;
decoding = encoding = 0;
has_audio = has_video = 0;
+   interlace_from_codec = 0;
opts = 0;
opt_duration = -1;
opt_video_filter = 0;
@@ -2411,6 +2449,10 @@ int FFMPEG::info(char *text, int len)
AVPixelFormat pix_fmt = (AVPixelFormat)st->codecpar->format;
const char *pfn = av_get_pix_fmt_name(pix_fmt);
report(" pix %s\n", pfn ? pfn : unkn);
+   int interlace = st->codecpar->field_order;
+   report("  interlace (container level): %i\n", interlace ? 
interlace : -1);
+   int interlace_codec = interlace_from_codec;
+   report("  interlace (codec level): %i\n", interlace_codec ? 
interlace_codec : -1);
enum AVColorSpace space = st->codecpar->color_space;
const char *nm = av_color_space_name(space);
report("color space:%s", nm ? nm : unkn);
@@ -3181,6 +3223,33 @@ int FFMPEG::audio_seek(int stream, int64_t pos)
return 0;
 }
 
+int FFMPEG::video_probe(int64_t pos)
+{
+   int vidx = vstrm_index[0].st_idx;
+   FFVideoStream *vid = ffvideo[vidx];
+   vid->probe(pos);
+   
+   int interlace1 = interlace_from_codec;
+   //printf("interlace from codec: %i\n", interlace1);
+
+   switch (interlace1)
+   {
+   case AV_FIELD_TT:
+   case AV_FIELD_TB:
+   return ILACE_MODE_TOP_FIRST;
+   case AV_FIELD_BB:
+   case AV_FIELD_BT:
+   return ILACE_MODE_BOTTOM_FIRST;
+   case AV_FIELD_PROGRESSIVE:
+   return ILACE_MODE_NOTINTERLACED;
+   default:
+   return ILACE_MODE_UNDETECTED;
+   }
+
+}
+
+
+
 int FFMPEG::video_seek(int stream, int64_t pos)
 {
int vidx = vstrm_index[stream].st_idx;
@@ -3468,7 +3537,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(, ,
+  par->width  * sar.num,
+  par->height * sar.den,
+  1024*1024);
+