I’m using a combination of Renoise and Digitakt as my MIDI controller.
My live set brain is the Digitakt, in which I have different patterns, sounds, etc. It does 80% of the work in the live performance.
However, despite being very very powerful, Digitakt is monophonic, can’t do chords, and the pattern size is limited (64 steps). So I’m using Renoise as an “extension”, since I have no polyphonic hardware.
This is where Paketti (the tool by @esaruoho) comes in handy.
I can have a Renoise instance with chord progressions and trigger the sections from my Digitakt (for example: I can set a rule to launch the section* 3 once every 8 bars…).
Same for breakbeats: I can use the Digitakt to tell Renoise to switch sections and even jump between patterns inside that section (hitori tori style) using MIDI mappings.
So I have two synced instances of Renoise working as instruments for the Digitakt: one for breakbeats and more complex drums + one for chord progressions. Idea is to set everything up in the Digitakt and not look at Renoise at any moment during the performance, because it distracts me.
The Paketti functions are called “Select section using knob”, “Select, Trigger and Loop Section XX”, etc… Natively, Renoise won’t move the section loop when you change sections (I mean the gray boxes at the left of pattern matrix), so @esaruoho was kind enough to script it. It would be nice to have it natively, though 
*By section, I mean the Pattern Matrix headers you can rename.
Just one problem:
I notice a lot of MIDI clock jitter regardless of my configurations when clocking Renoise externally on Linux. Sometimes the BPM speeds and slows down, which is very annoying. But I guess that’s a subject for another thread.