Thoughts from my first live looper gig

Thoughts from my first live looper gig

I just performed my first gig using SooperLooper with my Zynthian setup. Overall it went great. Kudos to whomever helped to integrate this amazingly powerful yet simple tool into the Zynthian interface. It has changed the game for what I am able to accomplish as a solo musician.

I have a few observations on what went well and what I’m looking to hopefully change in the near future.

My Setup

My gear consists of the following:

  • Zynthian v5.1: The Zynthian box with Raspberry Pi 5 processor, running Vangelis build.
  • Yamaha P-115: My 88-key keyboard, used for my main piano and electric piano sounds. This is setup on MIDI channel 1.
  • Arturia Keylab Essential 49: My ancillary 49-key keyboard, used for SetBFree Hammond Organ sounds as well as bass and other keyboard effects. This is setup on MIDI channel 2.
  • Behringer FCB1010 MIDI Foot Controller: The MIDI controller for sending CC messages to SooperLooper.
  • Korg nanoKONTROL2: Auxilliary controller for selecting tracks, setting volumes, etc.

I currently have the following controls mapped in the Behringer:

  • 1 (CC 20): Record
  • 2 (CC 21): Next loop
  • 3 (CC 22): Mute
  • Expression Pedal 1 (CC 1): Vibrato (SetBFree)
  • Expression Pedal 2 (CC 7): Volume (SetBFree)

Important: Record, Next Loop, and Mute are all set as “Latch” rather than the default “Momentary”.

General Approach

  • I have SooperLooper configured on the Main Mixbus. This gives me the flexibility to record any track at any time, essential for live performance. It does mean that whenever I select the SL UI, it selects the Main chain which unselects the SetBFree chain (more on that below).
  • Most songs, I just start a groove for the first loop. An essential trick I’ve found is to play through the loop once unrecorded, then hit Record on the downbeat of the repeat of that loop, then hit Record again on the downbeat of the next loop, and actually play that downbeat note. Much higher success rate of getting the track to start right on the beat record and finish right on the downbeat of the next repeat.
  • I have SooperLooper configured to sync to Loop 1. This enables me to more easily layer new channels with synchronized layers of loops. I hit Next Loop to cycle through the loops until I get to the one I want (usually it’s just hitting it once).
  • Whenever I need to mute a track, I just hit Mute with that track selected in SooperLooper. I also have mute quantized so that I can have the track mute at the end of the loop even if I press Mute early, then bring the track back in right on the beat by hitting Mute again.
  • On some songs, I will start with a groove, then layer a “clap” track on the 2 and 4 beats. This allows me to mute the first track when I need to play something that doesn’t match the main groove. The “clap” track lets me know exactly when the unmuted main loop will come back in.
    • For example, on “Cissy Strut” I’ll play the main groove on loop 1, layer a “clap” track on top of that, then mute the main track whenever I need to play the B-section.
  • Finishing a song is one of the most challenging aspects with playing loops. Generally I’ve found its most effective to just mute everything (all tracks finish to the end) then be prepared to play the main groove again live. I’ve also found it’s effective to remove selective tracks one-by-one to go back to the original groove.
  • An unexpected joy: Trading solos between the keyboards! I will play 4 bars of a solo on the electric piano (Yamaha), then immediately trade that solo with the Hammond B3 Organ (Arturia). It sounds like it’s two musicians who are really in tune with each other.
  • An important tip: I recommend refreshing your zs3 at the beginning of every song. This clears the SooperLooper so you don’t have bits from the last song inadvertently coming up in the middle of your performance!
    • Question: What exactly gets saved to the zs3 for SooperLooper configuration? I’m unclear exactly what does get saved, which would be helpful to know. It seems like for example the cc mappings and the number of tracks appear to be saved, but I cannot seem save which track is selected.
    • One thing that just occurred to me: I’ve been starting all songs with 4 empty loops, but it would make a lot more sense to start with just one loop and then add new ones with Next Loop. That way, every song starts with Loop 1 selected by default. I’m surprised this only now occurred to me…

Current Challenges

This gig helped highlight for me a number of challenges with live performance using this looper setup:

  • Inability to quickly see the SooperLooper UI. While in theory I can control everything with the Behringer, including selecting Next Loop, I’ve found it’s dangerous to rely on foot presses alone to confirm what track I’ve selected. I therefore want a visual on SL, but I also need to go to the Mixer UI in order to confirm other instruments. If there were some easy way to immediately go to the SL UI, without changing the selected track, that would be a huge help.
    • Even better would be an ability to have SL shown constantly and not have to lose focus to go back to the Mixer UI. Is there any way to connect a second external monitor that would be always showing either the Mixer UI or the SL UI?
    • Is there a way to map one of the function keys (e.g., F1) to show the SooperLooper UI? That may be sufficient.
  • Expression Pedals only active when the chain is selected. The key to effectively playing the Hammond B3 organ is having constant access to the expression and volume pedals. However, these pedals only work when the SetBFree chain is selected. Whenever I need to see the SooperLooper UI, I need to select the Main chain and that deselects the SetBFree chain. Perhaps this is a configuration option to have expression pedals constantly on across all channels? Of course, that brings complications as well, as the expression is also tied to the electric piano sounds.
    • Even better would be a way to permanently tie the expression pedals to the SetBFree chain, regardless of whether or not it is the selected chain in the Mixer. Can this be done?
  • Cannot map Undo/Redo: In the SooperLooper documentation, it mentions that Undo/Redo are a good way to facilitate switching between verse and chorus tracks. This would be amazing. However, I cannot find a way to map a CC message to the Undo or the Redo action. Has anyone configured this with a MIDI controller that sends CC messages?
  • Trigger is unreliable: I started experimenting with using Trigger as this will start the loop right from the beginning. This would be a great way to come back to the main groove, rather than Mute it and having to have a “clap” track in the background to let you know exactly when it comes back after you Unmute. However, in my practice I found that Trigger sometimes will play the loop twice on top of itself with a microsecond delay, which would be disasterous in a live performance. If this is a bug that can be fixed, then Trigger could be a good solution. For now, I’m sticking with Mute.
  • 40 second limit to loops: This limits the number of jazz standards that can be played directly into the looper. I understand you can change this default limit, but I’m thinking the limit is there for a good reason (longer loop = more memory = performance impacts), plus it can be difficult to consistently pull off a strong 40-second take. I keep hearing that the way to handle verse/chorus is to use Undo/Redo, which I haven’t figured out to how to map yet (see above).
  • Korg nanoKONTROL2 back lights are too dim outdoors: The nanoKONTROL2 is great for seeing which chain is selected and which ones are muted/unmuted, but the red backlight is way too dim to see if you are outdoors. The only way I was able to visually confirm the track I had selected was through the Zynthian screen.

Eventually as I get more adventurous, I want to play with using the Zynthian clock to orchestrate the loops rather than my own (somewhat questionable) sense of rhythm. I don’t see how this would be done without hearing an audible click track while layering the first groove, which to me is not acceptable for a live performance. I’m too scared at the moment to use any “round” feature; swing feel is way too nuanced and sensitive.

Final Thoughts

I’m very happy with using the SooperLooper. If you haven’t tried it, I highly recommend it. There is a learning curve, and I can’t promise you will get a full 8-hours of sleep when you start exploring its features (I have SooperLooper to thank for many a bleary-eyed Monday morning). I think the main things that would make it more “bulletproof” for performance would be the ability to see the SooperLooper UI anytime I need to, and an ability to see this UI independently of selecting the SetBFree chain so that the expression pedals are active.

I would love to hear your thoughts on what you find works best using this in your performances. Also, I’d greatly appreciate if anyone knows of any resources on how to use SooperLooper in performance.

-- TK

10 Likes

You may know about this possibility already, but if not: If you are willing to add a small monitor to your setup I think you could run vnc and put the SL UI on that monitor at all times. The downside is it might impact performance.

1 Like

Fascinating write up of actual use!

Many thanks!

Any recordings to hear what you were doing?

1 Like

Is that new in Vangelis? A second (HDMI) screen was never possible but would be a tremendous improvement.

So if you know how to accomplish this I would love to hear how it works …

It’s not new, been there for many versions, but I shouldn’t have called it a screen, cos you actually use a separate computer and a browser to access the engine’s UI and can also access a twin of the screen on Zynthian.

Here’s the doc on it, lemme know if you need help with it:

To my knowledge the RPi5 USB c port doesn’t support display port alt mode, so no video signal from there, while the Pi’s hdmi is already taken by the v5.1 screen. So, as tunagenes suggested, you need a “smart” monitor to access the UI of sooperlooper via vnc. The easiest would probably be an android phone/tablet and an Ethernet USB adapter. Then you can connect to the webconf vnc with very low latency (I wouldn"t trust Wi-Fi in a live setting).

VNC on Android is fine for display and short press but bold & long press are interrupted by the Android gesture detection.

You can learn CC either to the chain or globally.

3 Likes

I didn’t take any recordings because it was a paid gig and I didn’t know if they’d appreciate my recording myself. But here’s a new track I just threw down for fun, everything recorded live (using SooperLooper of course):

4 Likes

Thanks @riban, I totally forgot that I could enable the expression and volume pedals globally for the SetBFree patch while leaving them only locally selected for the others! That may be enough to allow me to keep the SooperLooper on screen the whole time without having to go back to the Mixer view except to change presets, since I have the Korg nanoKONTROL2 to select the mute and volume for each chain.

1 Like

Well, on the 5.1 the display is connected to the DSI connector, leaving HDMI free. Perhaps you are referring to a DIY zynth?

The HDMI screen works, but not together with the internal display. At least I did not find a way (yet) to use them both at the same time. It should be possible, but afaik has not been realised.

1 Like

It is also worth noting that in vangelis there is the concept of the active chain and the active MIDI chain:

  • The active chain is the last one selected, is indicated by the (by default) red block below the fader of the chain and directs chain actions.
  • The active MIDI chain is the last MIDI chain selected, is indcated byt the (by default) red strip at the very bottom of the chain and directs MIDI to Active Mode chains.

By arranging your audio only chains together, e.g. towards the right (adjacent to the main mixbus chain) you can avoid changing the active MIDI chain when you change audio chain selection. You may even want to pin chains so that they stick to the right side of the screen to provide visual separation of MIDI and audio chains. (I tend to pin mixbuses (groups / effect returns) but this is another use for the feature.)

You’re right, my brain didn’t work. So in theory one could simply connect a bigger touch display.

If the onboard display doesn’t work then that’s a bummer

Fantastic report @tkc!
Thanks for the feedback. Having feedback from real performance cases is really useful for developers.

Regarding your questions:

Apart from using Global MIDI learn for the expression pedals (instead of Chain MIDI learn), there is a little trick i implemented to access Main Control directly from the Mixer. Super Easy:

From mixer screen, enter ALT mode. You will see CTRL/PRESET button lights orange. Short-push CTRL to get the Main Control. From there, short-push MIX to go back to the Mixer screen. It will remember the ALT mode, so you can short-push CTRL again to get the Main Control, etc.

Regards!

2 Likes

Regarding the second screen:

The hardware part is easy. You could drill a little hole/slot in the rear panel of your V5 and connect a HDMI harness that you could use for connecting an HDMI display when you need it.

The software part is more tricky. There are 2 options:

  • Use the extra display to run the processor’s native GUIs, similar to what is done with remote VNC. This will add some CPU overload but modifications to the UI code would be minimal. It’s mostly implemented for the VNC.

  • Use the extra display to extend the zynthian UI, allowing to display a fixed screen, for instance, like the mixer. This would be super interesting, and it would improve the workflow without adding much CPU overload, but it would require deep changes and solve new challenges, like managing “focus”.
    I.e. if you rotate knob#4, what screen would receive the events? Do you want to change the highlighted chain in the mixer or you want to adjust the 4th controller in the control screen? Not trivial, but for sure we would reach a good solution.
    Perhaps you should open a feature request in the issue tracker and see what happens in the next months :wink:

6 Likes

I still reckon hdmi 2 is a lovely place to put one a4 pdf chord sheet.

And having a feature request rejected doesnt make me bitter, oh no…

Sniff

4 Likes

Obviously the only valid usage of a second screen is a terminal outputting random memory hex dump data to impress my analog gear only friends (and myself).

5 Likes

I’m actually working on a midi/sound controlled visual display to accompany an audio jam visually. For this I would use an extra Raspi with a dedicated HDMI output and using the builtin graphic acceleration. But it could be interesting to have it as an extra output from Zynthian, too. Unfortunately I think this is music from the future…

Because the application is only controlled by OSC/midi/sound no keyboard, no mouse or other physical input devices would be needed. Would this be able while using a dedicated xserver for the hdmi device output, omitting keyboard, mouse input? Not connected to Zynthian’s GUI in any way? Hence, more or less @wyleu 's feature question?

Regards

1 Like

:rofl: the digital equivalent of analogue guys with their oscilloscopes all over the place… : )

I refer the honourable gentleman to the following image…

5 Likes

I know, it’s already done :wink:

I will do that. Both options you mention are worthwhile.

Edit: Done

I’m already looking forward to it :grin:

2 Likes