Re: [Cin] more patches for building on my slackware

sorry, there was 4th patch On Friday, April 15, 2022, Andrew Randrianasulu wrote: > due to X libs/headers located in /usr/X11R7... > > but also due to some asm error in mpeg2enc when I build for i686 target... > > http://forum.tinycorelinux.net/index.php/topic,18142.0.html?PHPSESSID= >

[Cin] opencv build trim

https://github.com/Randrianasulu/CinelerraGG-slackbuild/blob/master/openCV4-static-gcc5_more-disable-3.diff basically re-applied locally because opencv build eats a bit too much space... From 72aace7d019acad6020e4eb7a2b73d60e83da4b6 Mon Sep 17 00:00:00 2001 From: Andrew Randrianasulu Date: Sat,

Re: [Cin] megapatch series 8

new, updated series! I moved libbthread at main level so dynamic termux build can be compiled automatically like others. not yet done any additional layout in bdcreate.C On Wednesday, April 13, 2022, Andrew Randrianasulu wrote: > > > On Wednesday, April 13, 2022, Phyllis Smith > wrote: >

Re: [Cin] megapatch series 8

On Wednesday, April 13, 2022, Phyllis Smith wrote: > Not sure what you want to change but making the box a little higher so > that the green + and red x are lower can be done by changing the yS(290) to > a larger number than 290 (what is currently line 481) as shown below in > bdcreate.C >

Re: [Cin] megapatch series 8

On Saturday, April 16, 2022, Phyllis Smith wrote: > Andrew, another Bluray update. > From megapile_8, I have in the following Bluray patches with 2 > modifications and the bluray disc works on both the Samsung UHD and the LG > Bluray connected to the TV. > >

Re: [Cin] megapatch series 8

thanks, it was not supposed to build this lib on non-android ( On Wednesday, April 13, 2022, Andrea paz wrote: > Still crashing with megapile_9, I enclose cin5.log and config.log > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] megapatch series 8

