Conversation

Notices

1. Machismo (zerglingman@freespeechextremist.com)'s status on Wednesday, 10-Jan-2024 01:26:54 JST Machismo
   why does ffmpeg put out on stderr?
   • john paul grips (grips@cawfee.club)'s status on Wednesday, 10-Jan-2024 01:43:22 JST john paul grips

     in reply to
     @Zerglingman does everything go there? maybe stdout is reserved for someting that's actual parsable output :thinkbird:
     Machismo likes this.
   • Machismo (zerglingman@freespeechextremist.com)'s status on Wednesday, 10-Jan-2024 01:43:56 JST Machismo

     in reply to

     • john paul grips
     @grips I don't know. Usually I don't try to parse its output.
     Specifically, this was ffprobe, whose default behaviour is to print information about the given track.
     The entirety of its output goes to stderr.
   • Machismo (zerglingman@freespeechextremist.com)'s status on Wednesday, 10-Jan-2024 02:13:01 JST Machismo

     in reply to

     • john paul grips
     @grips Yeah seems like ffmpeg puts EVERYTHING on stderr.
     Also for some fucking reason it's munching every second filename. I have no idea why. When I echo it it's all fine. But changing from:
     ls > files; while read file; do ...; done < files
     to:
     for file in *; do ...; done
     fixed it.
     What the fuck, bash.