Hey community,
Does anyone know if there’s a way to create a scene that would pull up the looper open and ready to loop.
I’m not seeing it, perhaps not possible.
Thanks
1 Like
There isn’t for now, to my knowledge.
My trick is to use a short MIDI cable to connect the In and Out, so you can send specific MIDI messages (like opening the Looper) via a footswitch, effectively grouping a scene change and pulling up the looper. A bit of a hack, and it only works provided you’re not using your MIDI in/out for anything else.
Also, have you checked the new Hybrid mode in CorOS 2.0? That has solved the issue for me, because I can have the top row dedicated to scene changes and the bottom row in stomp mode, to call the looper.
Thank you! Did you make a YouTube video about explaining this method? If so, it was a great and I love your playing!
I’m using the QC as a dual source preamp blender/ effects unit, DI. The looper is so handy and sounds great, my main thing is it’s sort of clumsy to have to open and then close as I jump around between other stomps and or scenes.I’m afraid I’ll hit the wrong switch, as I did on my first gig with it. I’m going to give it a go again tonight. The “hack” mode is cool because you never go to performance mode, as I see it.
One thing I’ve had happen more than a couple times, pretty scary. With the looper running the output lights up solid red out of nowhere and everything locks up.
It’s not an actual signal clipping issue.
It just locks up with No signal at all, you have to reboot.
Have you ever seen this?
Hey I know I’m commenting on an old thread, but I wanted to ask about the midi hack for the looper. Is it possible to still do the hack if I am using midi to control a pedal (strymon timeline and big sky) that has midi thru- and then I have the last pedal send a midi cable back to the QC? So it goes QC-Timeline-Bigsky-QC. With the new midi setup in OS 3.0 would that work?
I’ve experimented a good bit with the midi loopback hack, but I’m not sure about that situation. The Merge function is a bit problematic with the QC. You could try it-
Maybe using different channels on the devices would work
That’s what I was wondering (different channels). I’m brand new to QC (just got it 2 days ago) so I’m still working everything out but I’m going to experiment with it.
Another question you might know the answer to- if I assign a midi message to a footswitch on the QC, can I make it so that midi message is only sent when certain presets are loaded?
To go into more detail, here’s how I ultimately want my midi set up. First, I want individual presets to send midi messages to my strymon pedals on preset load (that seems easy enough).
For my looper, I’m mostly planning to use it to buff up some sections of specific songs with my band (record myself during chorus 1, play it back during chorus 2 so I can do a lead part on top, etc). I’m planning/hoping to do that by assigning footswitch G to send the midi signal for looper start/stop and footswitch H sends looper undo/redo (I understand from reading that’s the best way to “save a loop for later.”) I’d like those foot switches to have that functionality for those specific presets, but obviously that would be problematic on other presets where I want G or H to be something else and I don’t need to start/stop looping. Is it possible to do that? As a backup solution, will those midi commands only run if looper x is a device block in the preset? Any better way to organize things?
Those settings are Preset-specific, they will not save globally. You can configure it however you like per preset. Might be good to make templates, like a “Looper” template with those commands saved so you don’t have to configure the layout multiple times.