repository·master·Indexed 20 days ago
https://github.com/asticode/go-astiavA Go library providing idiomatic C bindings for FFmpeg version n8.0. It features typed constants, standard error patterns, and struct-based functions to improve developer experience over older bindings. The library includes Go implementations of official FFmpeg examples and provides utilities for memory management (Alloc, Unref, Free), audio buffering via AudioFifo, and bitstream filter processing through BitStreamFilterContext.
astiav is a Golang library providing C bindings for FFmpeg. It is specifically designed to be compatible with FFmpeg n8.0.
Key features include:
Warning: Breaking changes may be introduced without following the v2 Go module pattern. Check BREAKING_CHANGES.md for details.
When working with FFmpeg objects like packets or frames, you must manage memory carefully to avoid leaks or use-after-free errors.
General Pattern:
Alloc(): Use this to allocate an object once, often outside of loops, to allow for reuse.defer .Free(): Always ensure the allocated object is freed when it is no longer needed by the application..Unref(): Inside loops where an object (like a packet) is being populated by a method like ReadFrame(), you must call .Unref() to release the internal data 'injected' by the FFmpeg C function. Using a closure inside the loop is a recommended way to handle this with defer.// You can allocate the packet once and reuse the same object in the for loop below
pkt := astiav.AllocPacket()
// However, once you're done using the packet, you need to make sure to free it
defer pkt.Free()
// Loop
for {
// We'll use a closure to ease unreferencing the packet
func() {
// Read frame using the same packet every time
formatContext.ReadFrame(pkt)
// However make sure to unreference the packet once you're done with what
// have been "injected" by the .ReadFrame() method
defer pkt.Unref()
// Here you can do whatever you feel like with your packet
}()
}HardwareFrameContext was renamed to HardwareFramesContext.Building on Windows requires the msys2 / mingw64 gcc toolchain.
Note: For pkg-config, it is recommended to use pkgconfiglite from Chocolatey (choco). Ensure CGO and PKG_CONFIG environment variables are set to point to your FFmpeg build folder.
# Update Packages
pacman -Syu
# Install Requirements to Build
pacman -S --noconfirm --needed git diffutils mingw-w64-x86_64-toolchain pkg-config make nasm
# Clone the repository using git
git clone https://github.com/asticode/go-astiav
cd go-astiavTo ensure your Go code automatically picks up the FFmpeg dependency during compilation, you must set the following environment variables. Replace {{ path to your ffmpeg directory }} with the absolute path to your FFmpeg installation directory.
export CGO_CFLAGS="-I{{ path to your ffmpeg directory }}/include/",
export CGO_LDFLAGS="-L{{ path to your ffmpeg directory }}/lib/",
export PKG_CONFIG_PATH="{{ path to your ffmpeg directory }}/lib/pkgconfig",The examples/ directory contains Go implementations that mirror the official FFmpeg C examples. Use these to understand specific workflows:
examples/bit_stream_filtering/main.goexamples/custom_io_demuxing/main.goexamples/custom_io_muxing/main.goexamples/demuxing_decoding/main.goexamples/filtering/main.goexamples/frame_data_manipulation/main.goexamples/hardware_decoding_filtering/main.goexamples/hardware_encoding/main.goexamples/remuxing/main.goexamples/resampling_audio/main.goexamples/scaling_video/main.goexamples/transcoding/main.goTip: You can use the video samples in the testdata directory for your own tests.
NewIOInterrupter, you must ensure that the IOInterrupter.Free method is called after use to prevent resource leaks.Frame.KeyFrame and Frame.SetKeyFrame were removed. To manage keyframe status, use the Flags and SetFlags methods instead.Several API renames and replacements occurred in version 0.25.0:
CodecParameters.CodecType and CodecParameters.SetCodecType were removed. Use CodecParameters.MediaType and CodecParameters.SetMediaType instead.HardwareFrameContext.SetPixelFormat was replaced by HardwareFrameContext.SetHardwarePixelFormat.FormatContext.SetInterruptCallback was replaced by FormatContext.SetIOInterrupter.The generic NewFilterContext has been removed. When working with filter graphs, you must now use specific buffer sink or source contexts:
FilterGraph.NewBuffersinkFilterContext or FilterGraph.NewBuffersrcFilterContext.BuffersinkFilterContext.GetFrame to retrieve frames.args parameter was removed from the constructor. Instead, after calling NewBuffersrcFilterContext, you must call BuffersrcFilterContext.SetParameters followed by BuffersrcFilterContext.Initialize. Use BuffersrcFilterContext.AddFrame to provide frames.FilterInOut.SetFilterContext, use the .FilterContext field from the respective buffer context.In version 0.40.0, the fields used to query supported formats on a Codec have been renamed for clarity. Replace the old names with the new Supported prefix:
Codec.ChannelLayouts $\rightarrow$ Codec.SupportedChannelLayoutsCodec.PixelFormats $\rightarrow$ Codec.SupportedPixelFormatsCodec.SampleFormats $\rightarrow$ Codec.SupportedSampleFormatsFilterLink was removed. Instead of using links, use methods directly on the buffer contexts, such as BuffersinkFilterContext.ChannelLayout.