does this patch (on top of megapile_9) help? On Wednesday, April 13, 2022, Andrew Randrianasulu wrote: > thanks, it was not supposed to build this lib on non-android ( > > > > On Wednesday, April 13, 2022, Andrea paz > wrote: > >> Still crashing with megapile_9, I enclose cin5.log and

Re: [Cin] cingg vaapi on i3-3227U cpu

yeah, someone just need to implement this. Also found this discussion, it seems va-api a bit.. shortsightened: https://github.com/intel/libva/issues/540 "libva (v2.12) does not find /dev/dri/renderD129 (stops scanning for GPUs if "renderD128" is not present) #540 Closed eero-t opened this issue

Re: [Cin] megapatch series 8

actually if this patch will not help try also second on top of all this - I renamed source file (so clang stopped complaining) and deleted all those licence texts from middle of file (due to auto-cat-ing sources earlier. now I just compile single file into single o/a file. still work on Termux

Re: [Cin] megapatch series 8

ah, libdv + firewire libs... you can try to disable them (without-dv, without-firewire), or pass '--disable-static-build' or add them to cinelerra/Makefile {i do not have them in termux, not sure if have any sense here.. no pci for external card, no iLink by design..} sorry, I meet those so many

Re: [Cin] Still on hardware acceleration

On Tue, Sep 5, 2023 at 10:59 AM Andrea paz via Cin wrote: > > @Andrew > Sorry to bother you again on a subject you have already tried to > explain over and over again. > > Reading this page: > https://trac.ffmpeg.org/wiki/HWAccelIntro > it is my understanding that when decoding (note: from here

Re: [Cin] Still on hardware acceleration

On Tue, Sep 5, 2023 at 11:36 AM Andrew Randrianasulu wrote: > > On Tue, Sep 5, 2023 at 10:59 AM Andrea paz via Cin > wrote: > > > > @Andrew > > Sorry to bother you again on a subject you have already tried to > > explain over and over again. > > > > Reading this page: > >

Re: [Cin] Timeline x Hollywood

пн, 11 сент. 2023 г., 17:44 Andrea paz via Cin : > To make up for my recent mistake (timeline = canvas), I offer a > curious video on what a timeline looks like for large professional > projects. However, their entire YouTube channel is interesting and > informative. > Thanks, it surely was

Re: [Cin] CinGG/NLE comparison

пн, 11 сент. 2023 г., 18:16 Andrew Randrianasulu : > > > пн, 11 сент. 2023 г., 17:42 Andrea paz via Cin >: > >> By now my mental abilities have greatly decayed, so what I write and >> say must be carefully corrected. Sorry. >> I didn't remember CTRL+Z anymore; thanks for the correction. >> >> >

Re: [Cin] CinGG/NLE comparison

пн, 11 сент. 2023 г., 17:42 Andrea paz via Cin : > By now my mental abilities have greatly decayed, so what I write and > say must be carefully corrected. Sorry. > I didn't remember CTRL+Z anymore; thanks for the correction. > > > It is in the "Cutting a Region" paragraph and reads "Note that we

[Cin] DATvideo

compressed Video on Digital Audio cassettes! https://m.youtube.com/watch?v=mOug4t5r0P4 contain link to blog and supposedly github sources, too! Nice use of digital i/o. http://www.theresistornetwork.com/2019/02/datvideo-storing-video-on-digital-audio.html?m=1

Re: [Cin] CVE in libwebp

пт, 15 сент. 2023 г., 18:26 Phyllis Smith : > libwebp is currently at version 1.1.0 for a reason: it requires cmake 3.5 > and older versions of ubuntu as well as some other older O/S do not have > that. This is documented in the manual with the suggestion of users who > want an upgrade will

[Cin] CVE in libwebp

https://github.com/webmproject/libwebp/commit/902bc9190331343b2017211debcec8d2ab87e17a so far Slackware 15.0 bumped libwebp to 1.3.2 guess we ought to do the same? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] CVE in libwebp

can you check this attached patch with libwebp downloaded from https://github.com/webmproject/libwebp/archive/refs/tags/v1.3.2.tar.gz just rename to libwebp-1.3.2.tar.gz and put in thirdparty/src пт, 15 сент. 2023 г., 18:31 Andrew Randrianasulu : > > > пт, 15 сент. 2023 г., 18:26 Phyllis

Re: [Cin] cin freeze with group move?

I retested and sadly even with my patch hang still here (probably depend on something else) On Thu, Sep 14, 2023 at 9:37 AM Igor BEGHETTO via Cin wrote: > > Andrew, I am sorry. Maybe I wasn't clear. > I followed your steps/video and tested as I could on a my project. I > did't use your

[Cin] Fwd: CVE in libwebp

-- Forwarded message - From: Andrew Randrianasulu Date: Sat, Sep 16, 2023 at 7:22 AM Subject: Re: CVE in libwebp To: Phyllis Smith ah, it was "working" here because I had libwebp installed what about adding patch 0002 on top of previous one? On Sat, Sep 16, 2023 at 5:47 AM

Re: [Cin] cin freeze with group move?

so with debug it sits here when I ctrl-c it: SigHandler::signal_handler total files=0 Thread 1 "cin" received signal SIGINT, Interrupt. 0x08624b9c in get_edit_regions (edits=0xb3d0, regions=...) at edl.C:911 911 if( pos >= range.end ) continue; (gdb) p range_end

Re: [Cin] cin freeze with group move?

On Sat, Sep 16, 2023 at 10:52 AM Andrea paz wrote: > > I tried testing using only the keyboard: ctrl+x; ctrl + c and ctrl + v. > I still haven't had any freeze. > I've tried using keyboard and mouse together and I always have the > same result: no freeze. > (I still have your first patch

Re: [Cin] CinGG/NLE comparison

On Sat, Sep 16, 2023 at 10:21 AM Igor BEGHETTO via Cin wrote: > > To me, it seems good. I remember to all of you that We have a Manual. > I don't know how many people read the Document but the Manual is well, > enough, documented, I think. > For a beginner, using Cinelerra-GG is not simple but

Re: [Cin] cin freeze with group move?

so second attempt at fixing hang - declare both variables volatile... I wonder if anyone can reproduce this hang ... On Sat, Sep 16, 2023 at 9:35 AM Andrew Randrianasulu wrote: > > so with debug it sits here when I ctrl-c it: > > SigHandler::signal_handler total files=0 > > Thread 1 "cin"

Re: [Cin] cin freeze with group move?

вс, 17 сент. 2023 г., 10:38 Andrea paz : > I try to compile with the only patch 0004-Fix-for-group-move-hang-v2.patch. > Build OK; no error messages on terminal. > > I started the appimage while compiling CinGG, but had no LV2 errors. > (I have a CPU with many threads and have lots of Ram). > No

Re: [Cin] Fwd: CVE in libwebp

th > wrote: > >> With patch 0002, it now builds and a single render test worked. Will >> test on Ubuntu 16 and older Debian sometime today yet after looking at >> Andrea's odt/pdf file and other's commentary on it. >> >> On Fri, Sep 15, 2023 at 10:38 PM Andrew Randrianasulu

Re: [Cin] fileexr reading error handling

пт, 1 сент. 2023 г., 01:27 Phyllis Smith : > Just FYI: > My comprehension of this bug with Background Rendering change of file > format is still missing mostly due to lack of time yesterday, but I will > follow the discussion and try to understand it. Thank goodness Andrea was > able to follow

[Cin] Cingg bg render crash video scenario

https://youtu.be/URnvDY7Zjic at least cin does this on my 32-bit-on-64-bit kernel system ... recorded by another instance of the same cin version. Note, my machine set to full 3.97 Ghz speed. Also, I have 4 frames per bg job setting -- Cin mailing list Cin@lists.cinelerra-gg.org

Re: [Cin] Monthly AppImage updates

чт, 31 авг. 2023 г., 23:26 Phyllis Smith via Cin : > Despite the potential for problems, late checkin of changes, and not too > much testing, a new set of AppImages is now available for download. As > always, if problems, simply revert to the previous AppImage. Changes > includedare listed

Re: [Cin] fileexr reading error handling

On Fri, Sep 1, 2023 at 1:59 AM Andrew Randrianasulu wrote: > > > > пт, 1 сент. 2023 г., 01:27 Phyllis Smith : >> >> Just FYI: >> My comprehension of this bug with Background Rendering change of file format >> is still missing mostly due to lack of time yesterday, but I will follow the >>

Re: [Cin] fileexr reading error handling

пт, 1 сент. 2023 г., 00:23 Phyllis Smith : > Catching up on email now. > > with shared 4.4 rebuild I got crash due to new ffmpeg filters I >> enabled, so I added them to blocklist in ffmpeg/plugins.opts >> >> Andrew, in case you did not notice, I checked in the plugin.opts file you > had attached

Re: [Cin] selectable vaapi decoder device

пн, 28 авг. 2023 г., 20:43 Phyllis Smith : > > On Sat, Aug 26, 2023 at 3:36 AM Andrew Randrianasulu < > randrianas...@gmail.com> wrote: > >> Actually, I think this version will do encode vaapi device selection >> too, like this: >> >> CIN_DRM_DEC=/dev/dri/renderD129

Re: [Cin] Current heap of patches

пн, 28 авг. 2023 г., 20:52 Phyllis Smith : > Patches concerning the following have been checked into GIT: > 1) libav version in About and on startup window > 2) Copyright in About and on startup window for Cinelerra-CV and > Cinelerra-GG (which includes Andrew-R by default in that group and I am

Re: [Cin] Cingg bg render crash video scenario

пт, 1 сент. 2023 г., 04:28 Phyllis Smith : > OK, and is this WITHOUT the fix in? > yes, I have rebuild Slackware pkg from git, installed it -> no more crash! > > On Thu, Aug 31, 2023 at 5:51 PM Andrew Randrianasulu < > randrianas...@gmail.com> wrote: > >> https://youtu.be/URnvDY7Zjic >> >> at

Re: [Cin] Cingg bg render crash video scenario

пт, 1 сент. 2023 г., 09:43 Andrew Randrianasulu : > > > пт, 1 сент. 2023 г., 09:38 Andrea paz : > >> In my opinion, one possible source of BR problems is when we use CinGG >> as normal users, but the default BR folder is in /tmp and thus >> requires root privileges. Perhaps it would be better if

Re: [Cin] Cingg bg render crash video scenario

пт, 1 сент. 2023 г., 09:38 Andrea paz : > In my opinion, one possible source of BR problems is when we use CinGG > as normal users, but the default BR folder is in /tmp and thus > requires root privileges. Perhaps it would be better if CinGG created > a default folder in

[Cin] openexr error handling

According to this page https://openexr.com/en/latest/ReadingAndWritingImageFiles.html You may have noticed that in the example above, there are no explicit checks to verify that writing the file actually succeeded. If the OpenEXR library detects an error, it throws a C++ exception instead

Re: [Cin] fileexr reading error handling

ср, 30 авг. 2023 г., 18:25 Phyllis Smith : > Andrew, I do not think that the c++ code "try" is going to work -- it is > never used anywhere else and probably for a good reason. Is there an > alternative? > well, this is official way openexr does error handling ... it also fixes my error (try

Re: [Cin] cin freeze with group move?

On Tue, Sep 12, 2023 at 3:47 PM Andrew Randrianasulu wrote: > > So, I tried some of the simples group move moves. > > 1) load 28 sec of media (1 audio/1 video mp4). > > 2) switch to d mode. > > 3) double-clic on video track where media piece is. > > It highlight it and add both A and V to group

