home.social

#encoding — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #encoding, aggregated by home.social.

  1. After two weeks of wrangling, finally got the next batch of AV1 packages built for Arch into the repo. Should be back on the regular schedule of weekly releases unless something else rears its ugly head.

    - Some packages require GCC 15 and absolutely hate GCC 16
    - Zig 0.16 is not an option for a lot of stuff
    - VapourSynth API v3 C headers are no longer included with the Arch Linux package, so had to grab those from the repo and get them to the right spot

    #vapoursynth #encoding #av1 #archlinux

  2. After two weeks of wrangling, finally got the next batch of AV1 packages built for Arch into the repo. Should be back on the regular schedule of weekly releases unless something else rears its ugly head.

    - Some packages require GCC 15 and absolutely hate GCC 16
    - Zig 0.16 is not an option for a lot of stuff
    - VapourSynth API v3 C headers are no longer included with the Arch Linux package, so had to grab those from the repo and get them to the right spot

    #vapoursynth #encoding #av1 #archlinux

  3. After two weeks of wrangling, finally got the next batch of AV1 packages built for Arch into the repo. Should be back on the regular schedule of weekly releases unless something else rears its ugly head.

    - Some packages require GCC 15 and absolutely hate GCC 16
    - Zig 0.16 is not an option for a lot of stuff
    - VapourSynth API v3 C headers are no longer included with the Arch Linux package, so had to grab those from the repo and get them to the right spot

    #vapoursynth #encoding #av1 #archlinux

  4. After two weeks of wrangling, finally got the next batch of AV1 packages built for Arch into the repo. Should be back on the regular schedule of weekly releases unless something else rears its ugly head.

    - Some packages require GCC 15 and absolutely hate GCC 16
    - Zig 0.16 is not an option for a lot of stuff
    - VapourSynth API v3 C headers are no longer included with the Arch Linux package, so had to grab those from the repo and get them to the right spot

    #vapoursynth #encoding #av1 #archlinux

  5. After two weeks of wrangling, finally got the next batch of AV1 packages built for Arch into the repo. Should be back on the regular schedule of weekly releases unless something else rears its ugly head.

    - Some packages require GCC 15 and absolutely hate GCC 16
    - Zig 0.16 is not an option for a lot of stuff
    - VapourSynth API v3 C headers are no longer included with the Arch Linux package, so had to grab those from the repo and get them to the right spot

    #vapoursynth #encoding #av1 #archlinux

  6. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  7. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  8. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  9. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  10. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  11. After a ton of compiling, the v2 release is official. Containers all work, the client works, and now I'm gonna relax and watch some YouTube videos. Releases are available on the website though I still need to update the docs with the new "installation" process (much simplified).

    Releases: git.jamesthebard.net/jweatherl

    #sisyphus #encoding #programming #golang

  12. 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

  13. Lots of progress and a lots of pain. However, all of the Sisyphus modules have been implemented and I'm currently running a test across the `2.0.0b2` version. The most painful thing I fought was literally tailing a log file. Got lazy and brought in `hpcloud/tail` because it did what I needed it to, but what it _didn't_ do was work well for my application. After a day or two of battling it, I removed it and went with `bufio.NewReader`and a nice `context.CloseWith` setup and now it works every time.

    Also added a `PostRun()` call to each module just to have a place to do basic module cleanup if needed.

    Learned a ton on this one so far and while annoying at times: it's been pretty fun.

    Repo: git.jamesthebard.net/jweatherl

    #golang #sisyphus #encoding #programming

  14. C'est niche, mais je suis toujours surpris que certaines parties du monde informatique, par fatigue, n'implémentent pas encore d'éléments d'ergonomie et de reconnaissance de formes simonomi.dev/blog/color-code-y #programming #encoding #ergonomie #interface

  15. The Sisyphus client rewrite continues after a bit of a break. The `ffmpeg` module is mostly finished and should serve as a good template for `handbrake`, `av1an`, `mkvmerge`, and `cleanup` modules. Logging is progressing pretty well. The config has been expanded slightly and can now pull from TOML files on top of the standard environment variables.

    #sisyphus #encoding #ffmpeg #golang

  16. A nice afternoon running some brutal encodes across the homelab. This is initial testing of the 5fist fork of the `svt-av1-psy` encoder with some pretty severe settings. Hoping that the results are worth the wait, but gotta wait until the first few results come out of the workers.

    #sisyphus #av1 #svtAv1 #encoding

  17. 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.

    #sisyphus #encoding #av1an

  18. 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.

    #av1an #sisyphus #encoding #ffmpeg #mkvtoolnix

  19. Time to put the newly rewritten server into action. Broke out my totally stock firmware LG WH16NS60 drive, and started in on some Bluray TV episode sets. Currently ripping at ~9.2X which definitely helps out.

    Think I'm gonna target AV1 via `av1an` and use the `svt-av1-psyex` encoder. Already have the subtitles and attachments though I'll have to offset the subs by 1000ms for everything to work out.

    #video #encoding #bluray #lg #sisyphus #makemkv

  20. 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

  21. I've tested SVT-AV1 and the RX7600 AV1 hardware encoder with Unbeatable recordings and for this game specifically they look nearly the same.

    If I look at zoomed-in freeze frames, I'd even say the hardware encoder often wins by having less compression noise.

    But while playing the video, they all look same which is still wild because the hardware encoder is of course way faster.

    Maybe SVT-AV1 struggles with this game, I don't know.

    (Exact settings in a reply)

    #AV1 #SVTAV1 #Encoding

  22. Huh, look at that, you can encode #tapCode as ascii blocks

    ▓▓▓▓░░░░▓▓▓▓░░▓▓▓▓░░░░░▓▓▓░░▓▓▓░░░░░

    ▓▓░░░░▓▓▓▓░░░

    ▓▓░░░░▓▓▓░░░

    ▓▓▓▓░░░░▓▓░░░▓░░░░░

    ▓░░░░░▓▓▓░░░░░▓▓▓▓░░░▓▓▓▓░░░░▓░░░░░▓▓░░░░▓▓▓░░░

    ▓▓░▓▓░░░░▓▓▓░▓░░░░░▓▓▓▓░░░

    #knockCode #encoding #secretCommunication #wwII #usefulThings

    -wikipedia en.wikipedia.org/wiki/Tap_code

  23. So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

    For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

    Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

    I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

    Any tips? (Links to guides and tutorials are ok too)

    Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

    #ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows

  24. So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

    For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

    Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

    I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

    Any tips? (Links to guides and tutorials are ok too)

    Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

    #ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows

  25. So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

    For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

    Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

    I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

    Any tips? (Links to guides and tutorials are ok too)

    Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

    #ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows

  26. So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

    For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

    Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

    I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

    Any tips? (Links to guides and tutorials are ok too)

    Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

    #ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows

  27. So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

    For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

    Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

    I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

    Any tips? (Links to guides and tutorials are ok too)

    Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

    #ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows

  28. @doboprobodyne @christianp

    awesome!
    In the long run it might also make the online transcoding tools with the "Start now" [to download malware]-button obsolete.

    Funnily I talked about this [soon solved] problem with my funder @clemensg by phone today.

    #transcoding #encoding #video #browser #ffmpeg #webassembly #clientside #videoconverter

    just et. al. too
    please save us from uploading duplicate files or journalists from writing alt twice with clientside content-id comparison.

  29. Small thing I noticed today: splitting `.mkv` files using `ffmpeg` via the `-ss` and `-t` options works great, but the resulting `.mkv` file contains the wrong number of frames in the metadata. Evidently the total frames from the source file gets written into the metadata instead of the resulting frames post-splitting which is annoying. Not a deal breaker, but kind of annoying...easy to fix with a quick run through `mkvmerge` but still just weird.

    #matroska #ffmpeg #splitting #encoding

  30. Updated numbers for Eve-AV1 & Eve-VP9 are public! The last time they were updated was around 2019, so this should give a more relevant look at how they perform. It takes a lot to improve a mature video encoder, and I'm very impressed with the Eve lineup. I may be biased, though.

    #av1 #video #transcoding #encoding #codec #vp9

  31. Updated numbers for Eve-AV1 & Eve-VP9 are public! The last time they were updated was around 2019, so this should give a more relevant look at how they perform. It takes a lot to improve a mature video encoder, and I'm very impressed with the Eve lineup. I may be biased, though.

    #av1 #video #transcoding #encoding #codec #vp9

  32. Updated numbers for Eve-AV1 & Eve-VP9 are public! The last time they were updated was around 2019, so this should give a more relevant look at how they perform. It takes a lot to improve a mature video encoder, and I'm very impressed with the Eve lineup. I may be biased, though.

    #av1 #video #transcoding #encoding #codec #vp9

  33. Updated numbers for Eve-AV1 & Eve-VP9 are public! The last time they were updated was around 2019, so this should give a more relevant look at how they perform. It takes a lot to improve a mature video encoder, and I'm very impressed with the Eve lineup. I may be biased, though.

    #av1 #video #transcoding #encoding #codec #vp9