%comspec% /c ""%s_ffmpeg%" -f h264 -i "%s_source%" -c:v copy -fflags genpts "%s_original_path%\%s_original_name%.mkv"" ", then you must use the "Command executor"-node to create a completely custom ffmpeg command: If you need to use options before the input "-i", like "-f h264 -i. > looks like the input variable needs to be "%s_source%" now, not "%source%".
> indeed my code no longer runs from the command prompt. Also, you must be aware one thing regarding the "Custom FFmpeg" encoder: You can NOT specify options before "-i". The first thing you need to make sure is that your ffmpeg command works from a dos command. When I set this up, I settled with the command executor for ffmpeg because I couldn't get all of the custom parameters working with a Custom FFmpeg encoder processor. I've updated the file paths, checked them, and have tried using the previous working version of ffmpeg, but I keep getting an ffmpeg error code 1. The command executor runs ffmpeg to create a h.264 proxy file with vertical blanking cropped off, burnt in timecode (custom font), watermark, audio mixdown mapping. I'm migrating to a new workstation (Win 10) with the latest version of FFAStrans (1.1.0.0), but I'm having trouble setting up the command executor that I had working on the old workstation (Win7, FFAStrans v0.9.4.0).
0 kommentar(er)
