[Cin] HEVC hw encoding on AMD Polaris cards

Phyllis Smith phylsmith2017 at gmail.com
Fri May 31 04:27:15 CEST 2019


@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 Спицын Андрей <spitsyn.andrey at gmail.com>
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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20190530/c9f13080/attachment.html>


More information about the Cin mailing list