-
Notifications
You must be signed in to change notification settings - Fork 3
ffmpeg hangs on muxing #6
Comments
v1.6 is cursed... Due its being the first project it has alot of issues / bad code... It will take a few days until I will make the first Release. |
It's all good man. We all start somewhere. I wasn't a good programmer until after I graduated college and worked on some open source projects. I just don't have a C# development environment on my own system (and don't want one). But yea, we all start somewhere, and life is about getting better. Even the code I write now that I'm a 'better' programmer is still a process of cranking something out that works, then spending several weeks or months hammering out issues I don't like or bugs that I find/are found. Bugs aren't a mark of shame, they're a fact of life. The people who claim to code without bugs just hide them from their git commits. :p Or code very, very, slowly. |
Hello AlkL58! |
Hello j-mas, |
In my experience, the reference coder aom is the best quality encoder. Closely followed by SVT-AV1 and then Rav1e. |
Adding SVT-AV1 is on my To-Do list. It will work differently, because SVT-AV1 doesn't Support piping with ffmpeg for the time being. |
I prefer aomenc! |
Just to confirm: I have v1.6 and use the SVT-AV1 encoder and it (sometimes) also hangs when muxing for me. Pretty annoying, but checking 'Resume' and then starting the encode again will make it succeed immediately. |
@darkcharmander NEE is not developed anymore. Please check out: https://github.com/Alkl58/NotEnoughAV1Encodes |
@Alkl58 I see that I posted it in the wrong place indeed. Pretty stupid since I actually did use the NotEnoughAV1Codecs tool. I'll post in there then. Thanks! |
In v1.6 ffmpeg hangs on muxing due to an extra newline character at the end of 'myfiles.txt'. Or at least, I assume that's the reason based on my limited ability to debug and reproduce the issue on my system.
The text was updated successfully, but these errors were encountered: