![]() Move this option before the file it belongs to". ![]() Unfortunately returns this error: "Encoding: Option b:v (video bitrate (please use -b:v)) cannot be applied to input url iconSmall30.png - you are trying to apply an input option to an output file or vice versa. ![]() Run from a command prompt with all of the assets in the same directory:įfmpeg.exe -i TestSD16x9.mov -i iconSmall30.png -filter_complex "crop=720:576:0:608, scale=1024:576, setsar=1 yadif,scale=-2:576 overlay=main_w-overlay_w-30:main_h-overlay_h-15 drawtext=fontfile=OpenSans-Regular.ttf:\timecode='00\:00\:00\:00': r=25:x=(w-tw)/2: y=10: fontsize=45:fontcolor=white:borderw=1:bordercolor=DarkGray" -c:v libx264 -aspect 16:9 -crf 22 -maxrate 1404k -bufsize 3000k -pix_fmt yuv420p -profile:v high -level 4.0 -refs 3 -r 25 -c:a aac -b:a 128k -ar 48000 -ac 2 -movflags faststart -threads 0 -map 0:a? -metadata:s:a:1 language=eng -y D:\Proxies_OUT\Test_proxy_16x9.mp4 ![]() My working ffmpeg test script (Watermark, Timecode, Correct Font etc OK). I've made a little progress on this, but I'm still having trouble loading the correct font with FFASTrans. > encapsulation quotes check, and also a clue to check if ffmpeg can find Win10 installed fonts. The ouput will be in the same folder with the same base name as the original source by utilizing the "%s_original_path%" and "%s_original_name%" variables. This command will execute FFAStrans own ffmpeg executable and use the input delivered to the "Command executor"-node as the source. %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%". #FFMPEG CRF MAXRATE CODE#> 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |