New release AppImages with all having x265 10/12 bit encode
There are new AppImages at: https://cinelerra-gg.org/download/images/ All of the important changes are incorporated for fc38, suse15, debian11/12, and ubuntu22 at: https://github.com/einhander/cin-gg-packages/releases/tag/20240718 *Andrey*.could you check 20240728 / 20240729 for the ubuntu22 build? Just FYI, because of the time difference 2 of the last GIT change (trivial changes) were done on the 28 of July and the other 2 on the 29 of July (after midnight). ************* Release Notes ***************** *GIT for Cinelerra-GG has the following changes from 07/01/2024-07/31/2024* *Picons for Chromakey Avid and Color Swatch* plugins added to be seen in the Resources window under Video Effects provided by *IgorBeg*. *Chromakey Avid help* with Alt-h when running CinGG has been corrected by *SGE*. Since this affects doc/Context_Manual.pl, anyone who has customized this will have to refer to ~HOME/.bcast5 .bak file to reincorporate their specific changes. *Multibit x265* is now the default build for all appimages which only affects encode for x265 so that now the 10-bit and 12-bit x265 render formats will work. The 8-bit render format (h265.mp4) and other h265 formats that exist should continue to work as before. So there will no longer be a separate AppImage, CinGG_yymmdd-x86_64-multibit.AppImage. If doing your own build and for some reason you prefer not to build with 10 and 12 bit x265, delete thirdparty/src/x265*.patch* before compiling and modify thirdparty/Makefile as described in the Manual. As a side note, you may have to rebuild your video index the first time you use the 10/12 bit render formats, but only if you encounter an error message. Much information and testing was provided by *Terje and Andrea*. *Performance tips from Stefan* have been added to the manual: - when working with multiple tracks containing video at opacity 100%, if you just want to play one track, disable "Play track" in the patchbay for the other tracks. This uses a lot less CPU. - for playing a track that has attached Video Effects you can decrease CPU usage considerably if you temporarily disable the Video Effects. *Manual updates by Andrea* include a number of improvements, additions, and changes.
Thank you Phyllis, the ubuntu build is almost ready, and will be uploaded soon. It builds successfully, but fails to upload to github. Best regards, Andrey ср, 31 июл. 2024 г., 21:45 Phyllis Smith via Cin <[email protected]
:
There are new AppImages at: https://cinelerra-gg.org/download/images/ All of the important changes are incorporated for fc38, suse15, debian11/12, and ubuntu22 at: https://github.com/einhander/cin-gg-packages/releases/tag/20240718
*Andrey*.could you check 20240728 / 20240729 for the ubuntu22 build? Just FYI, because of the time difference 2 of the last GIT change (trivial changes) were done on the 28 of July and the other 2 on the 29 of July (after midnight).
************* Release Notes ***************** *GIT for Cinelerra-GG has the following changes from 07/01/2024-07/31/2024*
*Picons for Chromakey Avid and Color Swatch* plugins added to be seen in the Resources window under Video Effects provided by *IgorBeg*.
*Chromakey Avid help* with Alt-h when running CinGG has been corrected by *SGE*. Since this affects doc/Context_Manual.pl, anyone who has customized this will have to refer to ~HOME/.bcast5 .bak file to reincorporate their specific changes.
*Multibit x265* is now the default build for all appimages which only affects encode for x265 so that now the 10-bit and 12-bit x265 render formats will work. The 8-bit render format (h265.mp4) and other h265 formats that exist should continue to work as before. So there will no longer be a separate AppImage, CinGG_yymmdd-x86_64-multibit.AppImage. If doing your own build and for some reason you prefer not to build with 10 and 12 bit x265, delete thirdparty/src/x265*.patch* before compiling and modify thirdparty/Makefile as described in the Manual. As a side note, you may have to rebuild your video index the first time you use the 10/12 bit render formats, but only if you encounter an error message. Much information and testing was provided by *Terje and Andrea*.
*Performance tips from Stefan* have been added to the manual: - when working with multiple tracks containing video at opacity 100%, if you just want to play one track, disable "Play track" in the patchbay for the other tracks. This uses a lot less CPU. - for playing a track that has attached Video Effects you can decrease CPU usage considerably if you temporarily disable the Video Effects. *Manual updates by Andrea* include a number of improvements, additions, and changes. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Thanks for the new AppImage! I was wondering,... can We use the word "Avid" in a plugin or other part of the software? Avid is a trademark. One possible alternative could be "divA"? (as for DivX and XviD) IgorBeg Il 31/07/2024 20:44, Phyllis Smith via Cin ha scritto:
There are new AppImages at: https://cinelerra-gg.org/download/images/ All of the important changes are incorporated for fc38, suse15, debian11/12, and ubuntu22 at: https://github.com/einhander/cin-gg-packages/releases/tag/20240718
************* Release Notes ***************** _GIT for Cinelerra-GG has the following changes from 07/01/2024-07/31/2024_
*Picons for Chromakey Avid and Color Swatch* plugins added to be seen in the Resources window under Video Effects.
*Chromakey Avid help* with Alt-h when running CinGG has been corrected by *SGE*. Since this affects doc/Context_Manual.pl, anyone who has customized this will have to refer to ~HOME/.bcast5 .bak file to reincorporate their specific changes. **
I was wondering,... can We use the word "Avid" in a plugin or other part of the software? Avid is a trademark.
It probably could have been named ChromakeySpectramatte which is too
long. But naming it ChromakeyAvid as one word should be OK? I do not know for sure. Alternatively, we can just replace ChromakeyHSV with ChromakeyAvid which then breaks old projects AND new projects who started to use it as ChromkeyAvid. *quote from the internet: Spectramatte* is a fairly decent keyer but is showing it's age, as *Avid* haven't really updated it since it was introduced over a decade ago.
Might it be enough to write in the Manual on the ChromaKey (Avid) Video Effect, inside its footnotes, the sentence: "Avid is a trademark by Avid Technology, Inc."? Or something similar? I don't know. Il 05/08/2024 19:21, Phyllis Smith ha scritto:
I was wondering,... can We use the word "Avid" in a plugin or other part of the software? Avid is a trademark.
It probably could have been named ChromakeySpectramatte which is too long. But naming it ChromakeyAvid as one word should be OK? I do not know for sure. Alternatively, we can just replace ChromakeyHSV with ChromakeyAvid which then breaks old projects AND new projects who started to use it as ChromkeyAvid. // /quote from the internet: Spectramatte/ is a fairly decent keyer but is showing it's age, as /Avid/ haven't really updated it since it was introduced over a decade ago.
participants (3)
-
Igor BEGHETTO -
Phyllis Smith -
Андрей Спицын