Well sure always back up everything but this command will create new .opus files still leaving the original .m4a in the folder too, so even if it errors just delete the bad .opus files and try to resolve your ffmpeg codec issue before retrying the conversion or trying another method. Ffmpeg in my experience always converts with the “makes a new file with your file(s)” method, I’ve never had it do the “change the file destructively” method.
If you’re on linux try navigating to the folder in the terminal and running
for i in *.m4a; do ffmpeg -i "$i" "${i%.*}.opus"; donebefore doing anything like that… back up the folder.
Well sure always back up everything but this command will create new .opus files still leaving the original .m4a in the folder too, so even if it errors just delete the bad .opus files and try to resolve your ffmpeg codec issue before retrying the conversion or trying another method. Ffmpeg in my experience always converts with the “makes a new file with your file(s)” method, I’ve never had it do the “change the file destructively” method.
It’ll also error out or prompt to overwrite an existing file unless a flag is passed that tells it to overwrite unattended.
Sure, but if it errors out no harm no foul, and don’t pass any flags to overwrite the input file which I had not included above.
While I’m thinking about it, what is that flag? Because afaik ffmpeg can’t overwrite and convert the file simultaneously, you have to use a temp file.
That’s the point: you have to go out of your way to accidentally overwrite your input files with ffmpeg.
And no it indeed can’t output to the same file as input.