Resolume Forum

ok... thinking some more... now I see the issue i guess...

VJair has 1 long clip with several cuepoints... ?!

My theory only works for one cuepoint per clip... otherwise you need seperate keys to trigger the same clip on different cuepoints... maybe possible, but not that convenient i see...

hmmmm... Probably not possible while you can map 1 control to several parameters... but not several controls to the same parameter... (maybe via diferent MIDI channels?)



[edit] now reading your comment.. you're right indeed...
[edit2] i managed to map 2 cuepoints on the same clip with a combination of application and composition mapping... but that's a really ugly solution with no real advantages i think]
[edit 3] can't let this one go... I edited the "contextualKeyboardShortcuts.xml" and was able to map more than 1 key to the same cliptrigger... now assign those same keys to different cuepoints... Have to run now.. will come back later.

VJair... did you read my [edit3] from the post above?

I guess you should be able to use this option... It is a bit of searching in the xml file, but it's all there. (my advise is to start with this on a new composition with one clip on each layer as a starter! (mapped to an exclusive/unique key, in my case numpad 5, which is easy to recognize inside the xml file)

Save that compo/keymap and then start editing the xml file.

I just copied a block with the -in my case numpad 5- key, and pasted that 5 times, and then, in the pasted blocks, changed the "5" to 6, 7, 8 and 9, etc.. .. I guess you get it right now

Once finished, save the xml, and restart Avenue.
Now, when you try to clear the keymap on that specific clip (try it!!) you see that it's stacked with as many keys as you pasted in the xml file... in my case I had to clear it 5 times to get rid of the 5 keys mapped to that one clip!!

Once you edited the clip-trigger keys in the .xml file, the cuepoints can be "learned" from the mapping menu inside Avenue.

I hope you can understand my explaination... it's a bit of a workaround ofcourse...
I know it's not the most perfect solution, but in the end it will work i guess.


On second thought.. with my first solution (one possible cuepoint per clip) you also should be able to only load 1 clip.. but load that one clip several times, on several positions, with DIFFERENT cuepoints.. in the end, you can use the same file over and over again and just change the cuepoint on clip level for every clip
So you don't have to cut and make all different clips for all the cuepoints you want.

I would suggest the use of MAX, processing, … with OSC (bundled). Store the clip trigger command just before the cue point cmd and then send the package. I think this should work.