Differences

This shows you the differences between two versions of the page.

--- processors:encoder_custom_ffmpeg [2020/11/16 19:08] – external edit 127.0.0.1
+++ processors:encoder_custom_ffmpeg [2022/11/15 07:21] (current) – emcodem
@@ Line 1: / Line 1: @@
 ===== Custom FFmpeg Encoder =====
+{{:processors:custom_ffmpeg_enc.png?nolink&130|}}
 ==== Purpose ====
 Customized encoding using FFMpeg.
+==== How it works ====
+It is very similar to using a commandline processor for calling ffmpeg but it automatically inserts everything up to "-i" and the output filename in the executed ffmpeg commandline.
+Usually we engineer ffmpeg commandline processing in a windows cmd.exe box. The final result of such an experiment leads for example to this commandline:
+<code>C:\ffmpeg\ffmpeg.exe -i "C:\test\myfile.mp4" -codec copy -map 0 "C:\temp\myoutput.mp4"</code>
+In order to automate this commandline, we could now use either a commandline processor in ffastrans, we just need to change it to something like this:
+<code>"%s_ffmpeg%" -i "%s_source%" -codec copy -map 0 "%s_source%_transcoded.mp4"</code>
+Also, if the job goes on with the transcoded file, in the commandline processor we would check the "set s_source" to: "%s_source%_transcoded.mp4"
+Now, in a Custom ffmpeg processor, we would insert only this portion (and check that the codec text inputs are empty):
+<code>-codec copy -map 0</code>
+Custom ffmpeg processor would automatically insert before -codec:
+<code>"%s_ffmpeg%" -i "%s_source%"</code>
+and after -map 0 it would insert some output filename that goes into the current working directory of the FFAStrans job.
+Also, it would automatically take care that the variable s_source is filled with the generated filename.
 -------------------
 ==== Original Manual ====