- Cin - Cinelerra-GG Mailing Lists

Again on plugins in floating point (HDR)
by Andrea paz 22 Jan '24

22 Jan '24

I tried to make other changes to the plugins for Color Correction to be able to make it also see out-of-range (HDR) values and be able to change them. All of this involves floating point calculation. I tried changing the range of the following plugins: Alpha; Color3Way; ColorBalance; Gradient; Histogram Bezier e Overlay. If interested, I can report attempts to modify the code, but I got good results only with Color3Way. More in detail: Alpha: My modifications ruin the plugin. Probably widening the range 0 - 1.0 leads the algorithms to wrong results. However, I think the original plugin works in floating point. ColorBalance: From my tests I did not notice any difference with the unmodified plugin (I used an appimage). I am under the impression that this plugin already works in floating point and does not need modification. Gradient: Here again I find no difference with the original plugin. Again, I have the impression that the plugin already works in floating point. Overlay (shared effect): I don't notice any difference with the original plugin. Histogram Bezier: I tried extending the range similarly to Histogram (which works well in HDR, after modification). In this case I see no change. The code is much more complex and it is probably not enough to delete the CLAMP. The change I made is to the file "bistogram.C" line 361 I changed the value of 1.0 to 10.0. I also tried editing the file bistogramconfig.C line 110 e 111 I changed the value of 1.0 to 10.0. line 229 I changed the value of 1 to 10. I put these details because the plugin is very important for CC and I would love it if someone more experienced than me could make it work on out-of-range data as well. Besides, the plugin is not only a histogram but also uses the very important "Curves". For the Videoscope plugin I could not make changes because the code is too complicated for my skills; similarly to Histogram Bezier. Finally I describe Color3Way, in which the modification worked. In the original plugin the color wheels already seems to work in floating point, but not the V bar of brightness values (which are clipped). With the modification the V bar also works on out-of-range data. The modification is as follows: File "color3way.C": line 281 I changed the value of 1.0 to 100.0. line 284 I changed the value of 1.0 to 100.0 (I have also tried other values, e.g., 10.0, and the clamp always works up to those values). The floating point calculation works for both the saturation bar and the V bar. With the tests done so far, I have had no problems or errors/warnings on the terminal. I did the tests with exr images and then enabled the internal CinGG engine (but in the tests it also works with "ffmpeg first"). I set the color model to RGBA-FLOAT (inescapable: with integer 8-bit models you cannot have HDR) and the color range to 2020 NCL (but it works with all possible settings, not relevant). The graphics driver is X11 because with X11-OpenGL it does not work. Used patches: 0001-TEST-Simpler-unlimited-float-overlay.patch 0002-Allow-negative-numbers-in-overlayer.patch noclamp_in_histogram.diff Manual changes in color3way.C I am happy with the success with Color3Way (as with Histogram) because I believe it will become increasingly important to work on HDR video in the future. On the other hand, I regret not having success with Curves (Histogram Bezier) because it is an essential plugin for CC.

5 23

Donation and DaVinci Resolve EDL
by Matteo Bini 22 Jan '24

22 Jan '24

Hi Cinelerra GG users and developers, my name is Matteo Bini and I'm new to this mailing list. First of all, I would like to thank you for the amazing work you do on Cinelerra: it is a great non-linear editing software. Because of this, I would like to make a donation to support you. How can I do this? Do you accept bank transfers, credit cards... or even the horrible PayPal? My main question is about DaVinci Resolve. Is there a way to export a timeline from Blackmagic software to Cinelerra GG? I've recently finished shooting a short film, that's been edited and colour-corrected in DaVinci Resolve. I would like to edit its audio on Cinelerra GG. Do you think there's a way to move the synchronised audio clips from the two software, without having to export them by hand? Again, thank you for your incredible effort to produce Cinelerra GG and thank you for your help. -- Matteo Bini

5 9

Re: [Cin] [FFmpeg-user] LPCM in DVD - 44.1/32khz sample rate?
by Andrew Randrianasulu 21 Jan '24

21 Jan '24

On Sun, Jan 21, 2024 at 2:47 PM Paul B Mahol <onemda(a)gmail.com> wrote: > > /* no traces of 44100 and 32000Hz in any commercial software or player */ well, but mpv (and vlc?) supports it .... > > On Sun, Jan 21, 2024 at 3:44 AM Andrew Randrianasulu < > randrianasulu(a)gmail.com> wrote: > > > According to this source (vlc) lpcm dvd audio supports lower frequencies > > like 44100/32000 hz - useful for direct dv transcoding for example .... > > > > https://github.com/videolan/vlc/blob/master/modules/codec/lpcm.c > > > > see lines 524, 608 > > > > Does this mean that libavcodec/pcm-dvdenc.c can be trivially extended to > > support those ? > > > > Same question for mplex. (it only supports 48/96 khz lpcm audio). > > > > I also found this table via mjpeg-users archives: > > > > https://dvd.sourceforge.net/dvdinfo/lpcm.html > > > > it lists dynamic range/gain (?) setting equations. > > > > Not mplex nor ffmpeg support setting this to anything but hardcoded 0x80 > > > > This might be source of my "too loud" lpcm dvd experiments because I was > > making lpcm file via cinelerra-gg's raw pcm output format (using libsndfile > > internally). > > _______________________________________________ > > ffmpeg-user mailing list > > ffmpeg-user(a)ffmpeg.org > > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > > > To unsubscribe, visit link above, or email > > ffmpeg-user-request(a)ffmpeg.org with subject "unsubscribe". > > > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user(a)ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-request(a)ffmpeg.org with subject "unsubscribe".

1 0

