Trigger Messages won't work with Engaging Presets (Poly Ample Example)

Morningstar Software Bug Reports and Feature Requests
1

I’ve been building out this bank to be able to easily cycle between all of the presets on the Poly Ample. So I took the example provided by Morningstar for the Nano Cortex and applied it to the Poly Ample. This was essential because the Poly Ample does not have a screen so it can be tricky to remember which preset number corresponds with which Amp Model and the Nano Cortex Example seemed the perfect solution, and the results were excellent.

Nano Cortex Example

I then decided to extend the features provided in the Nano Cortex example to jump to the different categories of presets on the Poly Ample. There are a total of 7 different categories, each with 8 different presets that represent 8 different Amp Models that fall in that category:
Categories:

  • Clean
  • Crunch
  • Destroy
  • Classic USA
  • Classic UK
  • Gen X
  • Bass

So I created a preset for the MC6Pro that will cycle through the categories for you, responsible for changing the corresponding scroll counters and Msgs in all the relevant MC6 Pro presets so that everything is accounted for when scrolling through the amp models. The only problem I was having was that I couldn’t get the label to update when cycling through the different categories. I found a means to get that to work, however now I have a new problem that I’ve noticed…

You see this situation of having 7 categories containing 8 presets each requires a lot of MC6 Pro messages in order to manage, so I’m utilizing 3 pages in 1 bank in order to make the whole cycle process feel seamlessly integrated. The problem is when I’m changing pages, I have to handle quite a few things in order for that to work such as the relevant scroll counters, preset rename messages, etc. My solution to this was to utilize the Trigger Messages Action to trigger a few messages which should reset the labels when leaving a page so that when I cycle back, everything is as expected.

Unfortunately in my testing I have seen that specifically these messages do not get executed… I wonder if I’m running into the below issue where I simply need to disconnect the web editor and then it will work but if not then perhaps someone has some insight into what may be causing this to happen?

I’ve provided the bank if you want to throw it into an editor and take a look at it or even try it out on your own Poly Ample!! Please if you have any ideas on what may be happening then please reach out with your thoughts!

MC6PRO_Bank_PolyAmple.json (90.6 KB)

2

Card created

This is an automatically generated message

A Trello card has been created for this request: Trigger Messages won’t work with Engaging Presets (Poly Ample Example)

3

If it helps in illustrating how this Bank configuration works, I made a spreadsheet to quickly explain what each message does with each bank :slight_smile:

4

I thought I made complicated interfaces in the MC6!

As I’m thinking through what you’re trying to do here, though, maybe there’s a simpler way to get the result you want? Ultimately, you just want to have easy access to every Amp Model in an organized way, right? So why not just use 7 footswitches, each scrolling through the 8 models in a category? To visually know what’s going on, you can add them all to a toggle group, and whenever one is pressed, it is toggled on and the others are toggled off. You’d probably be able to bypass needing a bunch of different scroll counters (you don’t even REALLY need one at all). For ease I’d probably also set up an 8th footswitch as “reset all” and then just call that footswitch on my other presets.

It’s definitely worth it on our end to check to see if the message triggers are firing correctly, and James has created the relevant Trello card. But just from a user’s perspective, I’ve found that if I can reduce the number of cross-preset messages I send, the better things work.

2 Likes
5

I really appreciate the thoughtful response and to your point, you’re probably right that the less complicated I could make things the better it’s going to work in the end haha

Thinking this through, I can totally see how this would work and may try to set it up in a separate bank and drop it in this forum to share in case anyone else is interested. In the meantime, I’m going to see if there is someway I can get my current approach to work as to keep the name of the Amp Model in one place on the MC6 Pro’s screen.

Again thanks for the thoughtful response as I genuinely love MIDI programming and all the different approaches that come with solving these sorts of problems :slight_smile: