Quad Cortex Set Lists for Gigging

I use an RJM PBC6X and this is exactly the way I use and build setlists each week. It’s very handy. I actually prefer their naming convention too: “Presets” get loaded into “Songs” which get loaded into “Setlists”. Songs simply point to any Preset and Setlists simply point to any Song. No preset needs to be doubled.


Exactly, that’s the way to make setlists easy to handle. Not to forget - sorting per drag and drop is a must have, at least for setlists.
The QC is a powerful device with an amazing UI, but this is still a major shortcoming and a simple manual sort has not yet been announced for 2.0 either. Nevertheless I hope so.

Completely agree with this. I’ve had to make notes to try to get my head around the QC file structure. By contrast I’ve used the RJM PBC to easily drag and drop songs into a setlist for a given show with their editor. Then I can go back through the list and pull up an old Setlist, make s few changes, re name and save. Handy for keeping track of what you’ve played where as well. I think this is a really important change for Neural to make for live use, seems much more intuitive.

1 Like

Great idea! This is how setlists work in FourScore.
I guess current «setlists» in QC have to change name to «preset bank» or something like that.
It would also be great to be able to lock preset scrolling to one setlist in a circle with up/down switches. Let’s say you ise 3 presets for 3 different guitars. You don’t want to «stray» off by accident to other presets/banks «in the heat of the battle» live.

1 Like

That is exactly what I need. Simply put: set lists with shortcuts to presets that would be stored in another bank.
Like a computer…shortcuts :wink:


Oh, and NDSP, if you are working on this (which I hope you are :stuck_out_tongue: ), please take into account that if we move the original preset (the one that the shortcuts refer to), the shortcuts should be updated to point to the new location (so not really like a Mac/Windows/Linux PC, something a bit smarter :grin: )


Just stumbled upon the Setlist Feature from Fractal and it looks impressive!


Yea im all for this!

I think an excellent example of how this can work is actually in Arturia’s ‘Analog Lab’ plugin.

This gets my vote!

I also have a FM9 and I love this feature. Would be awesome if NDSP could do something similar!!!

1 Like

Just as a follow up, I’m sure it’s been mentioned elsewhere-- but a huge part of making this feature functional at all would be the ability to create and order gigging set lists in the app and have the device sync to the list.

I guess there are a few factors to this, but as a guitar tech, this is what I would need to make this functional, especially if I have multiple band members using their own QC:

  1. ability to connect app to device via Bluetooth or hot spot from phone. Bluetooth would be best-- i work tons of festivals where WiFi is unavailable and cell service can be bad
  2. Ability to connect one phone\app to multiple devices individually (not necessarily at the same time, but easily switch between them.)–again I’d like to be able to connect to edit devices for 3 band members with their own QCs
  3. Ability to quickly tell the QC to sync to the set list I’ve made for that gig, or have an option on the QC to have the device automatically sync to the latest set list on my app. Again, in a festival setting, with a 30 minute changeover, where I may not have the set list until 5 minutes before changeover, and may not have power for stage until 15 minutes before set start, being able to sync set lists quickly is crucial (unit boot time is a big issue here as well…)
  4. Ability to use app to set mode\state of device and edit mode settings, tying them to the set list. E.g. make sure all the presets in order in the set list start in the preferred mode, which would most likely be scene or scene\stomp hybrid for me, but there might be some songs where the artist would prefer just stomp mode, etc. Maybe it already does this, I’m just learning. Definitely have more thoughts on tweaks to the modes but that’s another thread.
1 Like

Fractal’s setlist implementation is already a step in the right direction, but unfortunately not thought through to the end. The limitation to 6 song parts doesn’t make sense to me here. This means that you only have a sound ↔ button connection at the end and still have to remember which part comes next in the song by yourself. And if a song has more than 6 different parts…bad luck. Without this limitation you could build the whole song in exactly the order you want to switch the sounds and then you would only need to press one only single button that always jumps to the next part. You no longer have to worry about which part comes next and where to find the button for the next part.

It would be so easy, but somehow usability doesn’t seem to play a big role with the developers of guitar effects devices.

I will never understand why people prefer to look for the right button among many, with the risk of hitting the wrong one in the middle of a song, instead of enjoying playing and the show on stage by pressing one and the same button to switch without thinking.

1 Like

I agree 100%! I have several tunes where I need to jump back and forth between parts as I cycle through the song parts - intro, verses, chorus, leads, outro, etc… It is all too easy to hit the wrong scene when a quick transition is required. That forces me to pay more attention to the footswitch label on the modeler than would be ideal. Especially when you use your modeler in hybrid mode.