sox to lpcm
by Andrew Randrianasulu 21 Jan '24

21 Jan '24

command line: sox /dev/shm/dvd_20240120-153459/dvd.wav -V -t raw -x /dev/shm/dvd_20240120-153459/dvd-1.lpcm I set output file to different name so I can compare pcm directly produced by cingg and sox-converted version. detailed output: sox /dev/shm/dvd_20240120-153459/dvd.wav -V -t raw -x /dev/shm/dvd_20240120-153459/dvd-1.lpcm sox: SoX v14.4.2 sox INFO formats: detected file format type `wav' Input File : '/dev/shm/dvd_20240120-153459/dvd.wav' Channels : 2 Sample Rate : 48000 Precision : 24-bit Duration : 00:01:00.00 = 2880000 samples ~ 4500 CDDA sectors File Size : 17.3M Bit Rate : 2.30M Sample Encoding: 24-bit Signed Integer PCM Endian Type : little Reverse Nibbles: no Reverse Bits : no sox INFO sox: Overwriting `/dev/shm/dvd_20240120-153459/dvd-1.lpcm' sox INFO formats: `/dev/shm/dvd_20240120-153459/dvd-1.lpcm': overriding machine byte-order Output File : '/dev/shm/dvd_20240120-153459/dvd-1.lpcm' (raw) Channels : 2 Sample Rate : 48000 Precision : 24-bit Duration : 00:01:00.00 = 2880000 samples ~ 4500 CDDA sectors Sample Encoding: 24-bit Signed Integer PCM Endian Type : big Reverse Nibbles: no Reverse Bits : no Comment : 'Processed by SoX' sox INFO sox: effects chain: input 48000Hz 2 channels sox INFO sox: effects chain: output 48000Hz 2 channels ===== so, modern sox (-w/-s options were deprecated and replaced by others - thankfully we do not need them if input file autodetected) can process wav files into lpcm suitable for mplex So, guide is much simpler in sense in cingg you just change audio to wav/24 bits, then run sox, and change mplex line to one including -L freq:channels:bits specification. May be you can even prepare text patch and apply it to dvd.sh ? Oh, and in case of 24-bit audio at 48 khz you definitely want to lower your video bitrate ...

1 1

removal from Cin list
by Roberto Carisio 21 Jan '24

21 Jan '24

I would like to be removed fromcin(a)lists.cinelerra-gg.org . I tried but I can't. Thank you -- Roberto Carisio roberto.carisio(a)gmail.com

1 0

patch for 44.1/32 khz pcm input in pcm dvd encoder
by Andrew Randrianasulu 21 Jan '24

21 Jan '24

relative to ffmpeg.git commit 6c4388b468bf92c0c1e7733c6cfe4ff3f9ca9723 lightly tested with mpv and mediainfo like this: ./ffmpeg -i ~/f9518976.mp4 -target pal-dvd -ar 44100 -c:a pcm_dvd -f dvd t.mpg mpv plays sound correctly, mediainfo does not know those frequencies and display 0khz. ;)

1 0

LPCM in DVD - 44.1/32khz sample rate?
by Andrew Randrianasulu 21 Jan '24

21 Jan '24

According to this source (vlc) lpcm dvd audio supports lower frequencies like 44100/32000 hz - useful for direct dv transcoding for example .... https://github.com/videolan/vlc/blob/master/modules/codec/lpcm.c see lines 524, 608 Does this mean that libavcodec/pcm-dvdenc.c can be trivially extended to support those ? Same question for mplex. (it only supports 48/96 khz lpcm audio). I also found this table via mjpeg-users archives: https://dvd.sourceforge.net/dvdinfo/lpcm.html it lists dynamic range/gain (?) setting equations. Not mplex nor ffmpeg support setting this to anything but hardcoded 0x80 This might be source of my "too loud" lpcm dvd experiments because I was making lpcm file via cinelerra-gg's raw pcm output format (using libsndfile internally).

1 0

Sox and mplex
by Andrew Randrianasulu 21 Jan '24

21 Jan '24

Canonical way to use mplex with lpcm sound seems to involve sox https://marc.info/?l=mjpeg-users&m=112004582102258&w=2 ==== 1. sox NAME.wav -t raw -x -s -w -c2 -r48000 NAME.lpcm 2. mplex -S 0 -f 8 -V -o NAME.mpg NAME.lpcm NAME.m2v === I also found at mjpeg-users list this utility that makes wavs into lpcm http://dvd-audio.sourceforge.net/wav2lpcm.tar.gz only 48/96 khz, 16/24bits stereo wavs are supported Also, this little table suggest there IS dynamic range bit in lpcm header https://dvd.sourceforge.net/dvdinfo/lpcm.html dynamic_range X 3 X High 3 bits of byte. dynamic_range Y 5 Y Lower 5 bits of byte linear gain = 2^(4-(X+(Y/30))) in dB gain = 24.082 - 6.0206 X - 0.2007 Y Also, according to this post 24-bit lpcm worked around mjpegtools-1.8.0 release: https://marc.info/?l=mjpeg-users&m=112912922124144&w=2 all this quite theoretical at this point, not tried it yet.

1 0

video on LPCM DVD from DV method
by Andrew Randrianasulu 20 Jan '24

20 Jan '24

https://youtu.be/-NE2LZsVUjo grand total of two and half minutes at whooping 5 fps.

2 5

attempt at fixing too loud sound with raw pcm output
by Andrew Randrianasulu 20 Jan '24

20 Jan '24

try andy dv test file, render only audio as Big Endian, Signed, 16 bits. Load it back and watch too loud audio. note: wav file not tested

1 3