Run from a cue list + test triggers

[Wibs]

Hi,

Let's assume I have 16 timelines, which I would like to group into 8 sets each set is two timelines. E.g. set one is 1 and 2, set two is 3 and 4 and so on.
I want to add a DINA-DR2-LITE with 8 port triggers. One port per one set. How can I create timeline cue lists?

• When I press port 1 for the first time, the first timeline in set 1 starts playing

• When I press port 1 again, the next timeline in set 1 starts playing

• When I press port 1 again, since there are not more next timelines, timeline 1 starts playing

• When I press port 2 for the first time, the first timeline in set 2 starts playing

• When I press port 2 again, the next timeline in set 1 starts playing

• When I press port 2 again, since there are not more next timelines, timeline 1 starts playing

• When I press port 1 again, the first timeline in set 1 starts playing

and so on.
So, the logic is: when in same group - start next, when in another group - start first in group.

I would like to accomplish this with timelines, as this is easier to create.

I've noticed in the trigger list there is a "next step in scene". Does it apply only to the paint block?
Also, I would like the timeline to pause as soon as it starts playing - as in to get a "hold at end" result, not have it looping.

Ideally, I would like to test the triggers in the office without a controller, instead of going on-site and trying to figure this out there. Is there a way to simulate triggers?

Here's the OneDrive link to the setup I have with 4 sample timelines.
https://adamestonia-my.sharepoint.com/: ... Q?e=JFwNRE

[TomHat]

Hello,

Terribly sorry for the late response.
In ESA Pro 2, timelines within the same scene cannot be played separately in StandAlone mode. When you write the scene into the device, it's turned into a list of steps, which is then played by the DMX Device (in your case, the DR2-Lite). So at the end of the programming process, it no longer matters what type of block you are using, as they all eventually turn into steps in the memory.
As of now, there is no easy way to test port triggers, but we are currently working on that for next versions.

Regards,