Re: [Cin] cin freeze with group move?

I tried to fix hang by checking if k>0, while even just printf was enough (I guess race condition somewhere?) Igor, Andrea, Phyllis - can you test this patch very well with various group/plugin/label moves? On Tue, Sep 12, 2023 at 4:23 PM Andrew Randrianasulu wrote: > > On Tue, Sep 12, 2023 at

Re: [Cin] cin freeze with group move?

https://youtu.be/JwUrcPF9Dtk (1:21) it took me multiple attempts but it hanged eventually. On Tue, Sep 12, 2023 at 7:57 PM Andrea paz wrote: > > I can't reproduce the crash. > Could you make a small video so that I can replicate your steps exactly? -- Cin mailing list

Re: [Cin] CinGG/NLE comparison

On Tue, Sep 12, 2023 at 12:37 PM Andrea paz via Cin wrote: > > > Also, my favourite "you drag media handle at edit's end and it behaves > > unintuitively" was not included :) (may be other editors behave the same?) > I didn't quite understand this point; can you explain more? (Or write > the

Re: [Cin] cin freeze with group move?

вт, 12 сент. 2023 г., 23:01 Andrea paz : > I cannot reproduce the freeze, even by varying formats and number of > tracks. I compiled with the new patch and found no errors. Obviously > still no freeze. > I recall I had some freezes/crashes during cingg development no-one was getting. May be due

