See pkg.go.dev references for documentation and examples.
Please make sure that you have followed the official gstreamer installation instructions before attempting to use the bindings or file an issue.
For building applications with this library you need the following:
cgo: You must setCGO_ENABLED=1in your environment when building.gccandpkg-config- GStreamer development files (the method for obtaining these will differ depending on your OS)
- The core
gstpackage utilizes GStreamer core - Subpackages (e.g.
app,video) will require development files from their corresponding GStreamer packages- Look at
pkg_config.goin the imported package to see which C libraries are needed.
- Look at
- The core
(also see #64)
Compiling on Windows may require some more dancing around than on macOS or Linux. First, make sure you have mingw and pkgconfig installed (links are for the Chocolatey packages). Next, go to the GStreamer downloads page and download the latest "development installer" for your MinGW architecture. When running your applications on another Windows system, they will need to have the "runtime" installed as well.
Finally, to compile the application you'll have to manually set your PKG_CONFIG_PATH to where you installed the GStreamer development files.
For example, if you installed GStreamer to C:\gstreamer:
PS> $env:PKG_CONFIG_PATH='C:\gstreamer\1.0\mingw_x86_64\lib\pkgconfig'
PS> go build .For more information, take a look at this comment with a good run down of the process from compilation to execution.
For more examples see the examples folder here.
// This is the same as the `launch` example. See the godoc and other examples for more
// in-depth usage of the bindings.
package main
import (
"fmt"
"os"
"strings"
"github.com/go-gst/go-glib/glib"
"github.com/go-gst/go-gst/gst"
)
func main() {
// This example expects a simple `gst-launch-1.0` string as arguments
if len(os.Args) == 1 {
fmt.Println("Pipeline string cannot be empty")
os.Exit(1)
}
// Initialize GStreamer with the arguments passed to the program. Gstreamer
// and the bindings will automatically pop off any handled arguments leaving
// nothing but a pipeline string (unless other invalid args are present).
gst.Init(&os.Args)
// Create a main loop. This is only required when utilizing signals via the bindings.
// In this example, the AddWatch on the pipeline bus requires iterating on the main loop.
mainLoop := glib.NewMainLoop(glib.MainContextDefault(), false)
// Build a pipeline string from the cli arguments
pipelineString := strings.Join(os.Args[1:], " ")
/// Let GStreamer create a pipeline from the parsed launch syntax on the cli.
pipeline, err := gst.NewPipelineFromString(pipelineString)
if err != nil {
fmt.Println(err)
os.Exit(2)
}
// Add a message handler to the pipeline bus, printing interesting information to the console.
pipeline.GetPipelineBus().AddWatch(func(msg *gst.Message) bool {
switch msg.Type() {
case gst.MessageEOS: // When end-of-stream is received flush the pipeling and stop the main loop
pipeline.BlockSetState(gst.StateNull)
mainLoop.Quit()
case gst.MessageError: // Error messages are always fatal
err := msg.ParseError()
fmt.Println("ERROR:", err.Error())
if debug := err.DebugString(); debug != "" {
fmt.Println("DEBUG:", debug)
}
mainLoop.Quit()
default:
// All messages implement a Stringer. However, this is
// typically an expensive thing to do and should be avoided.
fmt.Println(msg)
}
return true
})
// Start the pipeline
pipeline.SetState(gst.StatePlaying)
// Block and iterate on the main loop
mainLoop.Run()
}If you find any issues with the bindings or spot areas where things can be improved, feel free to open a PR or start an Issue. Here are a couple of the things on my radar already that I'd be happy to accept help with:
-
Compilation times are insanely slow when working within the bindings. This could be alleviated by further separating aspects of Gstreamer core into their own packages, or removing bindings that would see no use in Go.
-
There are a lot of quirks that make generators difficult to deal with for these bindings. That being said, I'd still like to find a way to start migrating some of them into generated code.
-
The bindings are not structured in a way to make version matching with GStreamer easy. Basically, you need a version compatible with what the bindings were written with (>=1.16).
-
More examples would be nice.
-
Support for writing GStreamer plugins via the bindings is still a work-in-progress. At the very least I need to write more plugings to find more holes.
- SWIG could be used to fix the need for global interfaces to be matched to C callbacks (most notably the
URIHandlercurrently). The limitation present at the moment is URIHandlers can only be implemented ONCE per plugin.
- SWIG could be used to fix the need for global interfaces to be matched to C callbacks (most notably the
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent