intel-vaapi-driver
FFmpeg
intel-vaapi-driver | FFmpeg | |
---|---|---|
9 | 486 | |
301 | 42,788 | |
1.3% | 2.5% | |
1.5 | 10.0 | |
15 days ago | 6 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
intel-vaapi-driver
- Fedora 37 drops VA-API accelerated hardware video decoding support
-
How to enable Hardware Acceleration for Intel drivers?
I wasn't convinced, so I dug through some Github issues until I found this one h624 support for GM45 - issue #544, in which someone mentioned that the crocus driver supports VAAPI but several people mentioned that it seems like h264 decoding doesn't work.
-
libva breaks stuff on debian 11
i965-va-driver is dead and no longer maintained by Intel. Version 2.4.1 is the last release of that driver (see https://github.com/intel/intel-vaapi-driver/releases).
-
Hardware accelerated video garbled on Wayland but not X11 (Videos/Totem app)
$ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.14.0) vainfo: Driver version: Intel i965 driver for Intel(R) Ivybridge Desktop - 2.4.1 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD Installed Packages Name : libva-intel-driver Version : 2.4.1 Release : 8.fc36 Architecture : x86_64 Size : 7.9 M Source : libva-intel-driver-2.4.1-8.fc36.src.rpm Repository : @System From repo : rpmfusion-free Summary : HW video decode support for Intel integrated graphics URL : https://github.com/intel/intel-vaapi-driver License : MIT and EPL Description : HW video decode support for Intel integrated graphics. : https://01.org/intel-media-for-linux Installed Packages Name : ffmpeg Version : 5.0.1 Release : 3.fc36 Architecture : x86_64 Size : 2.1 M Source : ffmpeg-5.0.1-3.fc36.src.rpm Repository : @System From repo : rpmfusion-free Summary : Digital VCR and streaming server URL : http://ffmpeg.org/ License : GPLv3+ Description : FFmpeg is a complete and free Internet live audio and video : broadcasting solution for Linux/Unix. It also includes a digital : VCR. It can encode in real time in many formats including MPEG1 audio : and video, MPEG4, h263, ac3, asf, avi, real, mjpeg, and flash.
-
/dev/dri/renderd128 missing
Mesa crocus
-
Firefox Fedora don't utilize the HW acceleration
libva-intel-driver didn't work for me, but installing intel-media-driver from nonfree rpm-fusion seemed to do the trick. leaving this here for anyone with the same issue.
-
How to get HW acceleration working?
And I have already complied and install tar ball from https://github.com/intel/intel-vaapi-driver. So, libva-driver-intel is trying to install this right?
-
Zypper - again .. Does not respect "--from"?
In general, Vaapi stuff is really hard to get running. Theres a bunch of different drivers per vendor and different (package-)names for the same thing in different distros, most tutorials dont even mention the GPU theyre using and point to other drivers .. Its a mess really. For example if you google Intel Vaapi the first result is: https://github.com/intel/intel-vaapi-driver. Which is the wrong one. Of course if would be to comfortable for them to mention the supported models in their readme. I have an Intel RKL GPU so I need intel-media-driver, found that out through trial and error.
- Is Hardware Acceleration on Browser is exist?
FFmpeg
-
Creando Subtítulos Automáticos para Vídeos con Python, Faster-Whisper, FFmpeg, Streamlit, Pillow
FFmpeg (https://ffmpeg.org/)
-
Show HN: CompressX, my FFmpeg wrapper for macOS, made $9k in the last 4 months
GPL2
Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?
IANAL, apologies if I miss understand license requirements.
https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file
- Microsoft offered FFmpeg one-time payment instead of support contract
-
Writing x86 SIMD using x86inc.asm (2017)
This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...
The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.
If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.
I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".
-
Video Generation with Python
You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.
- I want some logically difficult c programs
- Looking for a good file converter for upload testing
- Best Way to Rip Rare DVDs?
-
11 Ways to Optimize Your Website
There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.
-
AI-assisted removal of filler words from video recordings
To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.
What are some alternatives?
Flatseal - Manage Flatpak permissions
mpv - 🎥 Command line video player
mesa
ffmpeg-python - Python bindings for FFmpeg - with complex filtering support
OpenH264 - Open Source H.264 Codec
fedy - Fedy makes it easy to install third-party software in Fedora.
Exoplayer - An extensible media player for Android
mesa-git-extension
hlsdl - C program to download VoD HLS (.m3u8) files
GStreamer - GStreamer open-source multimedia framework
jcodec - JCodec main repo