Re: [Cin] cin freeze with group move?

tch) > IgorBeg > > > Il 13/09/2023 02:26, Andrew Randrianasulu via Cin ha scritto: > > > > > > вт, 12 сент. 2023 г., 23:01 Andrea paz > <mailto:gamberucci.and...@gmail.com>>: > > > > I cannot reproduce the freeze, even by varying formats and numbe

Re: [Cin] fileexr reading error handling

чт, 31 авг. 2023 г., 10:01 Andrea paz : > Compiling from last git: > > Compiling: OK (no crash; no errors) > > > Test with "Try ffmpeg last": > > Render EXR sequence: OK (43 fps) > > Load EXR sequence: OK > > Playback and effects on EXR sequence: OK > > > Other image sequences: OK > > EXR: 43 fps

Re: [Cin] fileexr reading error handling

чт, 31 авг. 2023 г., 10:50 Andrea paz : > I tried leaving the BR on and also turning it off between trials (from > "Preferences" not "toggle"). I have tried disabling the BR and then > deleting the sequence manually. In this case, when I try a new > sequence in a different format I get a series

Re: [Cin] fileexr reading error handling

чт, 31 авг. 2023 г., 10:31 Andrea paz : > > Thanks! Did you try yesterday's scenario with bg render set to jpeg, > enabled, then set to any other compression / filetype, and re-enabled via > menu so you have red bar at top of topmost video track but at this point it > made from wrong image type

Re: [Cin] libtiff dependency

чт, 31 авг. 2023 г., 00:17 Phyllis Smith : > Andrew, is this correct in: > "0001-Add-libjpeg-dep-to.libtiff-in-thirdparty-Makefile.patch" > that is, no comma??? between libwebp and libjpeg ?? as shown below > I noticed in one other example line "," was separating name of procedure from module

Re: [Cin] Current heap of patches

вт, 29 авг. 2023 г., 21:48 Phyllis Smith : > Oh, and does this have to be backed out when we actually upgrade to ffmpeg > 6.0/6.1 ?? I am confused by the patches name including 6.0 in it. > > 0002-Fix-build-in-pluginfclient.C-with-ffmpeg-6.0.patch >> > no, it fix build with 6.0+. > -- Cin

