Roman Lebedev LebedevRI

## VAAPI-hwaccel-encode-Linux-Ffmpeg&Libav-setup.md

      
              1 file
            
          
              42 forks
            
          
              86 comments
            
          
              215 stars
            
          
                Brainiarc7
                / VAAPI-hwaccel-encode-Linux-Ffmpeg&Libav-setup.md
            
            
              Last active
              March 26, 2024 18:18
            
              
                This gist contains instructions on setting up FFmpeg and Libav to use VAAPI-based hardware accelerated encoding (on supported platforms) for H.264 (and H.265 on supported hardware) video formats. 
              
          
    Using VAAPI's hardware accelerated video encoding on Linux with Intel's hardware on FFmpeg and libav

Hello, brethren :-)
As it turns out, the current version of FFmpeg (version 3.1 released
earlier today) and libav (master branch) supports full H.264 and HEVC encode in VAAPI on
supported hardware that works reliably well to be termed
"production-ready".

  
## 0-github-actions.md

      
              2 files
            
          
              85 forks
            
          
              60 comments
            
          
              600 stars
            
          
                domenic
                / 0-github-actions.md
            
            
              Last active
              April 8, 2024 23:35
            
              
                Auto-deploying built products to gh-pages with Travis
              
          
    Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.
A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.