some cleanups, adding ffmpeg script from mail archive
Using old thread https://lists.cinelerra-gg.org/pipermail/cin/2019-May/000671.html I added vaapi proxying script to our doc/ directory (really not fan of retyping scripts from manual ...) and removed near-empty "whats new" from 2.1 era and removed few 'sav' backup copies from tree and moved old 1.1.0 release notes and TODOs from svn era into new old/ directory. see if you like those changes, apply accordingly!
I think there is an easy solution to the below, but I am not sure what it is? After reading Andrea's email as referencing vaapi/proxy/ffmpeg speed up from the original thread as Andrew pointed out below, I see a problem that I do not understand how to make workable. I was starting to make an update to the manual about having vaapi_proxy.sh in the doc directory for user usage when I got confused. On Thu, Nov 3, 2022 at 7:49 AM Andrew Randrianasulu <[email protected]> wrote:
Using old thread
https://lists.cinelerra-gg.org/pipermail/cin/2019-May/000671.html
I added vaapi proxying script to our doc/ directory (really not fan of retyping scripts from manual ...)
Andrea Paz's reply below:
I made a build with the 2 patches of "configure.ac" + the other 4 patches ("cleanups"). I have no errors. I have not tried the proxy.
Problem: Andrey Spitsyn vaapi speedup using ffmpeg at 30x faster is a HUGE gain, but I do not see how it can be integrated into CinGG as in his suggestion of "So I thought that cinelerra can use this script to speed up the proxy files creation." 1) of course, it would only work if user had graphics board with vaapi capable acceleration but there are users who do; 2) but the real problem is if you run this script outside of CinGG, then how does Cinelerra work with this proxy file and switch back and forth to the "real" file and in the end have the changes applicable to the real file when you edit/render it in the future? Hoping Andrea Paz pursues testing a way if someone has a hint of how to do this? Or am I just missing something?
Hi Phyllis, Andrew My script was just a proof of concept, can cinelerra use external tools for proxy file creation or not. The answer is Yes.
how does Cinelerra work with this proxy file and switch back and forth to the "real" file As I remember, the user must create a proxy file with external script, and the next step is to tell cinelerra to use proxy. It won't recreate proxy files because they already exist.
Best regards, Andrey чт, 3 нояб. 2022 г. в 20:44, Phyllis Smith via Cin < [email protected]>:
I think there is an easy solution to the below, but I am not sure what it is?
After reading Andrea's email as referencing vaapi/proxy/ffmpeg speed up from the original thread as Andrew pointed out below, I see a problem that I do not understand how to make workable. I was starting to make an update to the manual about having vaapi_proxy.sh in the doc directory for user usage when I got confused.
On Thu, Nov 3, 2022 at 7:49 AM Andrew Randrianasulu < [email protected]> wrote:
Using old thread
https://lists.cinelerra-gg.org/pipermail/cin/2019-May/000671.html
I added vaapi proxying script to our doc/ directory (really not fan of retyping scripts from manual ...)
Andrea Paz's reply below:
I made a build with the 2 patches of "configure.ac" + the other 4 patches ("cleanups"). I have no errors. I have not tried the proxy.
Problem: Andrey Spitsyn vaapi speedup using ffmpeg at 30x faster is a HUGE gain, but I do not see how it can be integrated into CinGG as in his suggestion of "So I thought that cinelerra can use this script to speed up the proxy files creation." 1) of course, it would only work if user had graphics board with vaapi capable acceleration but there are users who do; 2) but the real problem is if you run this script outside of CinGG, then how does Cinelerra work with this proxy file and switch back and forth to the "real" file and in the end have the changes applicable to the real file when you edit/render it in the future?
Hoping Andrea Paz pursues testing a way if someone has a hint of how to do this? Or am I just missing something?
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
OK, thanks Andrey -- I should have been able to figure out usage myself but usually I forget more than I remember. Script has been checked into GIT and explanation has been added to the manual. Some day some one will come along and modify the source code to include this directly. On Thu, Nov 3, 2022 at 4:09 PM Андрей Спицын via Cin < [email protected]> wrote
My script was just a proof of concept, can cinelerra use external tools for proxy file creation or not. The answer is Yes.
how does Cinelerra work with this proxy file and switch back and forth to the "real" file As I remember, the user must create a proxy file with external script, and the next step is to tell cinelerra to use proxy. It won't recreate proxy files because they already exist.
They can all be removed as they existed in HV before the days of GIT. And that includes removing the TODO's, etc. instead of renaming, just delete. Any Objections?
and removed near-empty "whats new" from 2.1 era
and removed few 'sav' backup copies from tree
and moved old 1.1.0 release notes and TODOs from svn era into new old/ directory.
see if you like those changes, apply accordingly!
Applied to GIT the cleanup to delete 14 files to include OLD "TODO's" in cinelerra and mpegt2enc. On Thu, Nov 3, 2022 at 7:49 AM Andrew Randrianasulu <[email protected]> wrote:
Using old thread
https://lists.cinelerra-gg.org/pipermail/cin/2019-May/000671.html
I added vaapi proxying script to our doc/ directory (really not fan of retyping scripts from manual ...)
and removed near-empty "whats new" from 2.1 era
and removed few 'sav' backup copies from tree
and moved old 1.1.0 release notes and TODOs from svn era into new old/ directory.
see if you like those changes, apply accordingly!
participants (3)
-
Andrew Randrianasulu -
Phyllis Smith -
Андрей Спицын