Old version:
This is my concept for an arranger to end them all. I’ve been thinking alot about this lately, and learning of the different ways other programs handle arrangements. I studied the workflows of Ableton Live, Cubase (Playlist), FL Studio, Machinedrum and MPC arrangers and contemplated on how I work myself, and what would be most flexible. I’ve also tried hard to take into consideration difficulty of implementation and where Renoise is now, so as to not complicate things too much.
Firstly, the biggest obstacle with a “new” arranger, and the clip-style presented here earlier, is that it implies pattern “polyphony” - being able to play multiple patterns in parallel. I also don’t think this is optimal, since it creates the problem of what to do when you want a pattern to cut a preceding one.
Mostly, it looks like the FL studio playlist, except with some important improvements that makes it more powerful.
A quick run-down of my concept:
- The horizontal grid is strictly line/tick based. This makes visualizing pattern lengths easy, and keeps with the tracker tradition of time. Also, a “true” timeline would be complex and harder to implement.
- Each object in the arranger is a pattern, as defined today.
- Vertically, the arranger is split in lanes. For non-overlapping objects which lane it’s on is irrelevant. Essentially like FL Studio.
- An object can overlap another on the same lane, cutting it short. This is really useful for making breaks and getting creative with arrangements.
- Overlapping objects on separate lanes play in parallel - except if they contain events on the same track(s). If two objects play on the same track, whichever is on a lower lane in the arranger, gets precedence - like a monophonic synth, basically. Conceptually, this is like comping multiple takes in Cubase. FL studio will always play in parallel, which I believe is a poor idea.
- Doing it this way makes it easy to write a bass line pattern and a “place holder” drum beat, then focus on a separate beat pattern later.
- Changing a bass part for the last quarter of a pattern means simply making a new bridge pattern and put it in a lane below at the right time. Easy as pie, and creatively valuable.
- If you do want something to play in parallel, just put it on different tracks (like now).
Objects indicate in the arrange what tracks are overridden by another (higher priority) object. That’s what the red “tags” are, showing which track number is “muted” and where.
Showing of “overlap tags” could be togglable, simplifying the view even more (although reducing the level of information communicated).
The yellow lines indicate pattern truncation.
All available patterns are listed to the left. Simple drag’n’drop into the arranger to place patterns.
A transport marker indicates song play position, with line resolution.
Loop range markers allow looping a section of the arrangement.
Vertical zoom should be possible in the arrange, to allow listing more “track mute stripes” etc.
Objects should be mutable to disable playback. This makes testing new ideas easy.
Automation is preceded like other tracks. One very cool thing this lets us do, is use patterns as “automation clips” like in FL Studio. (Possibly, it could be a good idea to add global automation tracks, separate from pattern/object arrangement, at some point).
Multiple arrangements per song allows remixing and rearranging without losing info and previous work.
For this concept to work, only two new concepts need to be added to the renoise core. Muting of individual tracks during playback in the arrangement and cutting patterns short (skipping to the next). Importantly, no parallel pattern or track playback is necessary.
To me, the most important factors are creativity, a free-form workflow and simplicity, and IMHO this will kick so much ass it’ll wipe the floor with both Ableton and energyXT for exploring arrangements. Now, imagine a “live mode” where you can trigger whole arrangements, and you’ve got live sequencer nirvana.
So, whatcha think? Just plain stupid, or a useful concept?