Re: [Cin] Current heap of patches

вт, 29 авг. 2023 г., 23:49 Phyllis Smith : > Will try to compile now in ubuntu 16 and then debian 32-bit. Not sure how > much testing I will be able to actually do though because tomorrow is a > "lost day". > Its time to me to power up desktop, then :) sorry for late patches, I was not

Re: [Cin] Current heap of patches

вт, 29 авг. 2023 г., 21:41 Phyllis Smith : > Andrew, I "believe" I have the whole heap checked into GIT. Please verify > at your convenience (as long as it is before the morning of the 31st !! > smiley face). I played a few different audio tracks. This last GIT > checkin included: > >

Re: [Cin] Current heap of patches

вт, 29 авг. 2023 г., 21:41 Phyllis Smith : > Andrew, I "believe" I have the whole heap checked into GIT. Please verify > at your convenience (as long as it is before the morning of the 31st !! > smiley face). I played a few different audio tracks. This last GIT > checkin included: > >

Re: [Cin] fileexr reading error handling

On Thu, Aug 31, 2023 at 12:59 AM Phyllis Smith wrote: > > Andrew, could you check the final GIT checkin to make sure I got it right? I > found no problems but only minimal testing. > Andrea, if you have a chance to build from the latest GIT and send me email > before I start AppImage builds on

Re: [Cin] fileexr reading error handling

чт, 31 авг. 2023 г., 00:59 Phyllis Smith : > Andrew, could you check the final GIT checkin to make sure I got it > right? I found no problems but only minimal testing. > I also build (and playback-tested) current git + ffmpeg 6.0 on termux/aarch64 (ok) and FreeBSD 13.0 amd64 (also ok). so,

Re: [Cin] Oh, no, my ffmpeg 6.0 patch was failing with ffmpeg 4.4

ugh, I think I have another patch voming in addition to this . libjpeg dep for libtiff in thirdparty/Makefile. sorry! this specific patch shouldaffect only shared (*bsd) builds on old ffmpeg, or shared build on my Slackware box. I prefer to have tagged release buildable everywhere, yet I

[Cin] Oh, no, my ffmpeg 6.0 patch was failing with ffmpeg 4.4

Now fixed hopefully tested on Slackware 15.0 i586 no-thirdparty build and termux/aarch64 rebuild with ffmpeg 6.0 Slackware line was: LDFLAGS=`pkg-config --libs x11` setarch i686 ./configure --with-single-user --without-thirdparty --without-lv2 --without-libdpx make there was: make --version

[Cin] libtiff dependency

sorry for mess ... From f65fb0dc537894ea779e70cfc4ca5ffacfc63e4e Mon Sep 17 00:00:00 2001 From: Andrew Randrianasulu Date: Wed, 30 Aug 2023 05:27:10 +0300 Subject: [PATCH] Add libjpeg dep to.libtiff in thirdparty/Makefile --- cinelerra-5.1/thirdparty/Makefile | 2 +- 1 file changed, 1

Re: [Cin] CinGG 20230830 git code failure

чт, 31 авг. 2023 г., 14:39 Mat via Cin : > Hi, > > Pulled down git updates about 09 UTC today. > Built from scratch on Debian 11, 32 bit, Mint21.2 64 bit, and Fedora 38 > 64 bit, all on real hardware (not in VM). > Same hw or different in each case? > - Debian builds fine, CinGG itself,

Re: [Cin] fileexr reading error handling

чт, 31 авг. 2023 г., 16:16 Andrea paz : > I did some more testing for BR. > I noticed that to change the image type you just remove the "toggle" > and then from "Preferences" change format and give "Apply" (sometimes > you need "OK"). Almost always it works that way; at the limit you have > to

[Cin] filepng additional error handling

not sure why it was apparently working yesterday? example used: https://android.googlesource.com/platform/external/libpng/+/aa0ce810a62b165c39abf6252c5fec107716a2fe/example.c From 2cb59daa35ae3db75fb98a8a5e07ecd14ddeafb0 Mon Sep 17 00:00:00 2001 From: Andrew Randrianasulu Date: Wed, 30 Aug 2023

[Cin] fileexr reading error handling

Using https://openexr.com/en/latest/HelloWorld.html as example so for now I have base commit d51dc1ff2dbd920c6488af4380b8064c9b6a7b4c (origin/master, origin/HEAD) Author: Good Guy Date: Tue Aug 29 20:20:10 2023 -0600 Credit Andrew - rest of fix for Arch (and termux) which includes

