Re: [Cin] CinGG/NLE comparison

[Andrea paz via Cin]

If you intend to use Sketcher plugin to animate something written with
the Title plugin or imported from Inkscape, etc; no, it is not
possible.
Sketcher is only for drawing lines on the canvas, with which to
compose figures that can then be translated, rotated and resized, and
finally animated with keyframes. See to the minutes 23:56
https://www.youtube.com/watch?v=SBt9rkg7i8E
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Still on hardware acceleration

[Andrea paz via Cin]

Thanks for the links, very interesting talks from AMD developers and
ffmpeg. Unfortunately for video AMD is far behind Nvidia and now
Intel. Mpv I've already managed to get it working with Vulkan and so
far I haven't had any problems (apart from the "noise" of the GPU
fans)
I also see little difference between vaapi decoder and "none".
Sometimes you can see a small advantage though.
For Vulkan, I guess I will wait for ffmpeg 6.1, hoping the bug will be fixed.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] CinGG/NLE comparison

[Stefan de Konink via Cin]

On Tuesday, September 5, 2023 1:53:42 PM CEST, Andrea paz wrote:

If you intend to use Sketcher plugin to animate something written with
the Title plugin or imported from Inkscape, etc; no, it is not
possible.
Sketcher is only for drawing lines on the canvas, with which to
compose figures that can then be translated, rotated and resized, and
finally animated with keyframes. See to the minutes 23:56
https://www.youtube.com/watch?v=SBt9rkg7i8E


So basically you could do lower two thirds, but you would be forced to use 
keyframes, for which the current 'edit' interfaces in Cinelerra is poor. 
Hence it is possible to see which properties may change but not editing 
this easily. I don't mean a rather complex node based editor as I have seen 
in a video on Resolve or swimming lanes editor like Blender.


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

Re: [Cin] CinGG/NLE comparison

[Phyllis Smith via Cin]

Andrea, this is really nice and so well formatted.  Have not read it all
yet and want to do so more thoroughly. And  I am still going through the
Manual to see if there are other hints in there that could be added.

On Tue, Sep 5, 2023 at 1:58 AM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:

> I attach the pdf and odt file to put in the git repository. It is the
> union of my and Phyllis' writings. It is for new users to compare the
> workflow they are used to with the one in CinGG. I created the
> document in odt because it is a work-in-progress that everyone can
> contribute to. I am not familiar with Adobe Premiere Pro or other
> NLEs, so I may have written inaccuracies and errors. If you can revise
> and improve the document, please do me a favor.
> --
> 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] Mirror plugin

[Igor BEGHETTO via Cin]

Thanks to you!


Il 01/09/2023 23:55, Phyllis Smith ha scritto:
Thank you.  I have tested it and checked into GIT (I was in a hurry 
yesterday when I checked it in before I started the builds and so did 
not review it beforehand).


On Fri, Sep 1, 2023 at 6:55 AM Andrea paz > wrote:


@Phyllis Smith
Some corrections for the manual. Thanks to IgorBeg.


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

Re: [Cin] Monthly AppImage updates

[Igor BEGHETTO via Cin]

Thanks to ALL of You for the Great job You do!

IgorBeg


Il 31/08/2023 22:26, Phyllis Smith via Cin ha scritto:
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 below.

**
*Mirror* is a new user contributed new video plugin and has been 
documented in the Manual.
*Gain *audio plugin has been improved to include the text box for 
precise designation of the gain and the clear/reset button to revert 
to the default. This was a user contribution.


_Andrew contributions include:_
The *About* in the Settings→Preferences now shows the Copyright to 
include the Cinelerra-GG team, the previous Cinelerra-CV team, as well 
as the libav version. This is also shown in the startup window if 
using that.
*Debian 12* required a single change to bld_prepare.sh to remove 
python2 requirement. In addition, debian-testing and ubuntu-testing 
have now been switched to the default of debian and ubuntu with their 
older operating systems now being named as debian-older and ubuntu-older.
*Modifications* in the thirdparty Makefile and fileexr, filepng, 
filetga, filetiff to ensure that builds continue to work in various 
distros, like Arch and Slackware.

*Patches *to accommodate ffmpeg 6.0 and 4.4 for certain distros.

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

Re: [Cin] CinGG/NLE comparison

[Stefan de Konink via Cin]

Thanks for the document.

Question: I noticed the Sketcher plugin. Can this do animation? For example 
a lower two thirds title animation?


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

Re: [Cin] Still on hardware acceleration

[Andrew Randrianasulu via Cin]

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 on I am
> only referring to decoding/playback!) you can use the "-hwaccel"
> option without any other settings.

As far as I understand those options parsed in ffmpeg command line
tool itself, so using library from c/c++ requires some  similar manual
work 


 If the media file used supports
> hardware acceleration, then it will be used automatically without
> anything else to do. If it is not supported it will automatically
> switch to software decoding. There is no need to specify the device
> (because a device is automatically selected, even if it is not the
> preferred one), so it would be a generic feature that decides for
> itself when to run.
> Question, how can I impose "-hwaccel" when compiling CinGG?
>
> Another thing concerns decoding with Vulkan. Again, these are generic
> instructions and I would like to test it, however it requires device
> initialization, to be declared explicitly (although a generic term is
> fine: "vulkan=vk:0") and a few other options. See here:
> https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan
> The question is always the same: How can I compile vulkan in CinGG to
> do some tests?

There is possibility that current ffmpeg.git broken with latest
released vulkan headers, see ffpeg-user list..

In 5.1/6.0 you will get in best case just some  filters, _may be_ amd
specific (and not open source?) encoder.
Vulkan work in future 6.1 aims just more unified (win/mac/lin may be
android) video interface ... instead of libva/ dxva11 /  videotoolbox
on each platform, as far as I understand.

https://github.com/mpv-player/mpv/issues/11739

http://ffmpeg.org/pipermail/ffmpeg-user/2023-September/056774.html

May be there will be some benefits  in driving hw blocks  this way,
not sure (there was  talk mesa's va encoder implementation not most
speedy one)

But to your question just go to thirdparty/makefile and look for long
ffmpeg command line (without-ffplay etc), just remove --disable-vulkan
from there
.

Or try to compile cingg without thirdparty ffmpeg.


> --
> 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] Still on hardware acceleration

[Andrew Randrianasulu via Cin]

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:
> > https://trac.ffmpeg.org/wiki/HWAccelIntro
> > it is my understanding that when decoding (note: from here on I am
> > only referring to decoding/playback!) you can use the "-hwaccel"
> > option without any other settings.
>
> As far as I understand those options parsed in ffmpeg command line
> tool itself, so using library from c/c++ requires some  similar manual
> work 
>
>
>  If the media file used supports
> > hardware acceleration, then it will be used automatically without
> > anything else to do. If it is not supported it will automatically
> > switch to software decoding. There is no need to specify the device
> > (because a device is automatically selected, even if it is not the
> > preferred one), so it would be a generic feature that decides for
> > itself when to run.
> > Question, how can I impose "-hwaccel" when compiling CinGG?
> >
> > Another thing concerns decoding with Vulkan. Again, these are generic
> > instructions and I would like to test it, however it requires device
> > initialization, to be declared explicitly (although a generic term is
> > fine: "vulkan=vk:0") and a few other options. See here:
> > https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan
> > The question is always the same: How can I compile vulkan in CinGG to
> > do some tests?
>
> There is possibility that current ffmpeg.git broken with latest
> released vulkan headers, see ffpeg-user list..
>
> In 5.1/6.0 you will get in best case just some  filters, _may be_ amd
> specific (and not open source?) encoder.
> Vulkan work in future 6.1 aims just more unified (win/mac/lin may be
> android) video interface ... instead of libva/ dxva11 /  videotoolbox
> on each platform, as far as I understand.


AMF  stuff:

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/348



>
> https://github.com/mpv-player/mpv/issues/11739
>
> http://ffmpeg.org/pipermail/ffmpeg-user/2023-September/056774.html
>
> May be there will be some benefits  in driving hw blocks  this way,
> not sure (there was  talk mesa's va encoder implementation not most
> speedy one)
>
> But to your question just go to thirdparty/makefile and look for long
> ffmpeg command line (without-ffplay etc), just remove --disable-vulkan
> from there
> .
>
> Or try to compile cingg without thirdparty ffmpeg.
>
>
> > --
> > 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] Still on hardware acceleration

[Andrea paz via Cin]

@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 on I am
only referring to decoding/playback!) you can use the "-hwaccel"
option without any other settings. If the media file used supports
hardware acceleration, then it will be used automatically without
anything else to do. If it is not supported it will automatically
switch to software decoding. There is no need to specify the device
(because a device is automatically selected, even if it is not the
preferred one), so it would be a generic feature that decides for
itself when to run.
Question, how can I impose "-hwaccel" when compiling CinGG?

Another thing concerns decoding with Vulkan. Again, these are generic
instructions and I would like to test it, however it requires device
initialization, to be declared explicitly (although a generic term is
fine: "vulkan=vk:0") and a few other options. See here:
https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan
The question is always the same: How can I compile vulkan in CinGG to
do some tests?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin