В сообщении от Saturday 01 June 2019 01:04:02 Phyllis Smith написал(а): > The new builds are now available with this mod in. We do not actually test > them all but did Leap 15.1.
Ah, this was fast. Just in case I still uploaded my Debain 9 (x86-64) single-user build to https://cloud.mail.ru/public/2SM5/2x3DPD4sU look for xz file. sha256sum was updated. I think I'll just keep this VM around, but if regular builds now include Debian9/10 - there is no need for duplicating official efforts? > > https://www.cinelerra-gg.org/download/pkgs/debian9/cin_5.1.debian9-20190531_amd64.deb > > On Fri, May 31, 2019 at 2:43 PM Андрей Спицын <[email protected]> > wrote: > > > > > Thank you very much. This would be be very helpful. Can you provide me > > debian 9 amd64 package for testing please. > > > > пт, 31 мая 2019 г., 5:28 Phyllis Smith <[email protected]>: > > > >> @Spitsyn.andrey: concerning your previous message as provided below the > >> asterisks (***). A change to the Shell Commands has been checked into GIT > >> that I believe should get you what you can use when you use the "Add" > >> option after going to: Settings->Preferences->Interface->Shell Commands. I > >> have not documented how to use it yet but I am pretty sure you will > >> understand how to use it as I barely do. Be sure when doing the Add to > >> check the box "run /path/script.sh + argv" to run that script. I believe > >> this is all you have to do to get this working: > >> > >> 1) put your script as you described earlier below anywhere on your system > >> that will not be deleted > >> 2) set up you Shell Command as described in the CinelerraGG_manual.pdf > >> basically do an Add, type in the line /{your directory > >> path}/your_script_file.sh and check the "run" box > >> 3) click all OKs to get back to Cinelerra > >> 4) NOW to execute your script from inside Cinelerra, assuming you have > >> loaded your video files/assets, highlight the 1 file in the Resources > >> Window that you want to proxy using your script, then use the Shell Cmds > >> icon to find the Add that you did and click on it. I would suggest you > >> look at the output on the window from where you started up Cinelerra to > >> make sure it is working or your script could include an output log file. > >> > >> You can also use $1, $2, ... more args in your script and then highlight > >> multiple files. > >> Let me know if this works for you or what the problem is if it does not. > >> Thank you as this was a good addition for us. gg/Phyllis > >> > >> ************************************************************************************************* > >> > >> On Wed, May 15, 2019 at 1:22 AM Спицын Андрей <[email protected]> > >> wrote: > >> > >>> >@GG My hardware is little bit outdated so I already using script for a > >>> >proxy files creation. I've spend some time to find appropriate options > >>> for > >>> >ffmpeg to use fully hardware encoding/filtering. It has very good > >>> results > >>> >compared to cinelerra proxy routine (about 30x faster) and cinelerra > >>> using > >>> >ffmpeg's hardware filter and vaapi encoder (around 10x faster). > >>> >So I thought that cinelerra can use this script to speed up the proxy > >>> files > >>> >creation. > >>> > >>> Here the script file: > >>> > >>> #!/bin/bash > >>> > >>> filename="$1" > >>> fileout="${filename%.*}" > >>> proxy="6" > >>> # Hardware encode AMD > >>> ffmpeg -threads 2 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i > >>> "$1" -c:v h264_vaapi -vf > >>> "format=nv12,hwupload,scale_vaapi=iw/'$proxy':ih/'$proxy'" -vcodec > >>> h264_vaapi -preset fast -c:a copy -bf 0 -profile:v 66 > >>> "$fileout".proxy"$proxy"-mp4.mp4 > >>> > >>> -- > >> Cin mailing list > >> [email protected] > >> https://lists.cinelerra-gg.org/mailman/listinfo/cin > >> > > -- > > Cin mailing list > > [email protected] > > https://lists.cinelerra-gg.org/mailman/listinfo/cin > > > -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