[Cin] Trying to understand colour, try N!

https://blender.stackexchange.com/questions/46825/render-with-a-wider-dynamic-range-in-cycles-to-produce-photorealistic-looking-im well, this one says EXR can hold quite a big value per channel, way above 1.0f, obviously. But for displaying (and encoding?) it must be compressed back to

Re: [Cin] Trying to understand colour, try N!

вт, 7 нояб. 2023 г., 18:13 Andrew Randrianasulu : > > https://blender.stackexchange.com/questions/46825/render-with-a-wider-dynamic-range-in-cycles-to-produce-photorealistic-looking-im > > > well, this one says EXR can hold quite a big value per channel, way above > 1.0f, obviously. But for

Re: [Cin] Trying to understand colour, try N!

вт, 7 нояб. 2023 г., 18:32 Andrew Randrianasulu : > > > вт, 7 нояб. 2023 г., 18:13 Andrew Randrianasulu : > >> >> https://blender.stackexchange.com/questions/46825/render-with-a-wider-dynamic-range-in-cycles-to-produce-photorealistic-looking-im >> >> >> well, this one says EXR can hold quite a

Re: [Cin] Trying to understand colour, try N!

вт, 7 нояб. 2023 г., 18:47 Andrew Randrianasulu : > > > вт, 7 нояб. 2023 г., 18:32 Andrew Randrianasulu : > >> >> >> вт, 7 нояб. 2023 г., 18:13 Andrew Randrianasulu > >: >> >>> >>>

[Cin] gimp 2.10 and exact small color values

https://superuser.com/questions/1411132/manually-entering-16-bit-color-values-in-gimp/1411238#1411238 So, forgetting about setting the FG color, *the way to create a surface with a precision smaller than 1/256 in any component in GIMP 2.10 is using the painting or color tools*. You can do

[Cin] more vfx from reddit, exr, linearization

https://www.reddit.com/r/vfx/comments/ptk6ej/confusion_about_floating_point_in_color_space/ well, I think this answer answers it ... Q first: = Confusion about Floating Point in Color Space Transforms/Management from Learning

Re: [Cin] oiiotool

вт, 7 нояб. 2023 г., 21:46 Andrew Randrianasulu : > oiiotool --stats -v /dev/shm/1.exr Reading > /dev/shm/1.exr >/dev/shm/1.exr : 4096 x 2048, 3 channel, float > openexr > channel list: R, G, B > chromaticities: 0.63, 0.33001, 0.34,

[Cin] oiiotool

oiiotool --stats -v /dev/shm/1.exr Reading /dev/shm/1.exr /dev/shm/1.exr : 4096 x 2048, 3 channel, float openexr channel list: R, G, B chromaticities: 0.63, 0.33001, 0.34, 0.63, 0.150002, 0.0599972, 0.3127, 0.329

Re: [Cin] Trying to understand colour, try N!

