Install gstreamer with Homebrew

Project links

• Homepage

Commands and aliases

• ges-launch-1.0
• gst-device-monitor-1.0
• gst-discoverer-1.0
• gst-dots-viewer
• gst-inspect-1.0
• gst-launch-1.0
• gst-play-1.0
• gst-stats-1.0
• gst-transcoder-1.0
• gst-typefind-1.0
• gst-validate-1.0
• gst-validate-images-check-1.0
• gst-validate-launcher
• gst-validate-media-check-1.0
• gst-validate-rtsp-server-1.0
• gst-validate-transcoding-1.0
• gst-webrtc-signalling-server

Project history

The GStreamer project announced version 0.1.0 on 2001-01-10. Its own homepage describes the design as a library for constructing graphs of media-handling components, with applications ranging from simple Ogg/Vorbis playback through streaming to nonlinear editing and mixing.

A major packaging and API milestone came with GStreamer 0.10.0 on 2005-12-05, when the project announced a stable series split across core, base, good, ugly, bad, FFmpeg, and Python binding modules. That split made explicit the distribution distinction between core APIs, well-supported base plugins, good-quality plugins, plugins with legal or patent distribution concerns, and plugins needing more testing or documentation.

The 1.0 release on 2012-09-24 created a new API- and ABI-stable 1.x series. The announcement stated that 1.x was not API/ABI compatible with 0.10.x but could be installed in parallel, a detail that mattered heavily to distributions and package maintainers during the long transition.

Adoption history

GStreamer adoption spread through both applications and platform stacks. The official applications page lists media players, transcoders, streaming servers, XMPP/VoIP clients, and GNOME/GTK applications using it, including examples such as Banshee, Clementine, Empathy, Flumotion, Gajim, PiTiVi, Rhythmbox, and Totem.

The 1.4.0 stable announcement in 2014 included binaries for Android, iOS, Mac OS X, and Windows alongside the source releases, reflecting GStreamer's role beyond Linux distributions. Its documentation also covers deployment, Windows installation, plugin writing, application development, and language bindings.

How it is used

Developers use GStreamer by constructing pipelines of elements linked by pads and buffers. The command-line tools are central to everyday use: gst-launch-1.0 builds and runs simple pipelines, gst-inspect-1.0 lists plugins and element capabilities, and gst-discoverer-1.0 inspects media structure.

For package users, the installed behavior is determined by which plugin sets are present. Base plugins provide foundational elements; good plugins are broadly supported; ugly plugins may raise distribution issues; bad plugins are a staging area for code that needs more review, documentation, tests, maintainership, or usage. This is why package manifests and optional dependencies are unusually visible in GStreamer troubleshooting.

Why package nerds care

GStreamer is a classic package-nerd dependency because it turns media capability into an install graph. A missing decoder may be solved by a plugin package rather than by changing the application, and distributions make policy choices about patent-encumbered or legally sensitive plugins.

The 0.10-to-1.x transition is also packaging history: parallel installability allowed applications to migrate without forcing every dependency to cross the API boundary at once. The 1.x command names with the -1.0 suffix preserve that packaging lesson in daily shell usage.

Timeline

• 2001: GStreamer 0.1.0 was announced.
• 2005: GStreamer 0.10.0 stable series was announced with core, plugin, FFmpeg, and Python modules.
• 2012: GStreamer 1.0 introduced the API/ABI-stable 1.x series and allowed parallel installation with 0.10.x.
• 2014: GStreamer 1.4.0 announcement included Android, iOS, Mac OS X, and Windows binaries.
• 2014: The 1.2.0 announcement covered gst-python, GNonLin, and GStreamer Editing Services in the 1.x family.

Related projects

• gst-plugins-base, gst-plugins-good, gst-plugins-ugly, gst-plugins-bad, gst-libav, gst-python, GNonLin, GStreamer Editing Services, and RTSP server modules are part of the ecosystem package managers expose around the core.
• GTK and GNOME applications are common downstream users, while language bindings such as Rust and Python bindings make the same multimedia framework available outside C.

Sources

• https://gstreamer.freedesktop.org/
• https://gstreamer.freedesktop.org/apps/
• https://gstreamer.freedesktop.org/documentation/
• https://gstreamer.freedesktop.org/documentation/tools/gst-inspect.html
• https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html
• https://gstreamer.freedesktop.org/documentation/tutorials/basic/gstreamer-tools.html
• https://gstreamer.freedesktop.org/modules/
• https://gstreamer.freedesktop.org/news/