Page 1 of 1

Bug on Midi Mapping

Posted: Thu Jun 16, 2016 02:52
by Kadete
Hello everyone!

Everytime i restart resolume i lost my midi configuration on '*2' and '/2' bpm buttons

Midi Configuration:
Capture.PNG
Capture.PNG (13.77 KiB) Viewed 7730 times
After restart Resolume Avenue:
after.PNG
after.PNG (13.6 KiB) Viewed 7730 times
Regards

Re: Bugs on Midi Mapping

Posted: Thu Jun 16, 2016 08:37
by Zoltán
do you map composition midi map or application map?
for composition map you need to save the composition after mapping.

Re: Bugs on Midi Mapping

Posted: Thu Jun 16, 2016 11:40
by Kadete
ravensc wrote:do you map composition midi map or application map?
for composition map you need to save the composition after mapping.
Yes, this is on composition midi map.
I did save 3 times and restart to confirm the problem, the mapping over bpm (beats) stayed mapped.

This happen to all effects with a property in BPM Sync mode.

Re: Bug on Midi Mapping

Posted: Mon Jun 20, 2016 09:18
by Joris
Confirmed and ticket made. Thanks for letting us know!

Re: Bug on Midi Mapping

Posted: Tue Jun 21, 2016 16:49
by Kadete
No problem.

Another thing that i think is a bug is that souldn't be save midi deck/layer configurations in new preset of a effect.

If i reuse the effects on clips will have binding midi (my knobs are detecting) but i cant see on resolume midi configuration (layer/deck) since it was bind on different context.

Please confirm this, since i'm away from my PC right now.

Re: Bug on Midi Mapping

Posted: Tue Jun 21, 2016 17:01
by Joris
Can you write that one out in steps for me, please? Preferably starting from a blank comp and a fresh app map? Because it sounds like you just have some contextual shortcuts mapped for the active clip.

Re: Bug on Midi Mapping

Posted: Fri Jun 24, 2016 01:53
by Kadete
Joris wrote:Can you write that one out in steps for me, please? Preferably starting from a blank comp and a fresh app map? Because it sounds like you just have some contextual shortcuts mapped for the active clip.
There's a mix of bugs Joris

1. Add Effect, Map opacity parameter in Comp Midi, Save preset 'Dummy:
Capture.PNG
Capture.PNG (13.42 KiB) Viewed 7616 times
2. Add Same Effect, Map other(s) parameter(s) in Comp Midi, Save preset Dummy2:
Capture2.PNG
Capture2.PNG (14.57 KiB) Viewed 7616 times
3_1. Change Preset to Dummy:
Capture3.PNG
Capture3.PNG (13.76 KiB) Viewed 7616 times
>> You are kind of overriding the mapping when changing presets :?

3_2. Change Preset to Dummy on Edit Composition Midi Map:
Capture5.PNG
Capture5.PNG (12.15 KiB) Viewed 7612 times
>> This seems only to be visual bug, since it don't really save this midi

----------------------------------------------------

1. Clean Comp, Add Preset Effect:
Capture4.PNG
Capture4.PNG (12.12 KiB) Viewed 7616 times
>> My knob is detecting mapping, but i can't see it any mapping on the default preset on Edit Composition/Deck/Layer Midi Map :cry:
Edit: Option 'Reset to Default' resolved this


There's more problems but i can't explain :| i guess i have to clean all presets... :(

Re: Bug on Midi Mapping

Posted: Fri Jun 24, 2016 10:53
by Joris
I think this is a combination of false expectations and getting lost in the midi mapping maze.

False expectation:
Presets do not store shortcuts. Think of presets as a giant octopus. When you switch presets, the giant octopus just uses all its tentacles to set all the values of the effect in one go. The same way as you would do it with the mouse one by one, but at once. It's just a set of values that gets stored and recalled, nothing mare.

Composition shortcuts are applied on a specific parameter in a specific location. When you change the shortcuts, it doesn't matter what preset of the effect you are in. You are assigning shortcuts for the parameter, and the parameter doesn't change when you change the presets.

Shortcut maze:
Between Comp mapping, App mapping Deck focus and App mapping Layer focus, it's very easy to assign double shortcuts.

Especially App Layer focus is tricky. It stores shortcuts contextually. This means it doesn't remember a specific parameter like Comp map does ( for instance Hue Scale of Hue Rotate of Clip 10 on Layer 3 ). It just remembers it will control parameter 7 of effect 9 in the Active Layer. If you don't have 9 effects in the Active Layer, it won't do anything. If effect 9 only has 6 parameters, it won't do anything. The moment you add a ninth effect to the Active Layer, all of a sudden it will start working.

Worse yet, if you delete the ninth effect from Layer 1, you won't be able to find the Active Layer shortcut, because Layer focus is mapped on Layer 1. This doesn't mean the shortcut is gone. It will still control the 7th parameter of the 9th effect on the Active Layer. You just won't be able to see it.

Rules of thumb when it comes to creating shortcuts:
- Use App map, Deck focus for all of your mappings.
- Map the Dashboard dials and assign effects to the dials. Don't map effects directly.
- Only use App map, Layer focus if and only if you have the exact same set of effects on every layer or clip.
- Use Comp map if and only if you want to control a specific parameter on a specific clip all the time.
- Don't mix and match mappings if you can avoid it.

Re: Bug on Midi Mapping

Posted: Fri Jun 24, 2016 14:07
by Kadete
Joris wrote:I think this is a combination of false expectations and getting lost in the midi mapping maze.
Indeed
Joris wrote:Rules of thumb when it comes to creating shortcuts:
- Map the Dashboard dials and assign effects to the dials. Don't map effects directly.
This isn't so simple to follow, normally i use.:
Layer 7- 9/10 - Fx Layers
Layer 6 - Over Logo
Layer 5 - Logo
Layer 1-4 : 'Background'

I want to Mirror or Hue Rotate everything except the Logo
I have to comp map the effect and copy to the desired layers to achieve this.

---------------------------

Thank for the response, i will try to follow the other rules :D