Resolume Forum

hello, new user with questions regarding midi feedback. i am using a launchpad and have programmed a controller in Bidule to use with Resolume Arena. active, playing clips light up the corresponding LEDs on the launchpad -- great.

however, there seems to be no way to distinguish empty slots from slots that have media loaded. without this, the launchpad is a much less useful tool, and has far fewer visual cues to help you navigate.

i have searched the forums and found the following comments from Joris, mostly ~2012.

Joris wrote:We're aware of the demand for this. There a few issues that prevent us from implementing this as a feature though, one of which is that every controller requires different midi velocities to change colors...
...
Resolume's midi out behaviour is basically 'what comes in, goes out'. So when you have controls mapped to the active clip or layer, these will be sent out when you change the focus. Sending out loaded clips in a decks is not supported. This is primarily because every controller has a different protocol for led colors, and we can't make separate implementations for every controller out there.
...
We're in the process of seeing what controllers are popular among our users, and making specific templates for them. If you could describe specifically what functionality you'd like to see, we can take that into account.

one, those of us whom are routing midi to and from LED grids can find the device specification and make sure that the right color velocity gets sent. there are dozens of free vsts and other methods by which we can control velocity, so please don't worry about that.

two, i haven't yet seen any resolume midi controller templates. is this still happening? i've seen a bome's midi wrapper for the APC -- i would do something similar in Bidule, if only slots reported loaded media via some MIDI indicator (velocity X instead of full NOTEOFF -- again, let me worry about correcting the velocity to conform to my device specifications)

thanks for your time, great software.

Since most controllers seem to use velocity to control LED colors on buttons, the plan now is to let the user define the on and off velocity values, as well as the loaded/playing velocities for clip triggers, during the mapping.

This is still only an idea, so for dedicated LED feedback, you will still need to resort to Bomes / Processing / OSC wizardry for the time being.

I know it's annoying, but I'm afraid we don't have the time to make this a priority at the moment.

Since most controllers seem to use velocity to control LED colors on buttons, the plan now is to let the user define the on and off velocity values, as well as the loaded/playing velocities for clip triggers, during the mapping.

i think that's a good goal, thanks for the insight.

This is still only an idea, so for dedicated LED feedback, you will still need to resort to Bomes / Processing / OSC wizardry for the time being.

i have been looking at the OSC messages sent from Resolume, but i do not see anything indicating whether or not a slot contains a clip. am i missing this message? i haven't worked much with OSC but this feature is important enough for me to learn.

I know it's annoying, but I'm afraid we don't have the time to make this a priority at the moment.

i understand that creating a full solution that accommodates every user is laborious. note, however, that an easy intermediate solution for more midi-capable users would be as follows. this could be an off-by-default option so as not to interfere with others' setups.

* if emptyslot is clicked and then navigated away from, NOTEOFF is sent to that learned note. (current behavior)
* if slotcontaining clip is clicked, NOTEON is sent with 127 velocity while clip plays (current behavior). when clip finishes, NOTEON is sent with 1 velocity (request).

this allows midi-savvy users to filter out these noteons with velocity 1 and reassign the velocity layer to whatever their controller requires. this can be done so easily with midi vsts, max msp, bidule, etc. this would effectively solve this issue altogether for me.

i am overwhelmed by the amount of OSC messages being sent from Resolume. i copied the OSC log that is sent on load of a demo project (1 layer, 2 columns to shorten the message). i am looking for some indication of whether or not a clip is empty. could i get some direction as to what messages am i looking for? i'd post the results but it's 60000 characters+

so looking for anything to determine whether or not my slots are empty....

so looking for anything to determine whether or not my slots are empty....

could i get a holler on this issue? is there an OSC message that indicates whether slots are occupied or not? i've gone through resolume's osc output line by line to try to figure this out but can't determine which if any message i'm looking for.

once i get this info i can easily use osc > midi in bidule to create a color/brightness based layout for the launchpad.

when switching decks, you get /layerN/clipM/... messages for some parameters including the clip name.

hmm, i see, i also see that they don't update when you rename the clip manually. even after saving/reopening the project, the osc message contains the original filename rather than the clip name. that's OK - this might work though, thanks!

Joris wrote:
This is primarily because every controller has a different protocol for led colors, and we can't make separate implementations for every controller out there.

O.K., but if you have a closer look at the current controllers there is not much of a choice as long as you would like to have a maximum output for RESOLUME. At the moment that would be the Akai APC 40 Mk2: enough faders, knobs and pads to control the most important RESOLUME-parameters.
Very important > a template must have the ability of scrolling horizontally and vertically (clips and layers) as the APC 40 is limited to a 5 x 8 matrix.
So why not start with this implementation? Thank you ...

If you would read the thread a bit further, you will see that our current idea is the following

Since most controllers seem to use velocity to control LED colors on buttons, the plan now is to let the user define the on and off velocity values, as well as the loaded/playing velocities for clip triggers, during the mapping.

This is blanket solution that will allow custom color feedback for every ( as far as I know ) controller with LED color buttons.

A clip trigger grid is related to this, but a completely different function. Options for clip trigger grids and the problems we face with them are discussed and explained here: viewtopic.php?f=6&t=11876&p=48664&hilit ... rid#p48664

since this thread started, i have successfully used a combination of Puredata and Bidule to get clip feedback on my launchpad. as mentioned elsewhere, i use an 8x8 resolume grid to correspond to my launchpad.

it looks great, and really helps me visualize what's going on. it was a lot of work, but it finally pushed me to learn a bit about OSC and Puredata, both of which will be very useful to me down the line (i've already benefitted from the OSC knowledge -- my lauchpad LEDs now respond to REAPER OSC to show helpful status).

i'm not completely done with the patch yet -- i need to use Resolume's MIDI feedback to indicate which clip is playing (this is currently routed to nowhere) without then blanking the status light.