Resolume Forum

I'm fairly new to Resolume, but experienced with Ableton and MIDI. I've been having fun exploring how I can trigger things in Resolume based on my live playing within Ableton. I've got various MIDI messages (both CCs and notes in different cases) triggering clips and effects/parms with no issues. Today I moved on to trying to map the deck switcher, and things got weird.

I am trying to prepare a set of 6 songs, and I'm using a deck in Resolume for each song's media. In Ableton, as I launch the first scene for the song, I've got MIDI clips sending notes to Resolume to (1) move to a new deck and (2) launch a clip (a background clip, for instance). Here's the situation and what I'm observing:

- 2 different computers, one running Ableton the other running Resolume. Audio/MIDI USB interfaces on both computers, if that's important
- Deck shortcuts are notes
- Clip shortcuts come 1 beat later in the Ableton MIDI clip, and are set for Target="This Clip"
- Clips I'm trying to trigger are set to "Normal" trigger mode (I use Piano mode elsewhere with other clips, but not the ones in question here)

I started slowly, mapping 2 different deck buttons and their initial clips. At first it worked! But as I moved on to map a third deck button and it's first clip, Resolume then began ignoring the clip launch shortcut (but responding to the deck shortcut). I thought maybe I had some sort of confusion between different decks and "This Clip" settings, so I redid everything with unique MIDI notes for every deck and initial clip. No change. Then Resolume began ignoring even the deck change shortcuts... I quit and restarted Resolume, and behold it began working again for a short time. Then, after a few song switches (triggering the deck/1st clip MIDI notes each time), it began to ignore the launches again. Then eventually, the deck shortcuts again. The behavior seems repeatable, but each time I quit/restart it's a different pattern of what works/doesn't work.

Worth noting that even when this weirdness happens with the decks, my other MIDI note mappings for clips/effects still work.

I've checked the MIDI coming in via the MIDI inspector in preferences, and it's all good (MIDI Note On/Off are there and recognized). I even tried using some MIDI effects in Ableton to force Note On to 127 velocity and Note Off to 0 velocity, just in case. That didn't help anything.

Tried more time between the deck selection MIDI note and the clip launch MIDI note, thinking it might be something related to switching the decks, but that also didn't help.

Have I found a bug, or am I doing something wrong?

Any help greatly appreciated!

Dig

Which Resolume version are you using?

The latest version of Avenue, 6.0.3

Still on a trial version, in case that’s important.

I've tried a lot of different things trying to get this to work. Seems clear that there's a bug.

Somehow, switching between decks with a MIDI shortcut eventually puts Resolume Avenue 6.0.3 into a mode where it will not honor the MIDI shortcuts to launch clips in that deck. At least, not MIDI shortcuts to launch the clip using "Normal" mode.

Another hint: If I use the "Clear Layer" button on the layer I'm using for these initial background clips in the decks, and THEN trigger the MIDI note sequence to (1) select a new deck and (2) launch a clip in that deck, it keeps working. If I do not use the "Clear Layer" button prior to triggering the sequence, it will quickly begin ignoring the MIDI shortcut to launch an initial clip in the new deck.

So:
- clear layer, then switch decks, then launch clip = works
- just switching decks, then launch clip = stops working after a couple of deck switches

Of course, I don't want to use clear layer between songs. Please help

Bump. Trying to understand if this is a bug or if I'm missing something? Seems to be a bug.

Could you send us your composition, midi preset and ableton project?
The media files are not needed.
Thanks!

Composition and MIDI shortcuts attached.

My Ableton set is much too large and complex to try to navigate for this problem. Suggest you setup a simple Ableton set with a single MIDI clip that sends the mapped MIDI notes for a particular deck and first clip to test this.

For example, a clip that sends Channel 9, MIDI Note G#4, and then Channel 9 MIDI Note G4, in quick succession (I was trying them 1 beat apart, at various tempos from 60 BPM to 150 BPM).

If it helps, here are the deck and first clip mappings in the MIDI shortcuts so that you can setup multiple clips to switch between decks and play the first clip. Switching between these clips, you should soon see that the clip launch shortcut fails.

Thanks, we'll have a look.

Thanks very much!