If you need specific advice (for example, medical, legal, financial or risk management), please seek a professional who is licensed or knowledgeable in that area. - Please note: Wiki How does not give you opinion about the law, or advice about medical.- Some articles may contain names, images, artworks or descriptions of events that some cultures restrict access to.- A few of these subjects are frequently censored by educational, governmental, corporate, parental and other filtering schemes.Wiki How does not encourage the violation of any laws, and cannot be responsible for any violations of such laws, should you link to this domain, or use, reproduce, or republish the information contained herein. Text is available under the Creative Commons Attribution-Share Alike License additional terms may apply.

Process = subprocess.Popen(args, stdin=None, stdout=subprocess.⚠️ Disclaimer: Content from Wiki How English language website. You don’t have to use ffmpeg-python, just do something like this: args = [ My solution is to spawn a separate thread that consumes stderr see if you reinstall via pip install git+ I think your problem should go away if not please let me know. Ideally we would send stderr to /dev/null, but ffmpeg-python doesn’t expose this very well. Another thing we can do is just show the output of stderr, but I’d like to avoid this if possible. The typical way around this is to use municate, but I want to avoid reading all of stdout and stderr at once since a lot of data can get written to stdout in this case. Since there’s nobody reading stderr, maybe that’s why it is hanging. Probably ffmpeg is getting chatty on stderr (as it sometimes does) about 60% of the way through processing.

this suggests to me that maybe on Win7 (or maybe just for your video), the stderr pipe is filling up.

Install ffmpeg windows 7