Playhead position MIDI mapping

[zooloo]

I found a behaviour in resolume that I think is erratic.
If we take a longer clip, and selected an in and out point on a clip (for example selecting a 5 second section from a 5 minute video) and MIDI mapped playhead position of that clip, insted of mapping a whole 0-127 range onto the selection (giving us access to pretty much all frames of the selection for scratching) , Resolume insists on mapping the range onto the whole length of the clip - dramaticaly reducing mapping resolution. In my example (5 seconds selected from 5 minute long clip) resolume would only allow me to pick 3 frames from the video via CC, clamping all other values (so for example with those 5 seconds in the midle of the clip it would only move the playhead in response to values of 64,65 and 66, clamping values between 0-64 and 66-127).
I believe in resolume 2 playhed controller was correctly mapped to the selected range rather than clamped. Is there any reason behind that new behaviour?

I remember back in v 2.4 I used to use 'scratch'/'playhead position' mapping a lot, playing out custom LFO waveforms as CC from a sequencer, for example a sine wave which would give me a nicer, smoother ping-pong effect synchronised to the beat. I know you have BPM sync these days but I really miss that level of control ( I used to carry a RM1x with me, playing out MIDI for playheads for my layers)

Also I think for parameters that are set to Timeline, with a range selected (and timeline animtion paused), midi mapping range should be automatically set to match the range selected for the timeline (rather than requiring going into composition map mode for each range change (which also requires stopping the sequencer if it is sending any control data to avoid changing the mapping by mistake)).

That way one could play out a bunch of pre-recorded MIDI clips with CC's from Ableton, and change the ranges on the fly by adjusting timeline ranges, without going into mapping edit mode. While in timeine mode for a parameter with a narrow range selected, MIDI vaues are cropped/clamped anyways, so there is no use for keeping the ranges seperate.

I hope this makes sense.

[Joris]

Thanks for the report.

It sounds like this is indeed not desired behaviour. The range should scale with the in and outpoints. I've made a ticket for it. Keep in mind, it's going to be a while before we can get round to this.

Btw, I love how this has been the behaviour since Res 3, released in 2008, and you are the first one to ever mention it.