home.social

#vapoursynth — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vapoursynth, 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. After fixing two AUR `PKGBUILD` files and a bit of patching, the initial rough Arch repo is online. Even made the package list look good with some fancy indexing. The compile takes a long time, but since it's in a VM I'm not too bothered about it. I will probably make an actual build system, but for now the crontab will suffice.

    #archlinux #nginx #svtav1 #handbrake #vapoursynth

  7. After fixing two AUR `PKGBUILD` files and a bit of patching, the initial rough Arch repo is online. Even made the package list look good with some fancy indexing. The compile takes a long time, but since it's in a VM I'm not too bothered about it. I will probably make an actual build system, but for now the crontab will suffice.

    #archlinux #nginx #svtav1 #handbrake #vapoursynth

  8. After fixing two AUR `PKGBUILD` files and a bit of patching, the initial rough Arch repo is online. Even made the package list look good with some fancy indexing. The compile takes a long time, but since it's in a VM I'm not too bothered about it. I will probably make an actual build system, but for now the crontab will suffice.

    #archlinux #nginx #svtav1 #handbrake #vapoursynth

  9. After fixing two AUR `PKGBUILD` files and a bit of patching, the initial rough Arch repo is online. Even made the package list look good with some fancy indexing. The compile takes a long time, but since it's in a VM I'm not too bothered about it. I will probably make an actual build system, but for now the crontab will suffice.

    #archlinux #nginx #svtav1 #handbrake #vapoursynth

  10. After fixing two AUR `PKGBUILD` files and a bit of patching, the initial rough Arch repo is online. Even made the package list look good with some fancy indexing. The compile takes a long time, but since it's in a VM I'm not too bothered about it. I will probably make an actual build system, but for now the crontab will suffice.

    #archlinux #nginx #svtav1 #handbrake #vapoursynth

  11. However, sometimes it works out at the end. Got the repo online, still need to do a full end-to-end.

    #archlinux #repo #svtav1 #handbrake #vapoursynth

  12. However, sometimes it works out at the end. Got the repo online, still need to do a full end-to-end.

    #archlinux #repo #svtav1 #handbrake #vapoursynth

  13. However, sometimes it works out at the end. Got the repo online, still need to do a full end-to-end.

    #archlinux #repo #svtav1 #handbrake #vapoursynth

  14. However, sometimes it works out at the end. Got the repo online, still need to do a full end-to-end.

    #archlinux #repo #svtav1 #handbrake #vapoursynth

  15. However, sometimes it works out at the end. Got the repo online, still need to do a full end-to-end.

    #archlinux #repo #svtav1 #handbrake #vapoursynth

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

  17. Графические оболочки FFmpeg

    Считается, что работа в консоли эффективнее GUI по нескольким причинам. Во-первых, там быстрее набирать команды, чем двигать курсором. Во-вторых, на CPU, память и GPU не ложится лишнее бремя графической оболочки, так что любые процессы быстрее выполняются в консоли. Но есть люди, которые всегда предпочтут GUI . Они считают графический интерфейс «наиболее эффективным и удобным способом работы на десктопе». На самом деле они во многом правы, в том числе для специфических задач видеообработки важно сразу видеть результат. FFmpeg — изначально консольная утилита. Но её популярность крайне высока. Поэтому появляются всё новые варианты графических оболочек для FFmpeg, чтобы доступ к инструменту получили абсолютно все пользователи.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #ffmpeg #графические_оболочки #GUI #транскодинг #многопоточность #чистый_код #Антон_Кирнов #FFmpeg_61 #VapourSynth #Staxrip #LosslessCut #Shotcut #KDEnlive #H264 #HEVC #AV1 #ffmpegwasm