вт, 7 нояб. 2023 г., 23:25 Andrea paz : > > Still not sure where, may be in fader? (where fade can't be more than > 100%) . May be its time to ask Lion (Adam). > > Maybe it is in the code strings where "CLAMP" is? > well, this is macro, so it used to clamp various things, not just colors ..

Re: [Cin] oiiotool

вт, 7 нояб. 2023 г., 23:31 Andrea paz : > > also, guess we better to note in manual that even if cingg outputs fp32 > exr/tiff values there are normalized to 0-1.0f as far as we can see. > > Where do you think is best to put the note? Some hints are already > there in the appendix on Color

Re: [Cin] Trying to understand colour, try N!

вт, 7 нояб. 2023 г., 23:33 Andrea paz : > > well, this is macro, so it used to clamp various things, not just colors > .. > > I had found this string in some plugins. Could it be that it is about > colors? > CLAMP(output, 0, 1.0); > possible, but try to read roughly code around it... and

[Cin] Floating point numbers between 0 and 1.0

https://stackoverflow.com/questions/17949796/how-many-unique-values-are-there-between-0-and-1-of-a-standard-float ppl here come up with this number: 1,065,353,215. so ... even between 0.0f and 1.0f there is quite a number of ... numbers. Still, out of range numbers useful in photo work like

Re: [Cin] ffmpeg 6.1 probably delayed ?

вс, 29 окт. 2023 г., 18:38 Andrew Randrianasulu : > > > вс, 29 окт. 2023 г., 18:27 Phyllis Smith : > >> Oh wow. I guess I learned a lesson here -- don't wait for the point 1 >> (.1) release. But still I am a little confused because I always thought >> that the point 1 release was to fix flaws

Re: [Cin] ffmpeg 6.1 probably delayed ?

вс, 29 окт. 2023 г., 19:04 Phyllis Smith : > Thanks - waiting for download site, https://ffmpeg.org/download.html , to > update tar ball to 6.1. > I guess nv headers also should be updated, so hopefully patch10 will not needed? https://github.com/FFmpeg/nv-codec-headers/releases > > On Sun,

[Cin] ffmpeg 6.1 probably delayed ?

http://ffmpeg.org/pipermail/ffmpeg-devel/2023-October/316264.html -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] ffmpeg 6.1 probably delayed ?

вс, 29 окт. 2023 г., 18:27 Phyllis Smith : > Oh wow. I guess I learned a lesson here -- don't wait for the point 1 > (.1) release. But still I am a little confused because I always thought > that the point 1 release was to fix flaws in the main release and not to > add new features. > I think

Re: [Cin] Plugins in integer or in float

вс, 5 нояб. 2023 г., 23:16 Phyllis Smith via Cin : > Maybe Andrew knows how to detect this -- if it is just a matter of looking > at each plugin to see if it looks like the word "float" is in effect for > the majority of variables, that is something I could do. Or if Andrew has > another way? >

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 00:00 Andrew Randrianasulu : > > > вс, 5 нояб. 2023 г., 23:16 Phyllis Smith via Cin < > cin@lists.cinelerra-gg.org>: > >> Maybe Andrew knows how to detect this -- if it is just a matter of >> looking at each plugin to see if it looks like the word "float" is in >> effect for

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 01:53 Andrea paz : > > sorry for absence of easy answer ... > You are right: I cannot understand the operation by superficial > reading of the code. Each plugin has all the strings that I thought > could discriminate their operation. > Trying to read the code of histogram.C I

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 11:49 Andrea paz : > I did some tests to see which of the major CC plugins use floats and > which use integers. > It turns out that only Blue Banana and Gamma support values above the > range (0-1.0). Histogram Bezier reads values above 1.0 but does not > use them, returning

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 18:02 Andrew Randrianasulu : > > > пн, 6 нояб. 2023 г., 11:49 Andrea paz : > >> I did some tests to see which of the major CC plugins use floats and >> which use integers. >> It turns out that only Blue Banana and Gamma support values above the >> range (0-1.0). Histogram

Re: [Cin] Plugins in integer or in float

On Mon, Nov 6, 2023 at 10:10 PM Andrea paz wrote: > > A change on Histogram dates back to May 2021. See: > https://cinelerra-gg.org/download/testing/ interesting, thanks . Right now I see that Cingg compiled at may 2017 was showing over 100 values in scopes (with just videoscope and not any

Re: [Cin] Plugins in integer or in float

On Mon, Nov 6, 2023 at 10:07 PM Andrew Randrianasulu wrote: > > On Mon, Nov 6, 2023 at 10:10 PM Andrea paz > wrote: > > > > A change on Histogram dates back to May 2021. See: > > https://cinelerra-gg.org/download/testing/ > > interesting, thanks . > > Right now I see that Cingg compiled at

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 20:03 Andrea paz : > It seems to me that Adam's examples always involve integers, 8-, 10- > or 16-bit, but always integers. Interesting that Adam's Histogram also > shows data above 1.0, while in CinGG it happens with Histogram Bezier > but not with Histogram (nor with

Re: [Cin] Plugins in integer or in float

пн, 6 нояб. 2023 г., 23:13 Andrea paz : > In any case, using any plugin (even BlueBanana or Gamma) returns the > clip... > in scope from Compositor? yes .. but attaching videoscope to track still shows them go over 100 even with plugin(s) attached ... not sure how output values suppose to go

[Cin] nvenc on latest appimage works!

So, I compiled 64-bit proprietary nvidia driver on Salix 15.0 x64 xfce (by downloading and fully compiling kernel from kernel.org, then using NVIDIA-Linux-x86_64-470.199.02.run file from Nvidia website. anf compiled ffmpeg 4.4 against ff-nvidia-headers from salix repo. And fullhd video was

Re: [Cin] Fmpeg 6.1 in july?

http://ffmpeg.org/pipermail/ffmpeg-devel/2023-September/314594.html a bit late, probably not in September (2023). On Tue, Jun 6, 2023 at 7:03 PM Andrew Randrianasulu wrote: > > https://www.phoronix.com/news/FFmpeg-Vulkan-Video > > At least image embedded in post seems to say so -- Cin

Re: [Cin] cin freeze with group move?

пт, 22 сент. 2023 г., 00:00 Phyllis Smith : > Does not fail on Fedora. > With Debian 9.1 32-bit, the freeze happens on the first move. With the > "volatile" patch in, it works. I had an old AMD Slackware O/S and wanted > to try it there also, but it had an error on the build so decided not to >

Re: [Cin] cin freeze with group move?

other way to fix it. > On Sat, Sep 16, 2023 at 1:32 AM Andrew Randrianasulu via Cin < > cin@lists.cinelerra-gg.org> wrote: > >> so second attempt at fixing hang - declare both variables volatile... >> >> I wonder if anyone can reproduce this hang ... >> >>

Re: [Cin] cin freeze with group move?

> > > >> On Sat, Sep 16, 2023 at 1:32 AM Andrew Randrianasulu via Cin < >> cin@lists.cinelerra-gg.org> wrote: >> >>> so second attempt at fixing hang - declare both variables volatile... >>> >>> I wonder if anyone can reproduce this hang

Re: [Cin] New release update

сб, 30 сент. 2023 г., 21:36 Phyllis Smith via Cin < cin@lists.cinelerra-gg.org>: > New September 30, 2023 release update with the addition Alternative > Shortcuts AppImage included at: > > https://cinelerra-gg.org/download/images/CinGG-20230930-alternative_shortcuts.AppImage > Earlier email

Re: [Cin] New release update

вс, 1 окт. 2023 г., 14:13 Igor BEGHETTO via Cin : > Thank youuu!!! > Does the patch for the alternative shortcuts need to be updated every > month or does the same work for every code change ? > I don't know/understand how the patch work. Thanks! > It depends on how much code surrounding

Re: [Cin] Varied Standard Shortcuts AppImage version for testing

чт, 28 сент. 2023 г., 01:13 Phyllis Smith via Cin < cin@lists.cinelerra-gg.org>: > There is a modified Shortcuts AppImage version for testing on 64-bit O/S > which is set up to be more in sync with what is considered to be "Standard" > shortcuts for NLEs.. IgorB uses these and prepared a listing

Re: [Cin] Libvpx vulnerability

вт, 3 окт. 2023 г., 16:50 Andrew Randrianasulu : > > > вт, 3 окт. 2023 г., 11:56 Andrea paz via Cin : > >> A vulnerability hole in the vpx library has come out these days. Do >> you think it is worth updating? >> > > I think yes, because we at 1.13.0 already ... may be we can just add/apply >

[Cin] ffmpeg.git.patch10 started to fail ...

Because ffmpeg 6.1 still not branched I guess we better to look into relevant changes ... and adapt our patch. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] ffmpeg.git.patch10 started to fail ...

this one apparently work better, in sense it compiles! can anyone check if cuda/nvenc hw acceleration still works with it? On Tue, Oct 3, 2023 at 4:53 PM Andrew Randrianasulu wrote: > > Because ffmpeg 6.1 still not branched I guess we better to look into relevant > changes ... and adapt our

[Cin] offtopic: old Sony camera on yt

https://m.youtube.com/watch?v=h-wG4o8Kaug "Sony DVW 790WSP. Perhaps the highest quality SD camcorder of all time. Broadcast grade DigiBeta." if you dig into comments you will find that apparently BBC still shots interlaced HD?! -- Cin mailing list Cin@lists.cinelerra-gg.org

Re: [Cin] ffmpeg.git.patch10 started to fail ...

ср, 4 окт. 2023 г., 04:28 Phyllis Smith : > OK, will work on getting the build to work as I mentioned earlier. Next > time a new version of ffmpeg is released, we should probably upgrade and > not wait for the ".1" release which is what we have traditionally done. If > we had known how long 6.1

<    5   6   7   8   9   10   11   12   13   14   >