Renoise’s scripting interface is something special, allowing people to build anything they imagine in a way that’s directly integrated with this production studio – no add-ons required. But whether or not you yourself want to code, that also means access to the imagination of the Renoise user base. And one of the most impressive shows so far is an ambitious process to duplicate Ableton Live’s mixer and clip launching interface inside Renoise. We first saw that effort at the end of the year, but it’s now about to reach a whole new level.

Now, in fairness, part of why people like me would like to see people use something other than Ableton Live onstage is to see different performance modes on laptops. And this absolutely doesn’t do that – you’ll see that the interface is more or less a clone of Live. (And I’ve been known to be critical of such interface cloning.) But there are two advantages. One is, doing this in a script in another host is a fascinating exercise in learning how to maximize the potential of Renoise’s scripting, one that could lead to other things. The other is, it’s possible that the familiarity of environments that work like the Live Session View could help performers ease into new ways of working with Renoise – without having to make the leap all at once. Renoise itself offers a very different way of working, built on tools of yore – basically, an alternative music-making path in software design entitled trackers. Like being able to go for a burger, fries, and ketchup in a foreign town, the availability of Cells could help those foreign to the tool moonlight between Ableton and Renoise in their work.

If nothing else, it’s something of an engineering triumph that this works at all.

In version 2.0, now in beta, a complete rewrite of the code vastly expands what’s possible with Cells. CDM readers took a lot of interest in this development when we covered it last, so it’s great to see what may be possible as the code matures.

And in some critical respects, Cells now does things in an integrated fashion that aren’t in Ableton Live. Pattern riffs, built on Renoise’s unique instrument paradigm, encapsulate samples and sample mappings together with your patterns. Bi-directional controller support, while eventually grafted atop Ableton (particularly for certain supported controllers), is part of the framework. There’s also integrated network sync support inside the tool, all implemented atop OSC; it’s still in beta, but shows lots of potential. (That’s possible in Ableton using existing MIDI and network tools, but seeing the server inside the tool is impressive.) And these are the kind of areas where it’s hopeful we’ll see new ideas in Ableton and rivals alike – another reason choice is a good thing.

From the forum post, forwarded to CDM by the creator:

Cells! 2.0 is a complete rewrite of Cells! 0.9. This has been based upon further code experimentation and user feedback. However, due to the improved approach and cleaner code, it has been possible to add many more features.

