Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • I think you need to edit and show the ffmpeg command you are using. Based on a quick Google of the error, you might be passing the wrong thing to one of the parameters perhaos, but that's based on only the error log top part and kind of guessing. I got something related to incompatible fps rates too, but another guess only too. Commented Oct 28, 2022 at 23:34
  • Line added above.
    – LouF
    Commented Oct 29, 2022 at 5:39
  • "Error log top part": Yes, I began trying to solving this at superuser.com/q/1749943/1734749 I'm not sure if it's the command launch or PS error output handling.
    – LouF
    Commented Oct 29, 2022 at 5:50
  • I would try to work it out using start-process and play with the -RedirectStandardOutput or -RedirectStandardError parameters. So for example in PowerShell run Start-Process "C:\Users\User\Documents\Computer\FfMPEG\bin\ffmpeg.exe" -ArgumentList '-loglevel error -hide_banner -nostats -y -itsoffset 0.2 -i $videofile.Name -i $videofile.Name -map 0:0 -map 1:1 -vf yadif -c:v:0 libx264 -ar 44100 -scodec copy $newmp4filename' -RedirectStandardError "C:\Users\User\Documents\Computer\FfMPEG\ffreport.txt" Commented Oct 29, 2022 at 12:55
  • Also, I like working out PowerShell logic in PowerShell_ISE.exe and then once I get the kinks ironed out there, I then move it over to Powershell.exe executing as a script, etc. Commented Oct 29, 2022 at 14:19