11/19/2023 0 Comments Ffmpeg powershell![]() ![]() My theory is that in the old version, whatever code combines the outputstreams normally would make sure that individual lines were preserved and interleaved instead of of cut up. I read somewhere that with PowerShell Core they've changed the default encoding to UTF-8, so perhaps it is something related to that. I am still seeing this behavior when I use the old powershell, but I have since upgraded to PowerShell Core (7.0.2), and the problem seems to be solved. Somewhere powershell is interpreting something as newlines that is not newlines. Which makes slightly more sense, but is still missing the part of the line I care about ('Music'). Sometimes with precisely the same command the output is: GENRE : Strangely, I also get indeterminate output. ffmpeg's output is colored, so maybe there are color control characters in the output that are breaking things? Or, maybe ffmpeg's output isn't playing nicely with powershell's default UTF-16? I can't figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr. I am guessing something is different in the encoding. The output includes a bunch of lines without my matching string, "GENRE": album_artist : Post Human EraĪt least one output file must be specified But when I do: ffmpeg -i file.ogg 2>&1 | sls GENRE I'm trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |