CODEWITHSUNDEEP
powershellcommand-linesyntax
user310291
user310291

Reputation: 38190

What's the equivalent of cmd for powershell with ffmpeg

from https://www.poftut.com/ffmpeg-command-tutorial-examples-video-audio/

ffmpeg -i jellyfish-3-mbps-hd-h264.mkv

works in cmd but same on Powershell gives

Unexpected token '-i' in expression or statement.

what's then the right syntax ?

Upvotes: 1

Views: 871

Answers (1)

mklement0
mklement0

Reputation: 438198

As currently shown in your question, the command would work just fine in PowerShell.

# OK - executable name isn't quoted.
ffmpeg -i jellyfish-3-mbps-hd-h264.mkv

However, if you quote the executable path, the problem surfaces.

# FAILS, due to SYNTAX ERROR, because the path is (double)-quoted.
PS> "C:\Program Files\ffmpeg\bin\ffmpeg" -i jellyfish-3-mbps-hd-h264.mkv
Unexpected token '-i' in expression or statement.

For syntactic reasons, PowerShell requires &, the call operator, to invoke executables whose paths are quoted and/or contain variable references or subexpressions.

# OK - use of &, the call operator, required because of the quoted path.
& "C:\Program Files\ffmpeg\bin\ffmpeg" -i jellyfish-3-mbps-hd-h264.mkv

Or, via an environment variable:

# OK - use of &, the call operator, required because of the variable reference.
# (Double-quoting is optional in this case.)
& $env:ProgramFiles\ffmpeg\bin\ffmpeg -i jellyfish-3-mbps-hd-h264.mkv

If you don't want to have to think about when & is actually required, you can simply always use it.

The syntactic need for & stems from PowerShell having two fundamental parsing modes and is explained in detail in this answer.

Upvotes: 2

Related Questions