Hi Devs! Just tried the new track by track selection of chase behaviour.
Chase on locate is perfect for midi CC’s and Programchanges to automate external devices/plugins, but the chase works only if the events are inside the same clip (container).
To automate program changes on amplitube here in the pic below, i created single clips containing only the required midi program change, so my midi track is full of single event clips, the chase on locate should work “trackwise” finding the previous midi events even if not inside the same container clip.
In the image below, locating after a program change but still inside the “clip” send the correct program change to amplitubes, but locating after program change and outside the clip, don’t work …
Yeah… I would like to avoid it because clip separation helps me identify where the guitars sound change are!!! And because each clip have a name, CLEAN, DISTORT, SOLO etc, and help me both identify which sound should be loaded and to copy paste the clip where and when I need it. For now I’ll try to extend the first clip and overlapping it till the song end and see if I still can see the changes while make chase on locate working !
Oh I meant rather extend clips like “legato” just sligthly touch next event. But I see your point! (Also I guess you can’t replace theese small clips with “empty” PART-LAYERS to fire the same CC’s)…. But in reality you hit PLAY and chasing is not necessarily, as u simply play over the “Prg.Ch.-clips”, or?
Exactly, while performing I hit play and it all goes well, but when rehearsing, if I locate in the middle of a song the programchange is not sent so the sounds on guitars ar enot changed, i need to go back to the clip event and fire play to have sound changed… it’s just aplus being able to locate and have istantly the right sound on guitars
@ciro1983811
Belive or not… the 17000 EUR GrandMA3 (lighting desk) is working the same way, if you don’t pass the time-point, the CUE won’t be chased (backwards), need roll back before the “pinned-position”. Meanwhile experts can modify this behavior to something different but they say, that has another disadvantages, so rather staying with “default”) so that is way more advanced already with VSTL…
