#av1an — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #av1an, aggregated by home.social.
-
The long test is looking good for the `av1an`, `mkvmerge`, and `cleanup` modules, the Golang client is doing exactly what its supposed to which is a welcome change from yesterday. I need to do long tests on the `ffmpeg` and `handbrake` modules next, but I'll handle those tomorrow.
After that, I'll update documentation, release the `2.0.0` client, and deprecate the old client.
#sisyphus #av1an #ffmpeg #matroska #encoding #programming #golang
-
Oh yeah, things are working as intended now. Unfortunately, I did crank the settings so these encodes are going to take about an hour each. However, the homelab seems to be up to the challenge.
-
After breaking out `strace` and just a ton of other stuff I finally figured out what was going on. A single encoder option was invalid which caused the workers to crash before even writing the file in the data directory. Fixing the setting cleared up the issue and made everything happy.
What caused this rabbithole initially was `av1an` eating itself when trying to put the video and audio stuff together at the end of an encode. Unfortunately the `audio.mkv` file it was trying to mux into the container kept causing `mkvmerge` to fail because the audio file was empty. _This_ was caused by bad audio encoder options being passed to `ffmpeg`.
I made sure I documented both of these and I'm currently running test videos before calling it 100% good.
-
I think this might be the most frustrating thing I've dealt with: the `av1an` encoder not being able to create files in the client container. Definitely has free space, the user is running in the container as `root` (also does the this as a regular user) but absolutely refuses to run.
The mystery continues.
-
So, got the server in place but discovered that the Docker image that I created that has the Sisyphus client and all of the binaries like `ffmpeg`, `av1an` was not very happy. Ffmpeg crashed because it couldn't find the `libSvtAvcEnc.so.4` library which was because I had a custom version of it installed (`svt-av1-psyex`).
Got the Dockerfile fixed by installing `svt-av1-psyex` and then compiling `ffmpeg` against those libraries, then installing both `svt-av1-psyex` and `ffmpeg` into the final container which makes `ffmpeg` happy. Also saw an issue where the Vapoursynth `lsmash` module wasn't being found, but that got tracked down to a stale Docker image (forgot to pull the latest from the repo).
I have two encodes going: one `ffmpeg` and one `av1an` which should be the real final test. If they turn out well, attachments where they're supposed to be, etc., etc. then I'll probably start working on documentation and get this out there.
#sisyphus #encoding #av1an #vapoursynth #ffmpeg #svtAv1Psyex
-
Having trouble with my container, seems like it's using the incorrect version of the `SvtAv1EncApp` which is really annoying. Went ahead and just slammed the `psyex` version into `/usr/bin` and now everything is happy.