Usually, I try to limit my scenes to four total so that I can have stomps on my bottom row. This means that if for example I have the verse on footswitch 1, the chorus on footswitch 2, and lead on footswitch 3, I have to jump back and forth between them as the song parts change and come back around.

Just wanted to add that if you have a switch to move forward through the scenes, make sure there is one to go back as well. Inadvertant double-clicks happen: grin: This brings up another interesting capability that could be added that would be awesome if you could progress through scenes sequentially with up and down switches.

With sequential footswitched scene cycling you could have virtual scenes. Virtual scenes would mean that you could still for example have eight scenes easily available while you were in hybrid mode. The virtual scenes would not require a foot switch assignment for each scene. The sequential movement through them would only require two of your footswitches (up & down) for all eight scenes, leaving the rest or your footswitches available for stomps, presets, one-off scenes, or whatever.

Yes, you need a back, of course. And on the other hand, as far away as possible a “Next Song” and “Previous Song”. It would always be good if the next patch or snapshot is anteased, so that you also know what comes with the next button press. I had built something like this with a Teensy and it worked perfectly. Only the programming of the SOngs and song structures was so complex that I no longer use it.

How something like this could look on the QC, I had built a year ago with Photoshop.


Sorry, but the song parts make things a lot more complicated than they need to be.
When you are in Scene Mode, you are only ONE click away from each song part, no unnecessary switching back and forth. Why do you need song parts in the setlist?

First of all, it is much more important that you can create a song list, with each song referring to a preset. Of course, several songs can refer to the same preset. These songs can then be used in one or more setlists. It is also important that the set lists can be easily sorted using drag and drop.

Then we’ll see.

1 Like

The idea is that you don’t have to think about which of the 8 possible buttons to press next. As soon as you have to think about where to press next, your attention is taken away from the actual performance. And the danger of pressing the wrong button is simply quite high.

In the end, everyone has to decide for themselves which method suits them best. However, the method that is safest for a performance and where you have to think the least would be if the necessary sounds are called up sequentially in the correct order via exactly one button (of course, you must not forget the back button, because you can also click one button too many by mistake) -< the less you have to think, the less is the chance to make errors.

As already written above. I had built myself exactly that once with a teeny and it was live simply a dream, no longer have to worry about which button I had to press when. But maybe you have to try it yourself before you realize how simple and easy it can be.

The point, after all, is to make things easier and avoid sources of error.

+1 for this essential feature. Current implementation makes no sense at all. It should be as easy as creating a playlist in iTunes: I don’t want to make a copy of my presets, I just want to make an ordered list that links to a library of presets.

(My trusty GT 100 with Boss Tone Studio had this functionality years ago)


I have a Fractal FM9 and the song/setlist feature is very handy when doing live gigs. It does have some limitations, but it works and prevents me from having to hunt for presets during a live show. It uses the “Pointer method” referred to above so you can leave the “Master” presets right where they are and just point to them. You can also “Point to” a specific scene in each preset. 6 “Scene Pointers” is enough for me for each song.

Their system has some limitations, but I would love to see Neural implement something like this. Preset (and capture) management is an issue on the QC with a lot of users and a feature like this would make that sooooo much easier. No need for making multiple multiple copies of the same presets in multiple setlists and trying to remember where they all are and which “Copies” have been updated or not.

This is the way…

1 Like

So how do we get this going?

Many thanks,

Robert Bushey
+44 7717 361 626

Good question… For starters, vote for this feature request at the top of this page. Beyond that, I don’t know. I assume by the number of votes for this (76 as I write), that there’s enough support for this idea that the Neural staff would be considering it or actively working on it. I am also assuming they are monitoring all these feature requests and at least occasionally reading these posts so maybe by expressing our opinions here we can help push things in the direction we want them to go…

Thanks. I don’t think I need to vote for it, I created it. I just want to know how we get them to implement it. :slight_smile:

Many thanks,

  • Robert

| 12tone
September 29 |

  • | - |

Good question… For starters, vote for this feature request at the top of this page. Beyond that, I don’t know. I assume by the number of votes for this (76 as I write), that there’s enough support for this idea that the Neural staff would be considering it or actively working on it. I am also assuming they are monitoring all these feature requests and at least occasionally reading these posts so maybe by expressing our opinions here we can help push things in the direction we want them to go…