On Sat 5 Mar 2022 at 14:04, Rukmangadh Sai Myana <rukmangadh....@nobroker.in> wrote:
> > In general, I mistrust wrapper libraries for things like this- I'd rather > > create the full command string myself and execute that; it gives much > better > > control over the process. > > Thank you for this suggestion. The issue was that ffmpeg was sending the > above logs, which don't correspond to any error to STDERR. The python > wrapper was interpreting this as an error. I changed the python wrapper > based code to one where I invoke ffmpeg directly as a command. This removed > the error :D Yup, doing a subprocess call rather than a wrapper has always worked better for me. Best, Kieran > > > Rukmangadh Sai Myana > +91 8106275207 > Associate Data Scientist | NoBroker.com > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
