ganv 1.4.0 has been released. Ganv is an interactive Gtk canvas widget for graph-based interfaces (patchers, modular synthesizers, finite state automata, interactive graphs, etc). For more information, see http://drobilla.net/software/ganv.
- Begin using library and pkg-config names suitable for parallel installation. This version of flowcanvas is flowcanvas-1 and is NOT compatible with previous versions
- Clean up API and improve documentation.
- Add font size API
- Use system theme font size by default
- Size empty ports in font based units so they look right when zoomed
- Adjust padding and placement to precisely fit text
- Add ability to select connections directly
- Add Connection::set_curved()
- Fix lingering handle when deleting connections
- Dramatically increase performance by rendering text manually rather than using the truly awful Gnome::Canvas::Text.
- Remove use of boost smart pointers. Adding and removing from containers (e.g. Canvas, Module) is now done automatically.
- Clean up API/ABI by hiding private implementations.
- Add ability to select connections by their handles, either individually or in groups with rect select.
- Further slight improvements in memory consumption and alignment.
- Improve scalability to graphs with many connections (eliminate linear connection searches and redundant connection collections).
- Switch to GPLv3+
Disabling the obnoxious lights on the Evoluent Vertical Mouse 4
I've been a fan of the Vertical Mouse for a while now, since the extreme wrist pronation of a conventional horizontal mouse aggravates my wrist. Unfortunately, however, Evoluent saw fit to put a blindingly bright blue lit-up logo on the back of the latest version (much to the delight of absolutely nobody in their target market). This is particularly problematic if you work late or sleep in the same room as your computer (blue light messes with your sleep cycle, hence tools like Redshift).
![The offending logo (unlit).] (/images/IMG_20140414_204108-225x300.jpg)
After unplugging my mouse every night for so long, I finally decided to tear the thing apart and see how easy it would be to disable those lights. It turns out this is very easy, you don't even need to desolder anything. There are four screw holes hidden under the label and front pad on the bottom. You don't need to remove the other two pads like I did in the process of figuring this out.
![Screw hole locations.] (/images/IMG_20140414_203908-300x225.jpg)
Remove all four screws and the top should come off easily. There are ribbon cables connecting the buttons, though, so don't pull too hard. Now you can see the battery of LEDS.
![The seven (!) offending LEDs. When Evoluent shoots for annoying they go full out.] (/images/IMG_20140414_203946-300x225.jpg)
Luckily, this pointless board is connected with a header, so you can simply unplug it, and reassemble the mouse.
![Disconnected LED board connector.] (/images/IMG_20140414_204005-300x225.jpg)
Pretty names in Patchage via Jack Metadata
The much-awaited (by me, at least) Jack metadata API has arrived. This will allow us to easily achieve many new things with minimal/nonexistent API friction. One of the simplest and most obvious is pretty names for Jack clients and ports, so I've chosen this as the first thing to tackle (as part of a drive to get Patchage polished up for a much overdue release).
Unfortunately, as far as I can tell, there is a chicken & egg scenario here since nothing is setting this metadata yet. So, I've made Jalv and Ingen both set pretty names for their ports. In the case of Jalv, the "pretty name" is the label given in the plugin data (distinct from the LV2 "symbol" which is restricted and unique).
Firing up Jalv with the Tal Dub III plugin (LV2 port courtesy KXStudio), we can see the port symbols, which are a bit awkward for end users with their prefixes and underscores. Conflating strong identifiers with human-readable labels is a serious design error I learned of the hard way, but that's a discussion for another time...
Enable "Human Names" in the view menu, or press C-h, and voilà, we see the pretty names set in Jack metadata (if present) instead.
The metadata API is very simple to use for ports, though there seems to be a hole in the API which makes it difficult to get the UUID for your client to set metadata (I want a simple jack_client_uuid, like jack_port_uuid, but it seems you have to get a string UUID and parse it to a jack_uuid_t, clunky enough that I just didn't bother). In any case, I am happy to see a low-friction mechanism in Jack which apps can use to share metadata towards making a better user experience.
It will be interesting to see what sort of information proves useful and becomes established/standard. For those of us of a mad scientist bent who live in a nest of patch cables, a CV tag seems like another obvious simple step, but for everyone, a big step is finally having meaningful port grouping and channel roles. I have always liked to joke that Jack (like LADSPA) doesn't really even do stereo, but with metadata, we can mark up stereo, 5.1, Ambisonics, etc., and other clients will be able to make sense of the channel assignments without resorting to dirty kludges based on guessing from names. All without changing the ABI one bit. Good stuff.
Labeled MIDI controller values in Ardour
A while ago, I implemented MIDI patch, controller, and note name support for Ardour.
There was one thing missing from that work: labelled controller values. This is particularly useful for controllers that don't represent a continuous numeric parameter, but instead have a set of specific values. For example, the Moog Minitaur supports CC #86 to control the LFO sync clock division, but it's not obvious how a 0-127 number maps to a clock division. From the manual, we can learn that 61-67 is "1/4", 68-73 is "1/8 Dot", and so on.
Translate that information into standard MIDINameDocument format, and a few hours of hacking later... voila, Ardour displays something sensible when hovering over an automation point instead of a meaningless number.
If you want to add support for your MIDI device or program, my .midnam documents for the Moog Minitaur, MF-104M, and MF-108M, included in the Ardour distribution all contain examples of labelled values. It should be relatively obvious how to copy and modify these for other devices.
mda-lv2 1.2.2 has been released. This is a port of the MDA VST plugins to LV2.
- Fix compilation against LV2 < 1.8.0
blop-lv2 1.0.0 has been released. This is a port of the BLOP LADSPA plugins by Mike Rawes to LV2.
mda-lv2 1.2.0 has been released. This is a port of the MDA VST plugins to LV2.
- Fix tuning of Piano and EPiano at sample rates other than 44.1 kHz
- Fix const-violating casts
jalv 1.4.4 has been released. Jalv is a simple but fully featured LV2 host for Jack which exposes plugin ports to Jack, essentially making any LV2 plugin function as a Jack application. For more information, see http://drobilla.net/software/jalv.
- Add -c option for setting controls from the command line
- Add --no-menu option for jalv.gtk
- Don't expose non-MIDI event ports to Jack
- Hide controls for ports with notOnGUI property in generic UI (based on patch from Robin Gareus)
- Support ui:portMap feature to allow UIs to avoid hard-coded port indices (useful for compatibility and separately distributed UIs)
- Preset menu support for Qt (patch from Timo Westkämper)
- Allow lilv_state_restore() to be used without passing an instance, for restoring port values via a callback only
- Fix unlikely memory leak in lilv_plugin_instantiate()
- Support denoting latency ports with lv2:designation lv2:latency
- Allow passing NULL port_class to lilv_plugin_get_port_by_designation
- Call GetProcAddress with correct calling convention on Windows
- Add support for running plugins from Python by Kaspar Emanuel
- Clean up after test suite so multiple runs are successful
- Add lilv_port_get_node() for using world query functions with ports
- lv2info: Don't display invalid control maxes and defaults (patch from Robin Gareus)
- lilvmm.hpp: Add wrappers for UI API