Open theasdfguy555 opened 7 months ago
turn on ffmpeg logging to see exactly what is happening.
it is hard to find (or build) an ffmpeg binary for windows that doesn't fail. in my case it was something related to font loading for text rendering overlay not liking paths that contained :
like C:\whatever.ttf
My system has 32 copies of ffmpeg on it (lol) from various software and many of them didn't work. I even compiled a build myself but must have missed something, because it also failed. The version that worked for me was from an app called stemroller. I have an old version, 2.0.1
For now, I am running WSL Debian and it just works with the apt version of ffmpeg
EDIT: looks like stemroller installs from https://www.gyan.dev/ffmpeg/builds/ffmpeg-release-essentials.zip
Good luck
Did you find any solution for this?, have same error myself.
Hey, so I was having a lot of issues with getting the Docker version of DizqueTV to recognize it's own FFMPEG binary (kept exiting with code 1), so I decided to run it natively on Windows so I could know exactly where FFMPEG.exe was.
All seemed well and good until FFMPEG exited with 4294967274. This is a dump of the entire log. While the only thing I think is relevant is the exit code, I could be mistaken. I've tried the most recent builds of both the GyanDev and BtbN builds of FFMPEG. I keep looking for something I might've missed. For some reason, it also thinks Direct Play isn't available despite being run on the very same system as my server.