

But your commands will still have to point to the correct folders and files. This will allow you to run ffmpeg commands from any working folder displayed in cmd.

In addition to your typo fixes, I strongly recommend mapping a system path to your ffmpeg bin. The other way is to map the folder in the system paths, so that you can be in any working folder to use the executable. That would be the cd command that changes the working folder. One way is by navigating to the correct folder in cmd before you run the commands. When you call up another executable in cmd, you have tell Windows where to find it. To be fair, this isn't actually anything to do with ffmpeg.
