cfichter wrote: ↑
Wed May 15, 2019 14:59
Zoltán wrote: ↑
Wed May 15, 2019 10:39
It will leave some buttons lit up from the previous deck, and it won't always populate all the programmed buttons from the new deck or composition I selected.
Which buttons/UI items are these which don't update properly on deck switch?
Let's say I have two decks for two different songs. One of them only has 5 clips and the other deck has 20 clips. If I go from the deck that has 20 clips to the deck that has 5 clips, a bunch of the buttons that were lit up on the deck with 20 clips remain lit when I go to the deck with 5 clips.
I believe this is the intended operation for Resolume.
When switching between decks, the currently selected clips will remain active until you trigger a new clip from the deck you have switched to. You could turn the clips off before switching decks by triggering a layer router or something if you need to switch them off before changing decks. Or you could assign opacity for specific clips to individual faders or knobs on the apc.
Also, make sure you are assigning midi via the Composition Midi map and not Application midi map. This way, you can use multiple instances of one function on the apc across multiple decks that won't overlap.
This is how it works for me and I'm running an akai MPK261 or LPD8 to do my midi mapping.