Blogs

Rack Performer - MIDI effects configuration

Next release preview: create keyboard splits / layers / merges using the builtin MIDI effects

Live Factory Team's blog - November 1st, 2012
We added three basic but powerful MIDI effects that can be applied to each module MIDI input: message filter, notes range and notes transpose.

By combining these effects it is now possible to create complex keyboard splits, layers and merges, as explained in this post.
Rack Performer - MIDI input filters configuration

Next release preview: versatile MIDI filters

Live Factory Team's blog - October 26th, 2012
Next version will include a basic but useful new feature: MIDI input filters.

When using external MIDI hardware, sometimes you don't have control on what kind of messages the devices will send, and it can lead to conflicts when several devices send contradictory messages.
Rack Performer presets links

Next release preview: one preset to rule them all!

Live Factory Team's blog - October 5th, 2012

Scene Snapshots offer a very fast mean to recall entire patch presets, but they don't offer much granularity as they always apply to all modules.

Sometimes you would like to have an instrument and all the effect chain patched after it change their presets at the same time, and this is what the new Presets Links are about.

Rack Performer live synopsis

Next release preview: introducing the Live Synopsis

Live Factory Team's blog - October 1st, 2012

As live performance is all about control and interaction, we try to make the human-machine interface configuration as simple as possible.

The Live Synopsis offers a clear and intuitive way to manage all mappings from a centralized location.

Rack Performer mode selection menu

Next release preview: how we decided to get rid of an annoyance

Live Factory Team's blog - September 13th, 2012

Today we decided to tackle what was surely the number one source of frustration in Rack Performer: patcher locking when audio is enabled.

This behaviour had nonetheless a rational ground, so here is how we settled the issue...

Subscribe to our newsletter