Thanks to Void Pointer (http://soundcloud.com/void-pointer) for kindly supplying the samples used in the demo video.

Realtime ‘Granular’ Timestretch

Cells! 2.0 allows realtime timestretch in a ‘granular style’. This allows full independant control of both tempo and pitch while still keeping playback syncronised to the beat. Granular timestretch applies to samples which have both a beat sync value and autoseek enabled but beat sync is disabled.

Realtime ‘Slice Based’ Timestretch

Similar to the ‘granular’ timestretch, Cells! 2.0 adds support for sliced loops with independant tempo and pitch control. Each slice will be played back at the correct time to maintain the overall tempo of the entire loop. Slice-stretch applies to samples which are sliced. The length of the cell is assigned through the beat-sync value.

Pattern ‘Riff’ Storage and Playback

Cells! 2.0 allows you to quickly save individual pattern tracks as riffs for use live in Cells!. The riffs are stored in compressed format within the instrument itself, so you can quickly and easily save all samples, sample mappings and riffs self-contained within a single XRNI file. Note that any Renoise instrument is be supported. This means you should be able to send note riffs to external instruments or VSTi’s.

Live Jamming Mode

For specific types of samples, Cells! 2.0 allows real-time ‘live jamming’ playback mode. Play your samples directly with either the mouse or a physical controller for improvising over your mixes to add that extra sparkle. Individual slices from sliced loops and plain one-shot samples can be played in ‘live jamming’ mode.

Bidirectional Controller Support

Cells! 2.0 now has its own native controller framework. This allows full bidirectional support for supported hardware controllers. Livid Instruments Ohm64 and Novation Launchpad (beta) are available with the inital release. If you would like further support for any additional controllers, feel free to either send them to me for development or contact me directly to work together and implement support.

MultiFX

Cells! 2.0 incorporates a simple ‘DJ style’ effects processor into the main UI. Effects supported are a low-pass filter, beat repeat, delay and phaser. All effects are controlled through simple common amount and rate controls. All time based effects are syncronised to the beat.

Sample Preparation Tools

Cells! 2.0 incorporates simple methods to quickly create and prepare samples for use. Both the sample editor and the sample list box contain a ‘Cells! menu’ from which the sample can easily assigned to a specific playback mode and length. A ‘sample report’ feature is also available which allows you to quickly identify how the selected sample
will play within Cells! 2.0.

Additionally, Cells! 2.0 allows quick rendering of either entire patterns or specific tracks within patterns from your existing songs. Only the instrument of the first note within the pattern track will be saved. It will automatically assign the correct beat sync values even if the original song is not written at 4 LPB. All rendered samples will be contained within an ‘Unsorted Cells! Renders’ instrument within the song to easily allow saving of all samples to disk. This menu is present in the pattern editor context menu.

Multiplayer Networking (beta)

Cells! 2.0 has built in support for up to four machines to link together over a lan (via OSC) and keep in sync. Make huge mixes across multiple machines or get some friends around and all play together. Setup network connections on the master and ensure Renoise OSC servers are running on all machines.

Minor improvements

- Variable channels from 4 to 16.
- Variable cells per channel from 4 to 16.
- Variable cell height and width (for touch screen usage).
- Automatic sample selection option (for waveform view in the sample editor).
- Safe cueing option to automatically mute cue output if set to the
same as the main audio output.
- Single output mode (splits the audio so master output on one
channel and cue output on the other).
- Slightly tweaked user interface to cater for the additional features.
- Better audio routing (A/B crossfader or crossfader bypass (M))
- Various other optimisations (too many to list)

Downloads

Download the updated 2.0 beta manual here (http://www.box.com/s/evt2vnpb51hzj6kic1zg). The XRNX tool will is attached to [the forum] post. Please ensure you read the manual, most questions will probably be answered within. Cells! 2.0 Beta requires Renoise 2.8 beta 7.

Download and forum post:
http://www.renoise.com/board/index.php?/topic/33947-cells-20-for-renoise-28-beta/

Let us know if you put this to use; we’d love to hear how it works (particularly network-synced jams). And, hey, there’s nothing stopping you from using this alongside a machine running Ableton Live – even on a Linux laptop.

For years, since the launch of Ableton Live, many have waited for a worthy rival, something that combines production and live performance for music users. Live isn’t without alternatives – Renoise, for instance, has earned some fans, though it isn’t necessarily built for live performance. But few provide the same real-time workflows.

Bitwig, based in Berlin as is Ableton and featuring some Abletronic veterans, today took the wraps off its own Bitwig Studio. The good news is, it’s looking as though it might shape up to be a viable tool for DJing, performing, and making music. The bad news is, in a market already crowded with lots of similar tools vying for your attention, the first release will look more familiar than radical. That is, it looks and works a whole lot like Live. There’s an Arranger view, a clip launching view with scenes, a tray on the bottom with effects and instruments (they’re even called Devices, like in Live). The screen layout, and even specific interface widgets and channel strip arrangements are all straight out of Live.

It’s not just a little like Ableton Live, either – it’s in some cases a direct clone. Nested drum machine Devices, for instance, work in a way that I’ve never seen out of Ableton Live. A channel strip similarity or two is almost inevitable; here, though, lots of little details add up to something that feels like Ableton, but didn’t come from Ableton.

What that means to you may depend on what you want: whether you just want an improved Ableton alternative that works like Live, or whether you want something more fundamentally different from Live as an alternative.

If you want “Ableton Plus,” Bitwig does take on features Ableton is missing. For instance:

1. Linux support. In fact, right out of the gate, this could quickly be the answer for Linux users waiting for something they could use without booting to Mac or Windows.
2. Proper multiple document support. You can share content between projects in Ableton, but here you can actually open and freely exchange media with multiple files at once.
3. Mix audio and MIDI on the same track. Tracks are content-agnostic.
4. Per-note automation, with the mixed MIDI and audio, promises more detail-oriented editing.

Those are three significant breakthroughs. And it looks like there are lots of tweaks and improvements throughout the tool, many of which I’m sure we’ll hear about as people begin testing the beta. (One nice example: a vertical pane lets you view arrange and clip launching views simultaneously.) Multi-monitor support, while present in many tools, is sorely lacking in Live but available here. Plus, as some readers note, you do get 64-bit support, though that seems an advantage over Ableton that won’t last long.

The challenge is, as a new entrant to the market, your first obstacle is telling a story about what you are. And here, there seems a missed opportunity to make a first impression as something truly different, rather than something “similar, but better.” Ableton Live 1.0 when it was released was a significant departure from what had been seen before. So, too, were the first trackers, the first audio+MIDI DAWs, and the first graphical sequencers. Bitwig Studio isn’t that kind of breakthrough – not yet.

Not that being different is easy, or even always desirable. Amidst so many things users want, and so many expectations they have about how things will work, it’s tough to do something genuinely new without simply confusing everyone and driving them away. But it has happened – Ableton Live’s original release being a notable case. One question is whether you make some sacrifices to release the most significantly-different tools initially, or whether you choose to cover the basic bases to provide a workable solution from day one, and the Bitwig devs seem to have chosen the latter.

The most interesting features remain on the horizon. LAN multi-user jamming and multi-user production are both on the roadmap – features we’ve seen in other tools, but which have yet to catch on. And there’s an integrated modular system that lets you build your own instruments and effects with graphical patching – something seen in various forms from Buzz to Max for Live, but one that could use a fresh take in integration with the tool.

In the meantime, we’ll have to hear from beta users whether Bitwig is something worth a look. You can sign up now:
http://bitwig.com/bitwig_studio.php

We’ll be eager to hear what you think.

Pics:

If you’re using Ableton Live 8, you’ve hopefully already discovered the joys of Track Groups. Track grouping is a welcome feature in any DAW, but in Live, the mixer-centric Session View can easily get unruly with endless columns of vertical tracks.

I wanted to share some discoveries about Track Groups, including what I thought was a big realization about how they worked with clips that turned out not to be as exciting as I thought.

To group tracks, select multiple tracks first (click one, then shift-click the last one), right-click (ctrl-click on Mac), and choose Group Tracks. The result – what’s basically a submix:

• You can save space by collapsing tracks in your view, clicking the triangle at the top of the Group
• You can add insert effects to the whole Group, and signal will be routed through that entire chain (making them like a quick send)
• You can control the whole “submix” Group at once using the Group’s mixer parameters

No surprise there. Here’s the surprise.

You’ll see when you create a Group that the Group track has actual clip slots – unlike the Returns, which have none. (Check out “A Return” and “B Return,” created by default, to see what I mean.) You’ll also see a colored pattern for each clip slot that is adjacent to grouped tracks with clips in them:

You can use that slot (seen here on the left) to trigger groups of clips. So, if you’ve grouped four tracks, and the first three of clips, triggering the clip in the Group track will trigger all of those clips at once.

It works just as Scenes do, but with a couple of twists. Unlike Scenes, you won’t trigger everything else in your Session – you have some control over what gets triggered. Also, you’ll see if you click one of the slots for the Group, you get a Clip View for editing.

At this point I got really excited, as I thought we might finally have Scenes that had the same editing parameters as Clips. No such luck. If you click one of the Group slots, you’ll see Clip, Launch, and Notes boxes. This includes things that Scenes lack – Launch Mode options, Quantization override, and Follow Action. So, initially, you might think as I did that we finally had the ability to have Scenes (albeit inside Groups) with more control and Follow Actions. Unfortunately, these actually behave as “wildcard” editing for the Clips. So what you’re actually doing is changing the Follow Actions for all the clips to the right of the Group slot.

That said, you can still use this as a hack to quickly create chains of Follow Action events, so it still could be useful – just not as useful as if Ableton finally gave us more control over Scenes or other groups of clips.

One last note: as further illustration of this principle, you can’t rename the slots in the Groups. That’s too bad, because it would allow you to create effectively grouped Clips that controlled Subclips. If you try to use the Clip Name box, you’ll actually rename all the Clips in the Group – and you still won’t see any text in the slot in the Group.

To me, it would be more consistent if both Scenes and Clip slots for Track Groups behaved exactly the same way individual clips did, enabling the quantization and follow actions that clips do. But that’s just my take.

There are people who are bigger Ableton gurus than I am who read this site, not to mention various people who work for Ableton, so I’m curious to hear what you think about this, and if you have other ideas for how to use Groups. I do remain a little disappointed, because you get track groups in lots of DAWs, but you only get Clips in Ableton Live.