That is the BIG advantage of AppImage -- it will work on most other Linux
operating systems and on most other same or any newer version levels. And
that is why ubuntu 16 will most likely be the version where the alternative
shortcuts will be created for several years yet! Thank you IgorB for
Unfortunately, Dav1d uses meson instead of cmake. The current old version
included with CinGG was converted from meson to cmake. It would take
someone who knows both meson and cmake intricacies to do the same
conversion for an updated version of Dav1d.
On Fri, May 31, 2024 at 12:35 PM Andrea
*New release *of May 2024 appimages now available at:
https://cinelerra-gg.org/download/images/
These executables contain the same updates as the latest packages for newer
operating systems at:
https://github.com/einhander/cin-gg-packages/releases/tag/20240522
-- This means that if you
Because the last release was Feb. 29th, the fixes I made as recommended by
SGE were only implemented locally on my computer so that the online
manual/files/source would still be synched with the February 29 date.
With today's updated release, there should no longer be a conflict with
duplicated
Thanks to the user and Andrea for good suggestions and implementation which
I have reviewed and checked into GIT. I also opened up a Bug Tracker #660
for the user's discovery of a long time error for the Render menu, Render
Range of Selection or In/Out points, starting at the beginning of the
Terje, thanks for letting us know. I have downloaded it and will test in
June to use with CinGG.
On Wed, May 29, 2024 at 9:47 AM Terje J. Hanssen via Cin <
cin@lists.cinelerra-gg.org> wrote:
> According to Phoronix the Alliance of Open Media project quietly released
> (the Intel based) SVT-AV1
Reminder for those with recent versions of the Operating Systems, you can
install the packages from Andrey's website:
https://github.com/einhander/cin-gg-packages/releases/tag/20240522
Quote from website is below (I do not currently see suse15 there):
> Storage for Cinelerra-gg nightly packages
Very entertaining, but I did not watch all 22+ minutes. It is amazing how
some of the 20+ year old software was really pretty good and still works
under the right circumstances. I still use "xv" daily which was written in
the 1990's!
On Thu, May 23, 2024 at 9:04 AM Andrew Randrianasulu via Cin <
FFmpeg 7.0 checked into GIT (previous version 6.1) thanks to Andrew
updating numerous patches in ffmpeg plus another bunch in the cinelerra
subdirectory (5 or so). And thanks to Andrea and others for all of the
testing and problem reporting. If Andrew and Andrea can verify I did not
make any
Thanks again to Andrea. I had to make a single change as my Latex got an
error on: ($#ff00$). I had to remove the 2 $ to solve it.
> To add the explanation of the new keys and equalize the presentation
> to what was done for ChromaKey-HSV, I updated the manual for the
> ChromaKey plugin.
About CinGG in wayland as stated below. I think the error message is from
the graphics library (gl_...) and is probably one of the startup screens
that has gl commands that may be different now than before. Just a guess!
On Tue, May 21, 2024 at 2:16 PM Andrea paz
wrote:
> I tried to start
This is consistent behavior with other plugins. For example Sharpen,
Linear Blur, Wave, Radial Blur.
> Instead, an important thing that I had noticed even before trying
> wayland, but forgot to report in the previous email is that the
> “Default” button returns the threshold to 10, as required.
Chromakey plugin has had its menu improved by anonymous contribution and it
has been checked into GIT. (Andrea, can you test it too? and check the
manual to make sure still matches and make new image?)
Improvements include:
- added Default button
- default values for Threshold and Slope changed
P.S. although there have not been very many users testing ffmpeg 7.0, I
have found no problems with it and I believe that Andrea uses it frequently
also with no new reported issues. I am in the process of outlining a set
of tests to run, i.e. a "test suite", when a library like ffmpeg is updated
>
> Also, it was suggested that we (cinelerra-gg) can create different git
> branch < named, say, "testing" > for "potentially unstable" patches, like
> current ffmpeg 7.0 patchset and then merge back to main/stable when feature
> is deemed ready.
>
+2 for testing branch. (wink, wink).
Thank you. The new image of chromakeyhsv menu has been checked into GIT.
On Thu, May 16, 2024 at 12:43 PM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:
> With the new, beautiful, configuration window, we need to change the
> image in the manual.
> --
> Cin mailing list
>
That is probably OK as long as it just keeps working. I did notice that we
are at 0.7.4 and there is an 0.8.0 available but "if it isn't broke, don't
fix it".
Probably in another 20 years, Cinelerra will be replaced with a totally
revolutionary alternative. But it won't be Olive.
On Tue, May
OK, it is removed in GIT.
On Mon, May 13, 2024 at 3:26 PM Andrea paz
wrote:
> I would prefer tò remove the references tò Compositore, It serms tò me
> that It leads tò more confusione.
>
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Andrea, I think it is explained just fine and I would actually like to
leave it in. My reasoning is that by saying"While the rendering is in
progress some frames from the timeline are displayed in the Compositor
window, but it has no bearing on the actual rendering process"it makes
it
Checked into the GIT for the Manual. Like said previously, instead of
having to read the entire chapter on Rendering, it is easy to get started
by just checking these 3 items as Andrea has documented.
> I wrote a short introduction for chapter 7 of the manual, the one with
> the rendering
Checked into GIT an anonymous contribution for a much improved ChromakeyHSV
menu to include:
1) Now there are individual boxes on the left side where you can either
keyin a distinct value or use the up/down arrows to change the value. This
gives you a much better control than where previously
eo to test, but it sure did not
>>>> work.
>>>> I just picked the first one at::
>>>> https://filesamples.com/formats/mjpeg which was:
>>>> sample_1280x720_surfing_with_audio.mjpeg
>>>>
>>>> On Fri, May 10, 2024 at 4:47
ps://filesamples.com/formats/mjpeg
>> which was:
>> sample_1280x720_surfing_with_audio.mjpeg
>>
>> On Fri, May 10, 2024 at 4:47 PM Andrew Randrianasulu <
>> randrianas...@gmail.com> wrote:
>>
>>>
>>>
>>> сб, 11 мая 2024 г., 01:39 Phyllis Smith via Cin <
>>> c
g
> which was:
> sample_1280x720_surfing_with_audio.mjpeg
>
> On Fri, May 10, 2024 at 4:47 PM Andrew Randrianasulu <
> randrianas...@gmail.com> wrote:
>
>>
>>
>> сб, 11 мая 2024 г., 01:39 Phyllis Smith via Cin <
>> cin@lists.cinelerra-gg.org>:
>>
wrote:
>
>
> сб, 11 мая 2024 г., 01:39 Phyllis Smith via Cin <
> cin@lists.cinelerra-gg.org>:
>
>> Because Andrea had a compile problem and Andrew found an update to
>> mjpegtools from 2.1.0 to 2.2.1 that seemed to solve the problem, I have
>> been testin
Because Andrea had a compile problem and Andrew found an update to
mjpegtools from 2.1.0 to 2.2.1 that seemed to solve the problem, I have
been testing this.
Questions for Andrew concerning the patches in 2.1.0 to be moved to 2.2.1:
??? patch 1,2,3 are no longer relevant because patch1 cpuinfo.sh
Well to me it is a good introduction because if you read this, you can
start rendering without having to read anymore. I will wait to see if
anyone else comments (and as usual, I might change the wording a little
which Andrea does not seem to object to). Thank you.
On Fri, May 10, 2024 at 8:49
As far as I know, the goal is for the new released AppImages to work on
other computers that have VAAPI and VDPAU hardware graphics capabilities
even if at different levels of the operating system than the computer where
the AppImage was created.
But so far, I have not been able to either get a
Thanks for the info. I will check to see if upgrading mjpegtools on older
computers creates any problems (hopefully today).
On Fri, May 10, 2024 at 8:06 AM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:
> With the new mjpegtools 2.2.1 the compile happens without errors.
> Thanks
Andrew,
Unfortunately, the setenv for LIBVA_DRIVERS_PATH in main.C used in an
AppImage does not solve the problem of being able to use the Hardware
Vaapi/Vdpau capability of the computer CinGG is executed on. I am assuming
that this was the goal? Here is what I tested:
1. Compiled CinGG with
Attached is the patch which you apply when in the cinelerra subdirectory.
The patch is not complete yet because of accommodation for 32-bit and I
really have to test more too.
If the patch does not work for you, just edit cinelerra/main.C and add the
line:
>
> Your way seems to be working correctly but I will have to do better
> experiments tomorrow using various computers/hardware setup to make sure.
> Lots more tests to do. Below is how I added line to main.C.
>
batch_path[0] = 0;
deamon_path[0] = 0;
Units::init();
This is what I tried, but it made no difference. Is there some other way
for me to try?
1) in creating the AppImage, I ran the following 2 lines. The 2nd line is
the usual.
export
"LIBVA_DRIVERS_PATH=/usr/lib/dri:/usr/lib64/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib/aarch64-linux-gnu/dri"
It is worth a try. I will try that tomorrow.
On Mon, May 6, 2024, 18:06 Andrew Randrianasulu
wrote:
>
> https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/ce5096a51ce1f9009ba98c339894aaceb79fc5ef
>
> see, they set
>
>
>
There is another ffmpeg 7.0 AppImage available for testing 64 bit of newer
O/S (based on Fedora 39 and libva 2.20 which should work on any newest
distro):
https://cinelerra-gg.org/download/testing/cin-x86_64_newer.AppImage
Older O/S still here (based on Ubuntu 16):
Andre, just 1 little issue in the "Shortcuts" section. I have changed the
following:
Ci sono le istruzioni su dove scarircare l'appimage oppure fare una
> compilazione in proprio con la patch presente nei sorgenti.
>
to be instead:
There are instructions on where to download the appimage or how
Andrea has graciously added a new color wheel image + explanation to help
precisely describe the image for Chroma Key HSV. It can be temporarily
viewed since it is not part of the Manual yet by keying in:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Updated_Chroma_key_HSV.html
and then
Does anyone else have a reproducible crash when rendering using AV1 AOM
encode? as reported here:
https://www.cinelerra-gg.org/bugtracker/view.php?id=655
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Good, I will check this into GIT the next time I boot the desktop. Thank
you.
On Wed, May 1, 2024 at 2:38 AM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:
> I changed the description present in the av1_svt.webm preset. The
> previous one referred to the av1.webm codec.
> --
> Cin
Since this thread's subject is "small changes in Manual", I have made some
small changes also to Introduction.tex and AUTHORS.tex which you can see in
the Manual's GIT for clarification purposes.
Although I wish the Manual could be perfect and include everything
possible, that is not practical or
Andrea, thank you for locating these improvements. My commentary below is
not meant to be too picky, just suggestions that you can ignore. If you
agree with my suggestions, no need to resend Plugins.tex because I will
just make the changes accordingly. These are the result of my doing "Check
that
>
> may be use "index.htm" ?
>
In looking for the easy out I was hoping "index.htm" without the "l" on the
end would work but of course it did not. I always wondered why I saw some
URLs only have the first 3 letters, htm, working and now I know - it was a
good history lesson for today.
So I took
Thanks for the help and suggestion, I changed it to cin-index.html and it
seems to work which I will report to the Mailing List.
On Fri, Apr 26, 2024 at 9:34 PM Georgy Salnikov
wrote:
> On Fri, 26 Apr 2024, Phyllis Smith via Cin wrote:
>
> > Correction -- I need to find a w
Correction -- I need to find a way to change lowercase "index.html" to
another name. Can not change uppercase "Index.html" to another name
because it is used by Context Help (I have to verify that I said this
correctly now).
On Fri, Apr 26, 2024 at 5:05 PM Phyllis Smith
wrote:
> Trying to open
> Trying to open the html manual directly from the website, I no longer get
> to the
> cover and context menu,
>
...
> This has been happening for a couple of weeks.
>
This is fixed so IgorBeg's workaround is no longer needed. It was my
mistake for removing "index.html" so as to not conflict
Also worked well for me so checked into GIT. Thanks you Andrew.
On Mon, Apr 22, 2024 at 5:14 AM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:
> Yes, I also remember the noisy audio. I don't remember the details
> well. However, with your patch everything is OK, even with flac
>
>
--
Checked aging plugins improvements to source GIT.
On Mon, Apr 22, 2024 at 2:03 AM Andrea paz
wrote:
> AgingTv seems to work fine for me. The settings are maintained.
>
...
> 1- Grain is too pronounced. In my opinion there should be a slider for
> "Grain" as well so that it can be modulated.
>
IgorBeg, in Preferences/Settings/Playback A what is the audio set to? The
default on a new startup seems to be Alsa, default, 16 bit linear.
Unfortunately I have no speakers on my Ubuntu 16 O/S, but when I download
this new AppImage and load a ffmpeg 7.0 audio filter on my laptop, it works
for
cond patch mods againg.C so processing for pits/dust happens only if
> param > 0 (not sure if such change desirable?)
>
> On Thu, Feb 29, 2024 at 10:08 AM Andrew Randrianasulu <
> randrianas...@gmail.com> wrote:
>
>>
>>
>> ср, 28 февр. 2024 г., 20
On Sat, Apr 20, 2024 at 2:48 PM Андрей Спицын via Cin <
cin@lists.cinelerra-gg.org> wrote:
> After reading the mail list, I thought that some test cases are needed to
> test plugins after migrating from ffmpeg 6.1 to 7.0. And then compare the
> new videos with the old ones in semi-automatic
A new AppImage with ffmpeg 7.0 AND Dissolve fade problem patch (test media
attached; untar; load unwanted_black_flashxml) in is at:
https://cinelerra-gg.org/download/testing/cin-x86_64_older.AppImage
black_flash.tar
Description: Unix tar archive
--
Cin mailing list
Maybe I am wrong, but it does not seem to be any different to me. I tested
on Fedora and Ubuntu 16. Attached is a tar file containing
unwanted_black_flash.xml that can be untarred to /tmp and then the xml file
loaded into CinGG.
But I have created an Ubuntu 16 AppImage with the dissolve mod and
Late today in turning on computer, but have applied this latest 0003 patch
also and there does not seem to be any issue with it.
But I have to say that without knowing how to use the audio plugins much,
even when I changed values for some parameters on some of the F_ audio
plugins, I could not
Success, I think as there are no errors and it is doing something normal
but have not compared to ffmpeg 6.1 yet.. Still need more tests and Andrea
to try.
I had a hard time telling if several plugins were making a difference until
I tried F_volume and set the volume range to 10. Definitely got
Sorry for the late reply - I had to reboot to check. I added the first 12
F_ audio plugins, turned them all off, and then checked by turning them
each on one by one. All had the same error. (I will leave the computer on
for another hour if you want me to try something else).
But Andrea should
Andrew, sorry but no change for me - still same errors. At first I only
recompiled pluginfclient.C but since it did not work, I did a full build.
Still failed. Also, verified that the patch was actually applied just in
case I made a mistake. I have settings Alsa / HD-Audio Generic #0 / 16
bit
IgorBeg, like Andrea said that is much better and if you want to share,
that would be appreciated.
On Thu, Apr 18, 2024 at 1:26 AM Igor BEGHETTO via Cin <
cin@lists.cinelerra-gg.org> wrote:
> I have done a photomontage for the Chromakey_HSV. I add here two PNGs:
> the original and my
Very good - thank you both as I know this is quite tedious work. I have
updated the Manual GIT with these changes.
Just FYI - I could not find anamorphotic as a legitimate word (as in
non-anamorphotic). But we just made it one!! and it makes sense. ...Phyllis
On Wed, Apr 17, 2024 at 8:02 AM
Checked in change to GIT. I am glad Andrew and others read a lot and can
keep up on these notes found in other forums!
On Mon, Apr 15, 2024 at 6:56 AM Andrew Randrianasulu via Cin <
cin@lists.cinelerra-gg.org> wrote:
> it was reported that without libxml-parser-perl in
> blds/bld_prepare.sh
There is an AppImage on the server with FFmpeg 7.0 included in the build if
anyone wants to test. It should work on just about any 64-bit O/S but Help
is not included (nor alternative shortcuts).
https://cinelerra-gg.org/download/testing/cin-x86_64_older.AppImage
Also, checked into source
Andrea, thank you for this list. Results are a little strange. I have a
local modified version of ffmpeg/plugin.opts to comment out aap and fsync
which were giving errors on a fresh startup with ffmpeg 7.0. Also
commented out tiltandshift which as you noted gives an error message -- but
does
Glad they and you reported this. I will add tomorrow (hopefully).
On Mon, Apr 15, 2024 at 6:56 AM Andrew Randrianasulu via Cin <
cin@lists.cinelerra-gg.org> wrote:
> it was reported that without libxml-parser-perl in
> blds/bld_prepare.sh {debian section} Debian bookworm build does not work
>
I fixed it - no reason not to since it was discovered by Georgy and since
Andrey pointed it as a potential problem on
fat32 on Windows XP. Thank you both. ...Phyllis
On Sun, Apr 14, 2024 at 1:09 AM Georgy Salnikov via Cin <
cin@lists.cinelerra-gg.org> wrote:
> I accidentally found, that in the
First test looks good. Applied patch on top of other patches and did a
full build. Created a DVD and played on TV. I am still trying to
determine if it sounds a little different or my ears are just tired. Will
do more tests. Thank you.
>> Sorry, still stuck with this mysteriously
But why? there must be some setting conflict as the user should not have to
start out with a fresh configuration to be able to use the Alpha Offset. I
will play around to see if I can understand why.
Also, later I will create an AppImage with ffmpeg 7.0 in it in case others
want to test.
Andrea, I can verify that moving Alpha Slider in ChromakeyHSV seems to have
no effect in build with ffmpeg 7.0 . And for me it has no effect with the
Feb. Appimage (ffmpeg 6.1) or even June 2020 binary. Will attempt to go
back further to check more.
On Fri, Apr 12, 2024 at 1:07 AM Andrea paz
More tests recording on the TV have been done and the TV channels scanned
in just fine, but I need to go further in the testing.
I am concerned that Andrea on his latest Arch install, is not able to BD
render a video just taking all of the defaults. If he has time, could he
check the "Output
Commented it out in common/packages.tex, ran latex build (not up to date
install like Andrea), and checked into GIT so not lost. Thank you both
...Phyllis
On Mon, Apr 8, 2024 at 11:04 AM Андрей Спицын via Cin <
cin@lists.cinelerra-gg.org> wrote:
>
> I think that it should be commented out for
Compiling and running just 1 test with the patches Andrew has supplied so
far previously, on Ubuntu 16 and Debian 32-bit (9.1) is working.
Hopefully, Andrea will continue to run with ffmpeg 7.0 so that he might
notice more problems yet since he always has the most up to date Arch
distro installed.
Tried a longer .ts file with 6 audio channels on bluray (default and no
variations) - still no problem yet but will keep testing. Attaching
ffmpeg-7.0.patch4 and ffmpeg-7.0.patchD here -- have no idea if patch4 is
correct BUT patchD should be OK and I will test later.
On Sun, Apr 7, 2024 at 12:34
Andrea, oops, I guess I had better try another video as BD Render did not
crash for me, but I always use the same small file with only 2 channels.
Your terminal output looks correct though! More testing !! Phyllis
On Sun, Apr 7, 2024 at 12:28 PM Andrea paz
wrote:
> Compilation with all the
Default, with no variations having been tested, *Bluray creation works and
plays* on Samsung and LG TV connected devices just fine. This is after I
patched with 0005-Fix-audio-encoding-with-ffmpeg-7.0.patch and I had added
the attached patch to thirdparty/src/ffmpeg-7.0.patch3 (which I re-created
OK, thanks Andrew.
Creating blurays with what patches I had yesterday did not work, but am
testing with the latest patches today so I am behind.
On Sun, Apr 7, 2024 at 10:57 AM Andrew Randrianasulu <
randrianas...@gmail.com> wrote:
>
>
> вс, 7 апр. 2024 г., 19:12 Phyllis Smith :
>
>> I attached
I attached ffmpeg-7.0.patch0, but maybe we do not need anymore?? Andrew??
> Ah, even if most patches apart from 3, 4 and D still apply encoding is
>> busted :/
>> I have tried three encodings and they work normally (h265-Hi;
>> DNxHR-HQX and AV1.svt).
>>
>
>
ffmpeg-7.0.patch0
Description:
Our ChromaKey is broken as demoed in previous emails with GG-BLUR.tar.bz2.
I was trying to incorporate some changes in the version 8 (in GitHub) of HV
but failed to just get it to work. But hopefully Andrew will figure it
out.
P.S. We lost power here due to high winds, so have not completed
This is going to be fun for me today! on different distros hopefully.
Thanks and that was fast.
On Sat, Apr 6, 2024 at 4:24 AM Andrew Randrianasulu
wrote:
>
>
> сб, 6 апр. 2024 г., 01:16 Andrew Randrianasulu :
>
>> so I was using this patch as guidance
>>
>>
>>
Before we used this, Bill and I did some research to make sure there was no
copyright issue and even read the Lady's statement about it. She was not
all concerned and only people who are older even know where it came from. I
personally have never seen any of it except what is shown. It is a
Blue Banana is a complicated "work of art"! Since I have found a typo in
the Manual in the Blue Banana plugin section, I will add Beghetto's
summary of how alpha works as he stated below. Thanks too from me for the
illustrative video.
On Mon, Apr 1, 2024 at 3:59 AM Igor BEGHETTO via Cin <
It looks like they are back on schedule. But looks like we need to worry
about breakage but we will see what happens.
> - *a C11-compliant compiler is now required; note that this requirement*
> * will be bumped to C17 in the near future, so consider updating your*
> * build environment if it
This is quite surprising - I would never have expected that, but then the
videos there are very useful.
A quick note to say that CinGG's Youtube channel has reached 500 subscribers
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Updated the Manual and checked into GIT, this Tip section after reviewing,
testing the steps, and minor punctuation changes. I apologize if I do not
put the entire "Credits" personnel into the git line, but Andrea adds all
of the Latex to get it to format correctly and saves me from having to do
More searching on the internet leads to the following conclusion.
Changing aspect ratio - the reality seems to be "you cannot do that". You
either need to crop or distort. Instead I "think" you will have to add
borders to two of the sides.
On Sun, Mar 3, 2024 at 6:40 AM Rob Prowel via Cin <
Oops, previous email will distort it. But there must be a way to do this?
On Sun, Mar 3, 2024 at 6:40 AM Rob Prowel via Cin <
cin@lists.cinelerra-gg.org> wrote:
> I have 3:2 content that is saved in a 4:3 frame with black bands at the
> top and bottom.
>
> I want to remove the banding such that
The only way I have tested to do this will cut off the right and left sides
some and I do not know a way around that. IgorBeg may have a better
solution. My example had no content on the sides:
https://streamable.com/1a5osk
1) load your 4:3 video with the bands
2) drag the "Crop & Position"
Thank you Andrew and Andrey.
> The cpupower utility can be used to set minimum and maximum cpu
> frequencies and frequency scaling governor. I use it on my intel and amd
> laptops. With some governor you can't set frequencies, try to change them.
> I hope this helps.
>
Yes, this helped - laptop
Oh, that is a very good idea for me to try tomorrow when I do my next build
-- that is when it gets really hot. I do not care if it is slower but at
least then I can work on other things while doing a build. THANKS.
On Fri, Mar 1, 2024 at 5:16 PM Andrew Randrianasulu
wrote:
> My laptop was
We have a new release of AppImages for February 29th with only very minor
changes but was necessary to fix Color 3 Way plugin since that is often
used. There are also Manual changes and the excellent Anamorphic.pdf file
that Andrea created -- this was hours and hours of work with much reviewing
(ometimes I just can not stop myself and just had to look at AgingTV.) I
think I found the problem. If everything is unchecked and then one of the
3 items of Scratch, Pits, or Dust is checked BUT set to zero, you can still
see that item in the compositor. Grain is either on or off and works as
>
> some strangeness with AgingTV gui params (they not as interactive as they
>>> should?) but I have't looking at this problem yet.
>>>
>>
>> ... I only wanted to note this somewhere so hopefully *I* will have some
> added motivation to look at it! Well, at least in very "shake a toy and
> see
>
> Not even sure if it makes sense to do release this month? On the other
>> hand not even sure if we will able to fix more than one problem in next 30
>> days ...
>>
> I would bring out a new appimage because DeJay needed the appimage with
> Color 3 Way working...
Yes, I was planning on making
As to "why" you have to do a Reset, I think it must have something to do
with having been saved the way it was. Because I ran with a blank
configuration (CIN_CONFIG=/tmp/bcast1 ./bin/cin), loaded the sample .xml
file, deleted the Chromakey plugin on the timeline (because we already
agreed it has
IgorBeg, we always count on you when it comes to plugins working right. I
agree with Andrew-R, "but why?" is mysterious.
By my test, using IgorVlad's test case, Blur plugin works as it is (I am
> using "CinGG-20240131-x86_64-older_distros.AppImage"). Just press the
> Reset button in the Blur
This quote says it all (I believe it was Einar who said this in an email
but I could be wrong):
* "There will always be more bugs!"*
What is the problem with Chroma Key (HSV)? I can't find the original
> discussion.
>
There was not much discussion, but this is the email that mentioned it and
has
So, I am only assuming that the Blur plugin works correctly in CV as I do
not have an executable that works. Since the HV version (8 and "latest
after 8 binary" running on Ubuntu 18) appears to be the same flaw as CinGG,
it must be that the CV experts fixed it at some time.
CinGG was based on HV
>
> small video describing how it worked in cinelerra-cv 1.2.1 using old
> dynebolic 1.4 iso
In checking the above, I ended up clicking on:
http://cinelerra-cv.wikidot.com/cincvdocs:docs-start
I do not comprehend what the point of providing links to obvious
documentation for Cin*GG *without
> Nice post title! :)
>
Yes, I like the post title too -- it ranks right up there with one of
Andrew's previous ones which was "SAR, DAR, PAR - oh my!"
Thanks for the link. I tried to change the text in the manual, see if
> that's okay.
>
It looks good to me. I have checked in Andrea's changes
Andrea, I did not even notice that but apparently it works just fine as is
because I re-created the pdf file and the html file with no problems. It
is the ASCII symbol for "carriage return". That is: move the print head
back to the start of line just like you would on a typewriter. Also, I did
RE: CinGG chromakey plugin with HV 8.
Thanks! But I think mentioned fixes just went in into hv git few days ago,
> so post HV 8
>
Oh, sometimes I am a bozo. I got the new version with the RGB chroma key
bug fix and will look at that.
also, previews in file loading dialog!
>>>
>>
> Well, if
Andrew, I have started comparing CinGG chromakey plugin with HV 8. For
some reason I can not translate the url from Russian to English using
Google Website translate, but it does not matter as I can compare the code
without understanding the rhetoric.
>
Andrea, after reviewing again, I have checked the 4 tex files into the
Manual GIT. I did make minor corrections because it is hard to spell
"height" correctly. Really like the "rightarrowtail" latex command in the
document that I had never seen before. Later I will upload the pdf file to
the
1 - 100 of 1350 matches
Mail list logo
