In other words, when you seek frames, those will be stored in the GPU memory and the motion compensation calculations will occur in the GPU and the results will then be passed through to the CPU for the rest of the encoding. This will trigger the opencl implementation of x264 through the hardware accelerated lookahead. The right option to put there is: opencl=true or simply opencl. I noticed that you were trying to insert stuff into the custom x264 params well those are reserved to the x264 parameters while you were trying to put the ffmpeg commands there. This is generally done automatically for you by the filter_builder.a3x, but the encoding nodes don't support any kind of proprietary GPU Encoder like NVEnc or in your case the AMD Enc, however there's an exception: H.264. On the other hand, as emcodem said, you would have to deal with every transformation yourself, so it would be your job to deal with frame rate conversion, resizing, colormatrix and primaries conversion etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |