Page 1 of 1

midi mapping to video opacity

Posted: Tue May 09, 2017 04:13
by Glide
Hi all

I've mapped some midi to the video opacity of layer1 but it seems that you cant map different midi channels to each layer.

I hope I explained that right

I was hoping I could map seperate midi channels/values to each seperate layer so I could manipulate each layer on its own.

However it seems that you need to use a single midi value and then select the layer you wish to change the opacity of.

Is there away around this setup?

Re: midi mapping to video opacity

Posted: Tue May 09, 2017 15:57
by Joris
When you enter Application Midi map, switch the focus from 'layer' to 'deck' in the bottom left of the interface.

Re: midi mapping to video opacity

Posted: Thu May 11, 2017 02:11
by Glide
Thanks Joris

Will check it out

Appreciated

Re: midi mapping to video opacity

Posted: Sat Jul 13, 2019 08:00
by kammycakes
Hey folks,

I'm new to Resolume and am performing a show using my visuals piped through Resolume. The visuals will be controlled via chaotic and random MIDI messages coming from a Midi Controller that is connected to a living plant. The living plant is sending velocity data to a midi controller (custom) and then coming to me via Resolume.

I'd like to trigger the visuals based on the range of CC data from the MIDI messages. Is there a way to trigger visuals based on any midi data that comes in between certain ranges? 1-40 = visuals a, 40-87 = visuals a + B and 87-127 = visuals a + b + c.

When I look at the midi it, it's very sporatic and I'd like to pin it down and apply it to opacity and nice transitions between visuals.

I hope this is clear! :)

Re: midi mapping to video opacity

Posted: Sat Jul 13, 2019 12:33
by edwin
There is no functionality for this in Resolume itself. So you'll need a 3rd party tool that can 'translate' your MIDI input and forwards it to Resolume.
You could write a processing sketch for this (https://processing.org/) or use a tool like 'Bome Midi Translator (https://www.bome.com/products/miditranslator#).

Re: midi mapping to video opacity

Posted: Sat Jul 13, 2019 17:53
by kammycakes
I'm receiving MIDI CC and CTL messages when I open preferences. When I attempt to map these to a clip it jumps around because the input is random. Please see attached.

Re: midi mapping to video opacity

Posted: Sat Jul 13, 2019 23:14
by Zoltán
Do do the actual mapping with random messages like this, switch off the Midi inputs in preferences, go to edit midi shortcuts, and right click on the highlighted item you want to map.
Then select Create CC shortcut, or Create Note shortcut, and select the CC or note your'd like in the shortcut panel.
Exit mapping, enable the midi inputs back, and your shortcut should be working.


Re: midi mapping to video opacity

Posted: Sun Jul 14, 2019 00:41
by kammycakes
Thank you, Zoltan. However, I'm having some interesting Resolume midi handling issues when doing that.

When I map a CC from my midi controller to a clip -- it does not trigger even though I midi mapped it to the clip. Instead, Resolume seems to only be processing Notes "Types" -- Channel 80 and Notes (C#, D#). Please see the attachment.

I'd like to have it read and map the Value. The number indicated on the far right of the Midi Preferences Input Table.

Thank you again.

Re: midi mapping to video opacity

Posted: Sun Jul 14, 2019 02:03
by kammycakes
To further clarify, when I follow @Zoltan's instructions, it seems to only listen to Midi "Type" numbers and or notes. Instead, I want it to read "Channel" and "Value" in the midi message tables to I can correlate this with Opacity, Color of my clips.

Re: midi mapping to video opacity

Posted: Sun Jul 14, 2019 11:57
by Zoltán
To clear up a bit, one CC is a single Controller Channel. It can send you values from 0- 127.
There are a lot of Controller channels you can use, looks like CC80 is what you get the most data from.

As Edwin said, launching a clip with a range of a CC is not possible. If you map a CC to a clip trigger, it will trigger once it receives a value higher than 0.
To launch clips with CC-s again, like you have mapped with cc44, 54, 64 in your screenshot, the CC must return to 0 again before the clip will be triggered again.

The approach you try with the Connect specific clip shortcut, and the single CC80 would be what I'd recommend following, instead of mapping every clip to a specific CC.
That will give you 127 clip slots in the layer that can be triggered.

If you want to launch based on the range like you mention, value 0-20 clip1, 21-40 clip2 etc, that's not possible natively.
You can either do a translation in a third party app, which will give you a lot better control of what will happen,

or duplicate your clip1 to column 1-20 into a layer, set the clips to relative pick-up: https://resolume.com/support/en/video#playmode-away
This way if you get values int he range of 0-20 on CC80, your clip should appear like playing continuously.
Downside is that if you do the same with clip2, and you get a value 20, then a value 30, clip 2 will play where clip 1 in column 20 left off.

Once you got the clip triggering figured out, you can map other Controller channels to clip or layer opacities.

The randomness of the data might not be your friend here though.