raul 0.7.0 has been released. Raul (Realtime Audio Utility Library) is a lightweight C++ convenience library for realtime programming, with a bias towards audio applications. For more information, see http://drobilla.net/software/raul.
- Add several unit tests
- Use malloc'd memory for RingBuffer/SRSWQueue (instead of a new'd array)
- Fancy coloured console/logging I/O (raul/log.hpp)
- More flexible Path and better URI support
- Remove stack stuff from Array and create new ArrayStack
- Make Symbol and URI more opaque and use Glib string interning
- Add Configuration class for app command line option handling
- Use < operator in TableImpl instead of > so it needn't be defined
- Add IntrusivePtr, a trivial #define of boost::intrusive_ptr which is useful for hard realtime things (since adding and dropping refs is realtime safe, which is not true of shared_ptr)
- Remove TimeSlice
patchage 0.4.3 has been released. Patchage is a modular patch bay for Jack and ALSA based audio/MIDI systems. For more information, see http://drobilla.net/software/patchage. -- David Robillard firstname.lastname@example.org
- Switch to waf build system
- Fix compilation with GCC 4.4
- Better ALSA support
- Massive performance improvements when ALSA is enabled
- Center on startup
raul 0.6.0 has been released. Raul (Realtime Audio Utility Library) is a lightweight C++ convenience library for realtime programming, with a bias towards audio applications. For more information, see http://drobilla.net/software/raul.
- Switch to waf build system
- Fix compilation with GCC 4.4
- Add URI class and make Path a special URI (with scheme "path:")
- Remove JackDriver
- Add NullDeleter convenience for SharedPtr
- Add URI Atom type
- Add C++ style printing for Atom
- Fix type wackiness for glib atomic functions on PPC
- Remove misguided LASH stuff
- Depend on glib (instead of glibmm)
LV2 Extension Documentation
Recently there has been a lot of discussion on the linux-audio-dev list about LV2, and perceived problems thereof. Much of this was nonsense and FUD, but there is a problem with documentation of LV2 things in general, and the general public face of the LV2 site and wiki (i.e. it looks really bad and useful information is scattered everywhere, in inconsistent formats, and just generally hard to find or use, if it exists at all).
Towards solving this problem, I've done a lot of work on automatic documentation generation for LV2 extensions, and establishing good conventions for extension creators to follow in the future. The fruits of this effort can be seen by plugging the URI for any concept in an extension hosted at http://lv2plug.in directly into your browser's location bar.
For example, if you encounter event:inheritsTimeStamp in an LV2 data file somewhere and don't know what it means, head to http://lv2plug.in/ns/ext/event#inheritsTimeStamp (you will have to look up what the prefix "event" stands for in the file, of course). You are taken directly to documentation on that property generated from the extension itself (as defined in a .ttl file).
The same applies to entire extensions: the event extension's URI is http://lv2plug.in/ns/ext/event. Heading to that URI in your browser will take you to the documentation of that extension. This is the URI used directly in data files that refer to the extension, so no searching whatsoever is required to get at the information you need. As you can see on that page, there are links to all the related files you might need (e.g. headers, a tarball of the extension, etc).
Extension URIs will also content negotiate to return the requested type of data. Try these commands in your shell:
wget -q --header "Accept: application/x-turtle" http://lv2plug.in/ns/ext/event -O - wget -q --header "Accept: application/rdf+xml" http://lv2plug.in/ns/ext/event -O - wget -q --header "Accept: application/json" http://lv2plug.in/ns/ext/event -O - wget -q --header "Accept: text/plain" http://lv2plug.in/ns/ext/event -O - wget -q --header "Accept: text/html" http://lv2plug.in/ns/ext/event -O -
This could be used by LV2 hosts to automatically fetch from the web information they can not find locally. For example, if an extension is required by a plugin but a host doesn't know what it is, the host can trivially fetch that extension from the web and display a human readable description of what that extension does. This is the kind of thing that using good technology like RDF allows, you naysayers out there ;)
This is all a bit rough around the edges still, and the extensions hosted here aren't all documented well yet (and of course, not all extensions are hosted here), but I'd say this is a pretty big improvement. If you base your own extension on the form of these ones (which is easy), you get all this for free. Hopefully soon enough most if not all extensions and plugins will work this way, at which point I'd say that the reference documentation problem of LV2 is solved about as well as it possibly could be. Better than any other technology I have seen anyway (how many things do you use where you can just plug whatever you're curious about right into your browser and get taken directly to the documentation for that thing?).
Of course, more higher level "tutorial" type documentation is still needed, but this is a separate problem. As far as reference documentation goes, here is the chicken. Go forth and create eggs.
Stay tuned for more tools to come, e.g. a similar documentation generator for plugins, a plugin/extension validator, etc.
GStreamer LV2 Surround
My last post was mostly about adding multi-channel support to GStreamer.
That was only partially implemented though - many elements in GStreamer (and pretty much all of the ones that support more than stereo) require each channel to be explicitly labeled with its position. This information wasn't bridged until now.
The two sides of this situation are:
The LV2 Port Groups extension:
GStreamer multi-channel: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-gstmultichannel.html
LV2 "roles" correspond to GstAudioChannelPosition. Unfortunately, the mapping was a bit strained with the Port Groups extension as it was at midterm time. Fortunately, that extension is not finalized yet, and in the process I found some other problems with it, so I decided to bring it closer to the way GStreamer does things, which seems to be common in other software that does this sort of stuff. Formerly, the port groups extension used the channel names from the relevant surround spec (see the Wikipedia page on Surround Sound). This resulted in a lot of roles that were really the same thing, e.g. the "Surround Left" channel in 5.1 is really the same as the "Left Back" channel in 7.1. This was pretty confusing in practice. GStreamer instead always uses positional names like "Left Back", which is unambiguous regardless of context (you don't have to know if it's 17.2 or whatever to know what "Left Back" probably means...). So, I changed the LV2 port groups extension to be similar (though not identical; munging an LV2 extension to match GStreamer API wouldn't be appropriate).
This information is now queried out from LV2 plugins that have it, mapped to GStreamer channel positions, and set as capabilities on mulit-channel pads. This means multi-channel surround LV2 plugins should now work fine with surround sound GStreamer set-ups, for example playing a Theora video through some audio processing and out through Alsa.
I updated swh-plugins for the minor changes, and added port group information to Invada Studio Plugins.
More to come...
GStreamer SoC Midterm Summary
Apologies for not blogging along the way for those who are interested in this project. I'm more into actually doing things rather than blogging about doing things ;)
So, LV2 in Gst, where are we? Well, I've had LV2 plugins working with the same functionality as LADSPA plugins for a while. The main downside was shared by LADSPA: no support for multi-channel streams.
Some background for those unfamiliar with LADSPA or LV2: LADSPA and LV2 plugins are very simple in terms of I/O. A plugin has a collection of "ports" which contain either a single floating point value (control) or an array of floating point values (audio). LV2 extends this to any types but that's not important here. This is simple but causes problems in the face of stereo and other multi-channel streams: if a plugin has 3 audio inputs and 2 audio outputs, for example, what is what? Some kind of 3-channel audio input with stereo output? 5 completely unrelated ports? A stereo input and stereo output with a "sidechain" (common with e.g. compressors)? This information is not available in LADSPA, the best you can do is guess (which is practice means it just doesn't work).
GStreamer works with multi-channel streams as a single interleaved stream, so this is a problem. Thankfully, LV2 makes it trivial to add whatever information you like about plugins without having to touch a line of code since plugins are described in RDF (see the LV2 site for more information). All that needs to be decided is how to actually model that information. A specification for this is called an "ontology" in general/theory, and an "extension" in the LV2 community.
So, the problem is we need(ed) a good multi-channel ontology for LV2 plugins to work well inside Gst, since most things in Gst are at least stereo. The difficult thing with creating ontologies is making sure anything anyone might want to describe in the future is accounted for. Here's my best shot at this so far: LV2 Port Groups, based largely on earlier work by Lars Luthman and some input from the LV2 community. This extension isn't final, but expresses all the information needed by Gst for multi-channel (and more). (I also wrote the documentation generator that created the aforementioned specification page in the hopes that more user friendly documentation will encourage adoption by plugin and host authors).
I've created patches for the popular SWH and Calf plugin packages to add this information. When the extension goes final they will be included in these projects, but in the mean time are included in my git branch of gst-plugins-bad (see http://git.drobilla.net).
This is, as far as I know, the first time coherent multi-channel information has been available about plugins from the "LAD" community (e.g. LADSPA, DSSI, LV2). Coincidentally, this information is required for recent work on Ardour, among other things. In hindsight, this was a pretty glaring hole in the general state of LAD plugins, but back to GStreamer...
I've rewritten quite a bit of the GstSignalProcessor class (used by the LADSPA and now LV2 wrapper elements) to support multi-channel plugins. In code terms this means creating a set of buffers for non-interleaved data used by the plugin, and interleaving/deinterleaving buffers to/from Gst, respectively.
In summary: many LV2 plugins now exist with useful multi-channel information, and stereo LV2 plugins now work correctly in GStreamer. It should now be simple to add support for other audio plugin interfaces (VST? AudioUnits?) that also works with multi-channel streams.
- Get the "role" information from the plugin data and use it to support surround streams correctly
- Finalize and publish the LV2 Port Groups extension, and contribute patches for all major plugin collections
Where to go from there is pretty open-ended. Unlike LADSPA, LV2 can theoretically support any kind of data, or any feature (non-realtime and non-audio things included). Extensions just need to be made to bridge the gap. What sort of functionality would you like to see bridge the GStreamer/LV2 gap?
Opinionated dichotomies in science
Computing is the only real science. The rest can be simulated.
patchage 0.4.2 has been released. Patchage is a modular patch bay for Jack and ALSA based audio/MIDI systems. For more information, see http://drobilla.net/software/patchage. -- David Robillard email@example.com
- LASH support via D-BUS from ladi-patchage branch
- Remove old LASH support via liblash
raul 0.5.1 has been released. Raul (Realtime Audio Utility Library) is a lightweight C++ convenience library for realtime programming, with a bias towards audio applications. For more information, see http://drobilla.net/software/raul.
- OSC blob fixes
- Use true atomic integers for Queue indexes