I'm working for little musical and stage productions and I really love the options this nice piece of software gives me, but I'm always a bit disappointed about how many workarounds I have to build to get an easy rundown for a show, that simply triggers scenes and timelines one after another with simple transitions.
There are two problems/bugs that might be fixable and would make my productions much easier:
TIMELINE LOADING TIME
If you trigger a timeline it takes a few moments to load – I do understand that, but this means that I can not use the “solo buttons” option as it is intended. The scene I used before cuts or fades off and I have to wait for the timeline to load. The worst case is a few moments of pitch black stage. And even if I use the “fade out”-option on the button before which might make it smoother: once the timeline is loaded the running fade-out is ignored and everything jumps hard to the start of the timeline.
Maybe it is possible to technically wait for the timeline to load in the background and then handle it like scenes that dissolve nicely with the corresponding channels.
NO MIDI OUT ON STOP
When a timeline runs into its STOP marker all associated buttons go off, but the MIDI out command of the button is not send. The LED on my launchpad stays on. With a scene-button that has a “number of loops”, the same thing works perfectly.
I think the same problem affects the “chase page”-feature as well: If you only use scene-buttons in a “chase play”-page it works like charm. But if you use timeline-buttons the software triggers the timeline, but crashes afterwards before it even reaches the STOP. I understand that it might be a problem for the software to get the end of a timeline, especially if it has no “STOP” - but I hope this is not a serious problem to solve.
And as we're talking about the chase-feature: I don't get it why it seems so hard to implement a cue-feature based on that chase-option. All there has to be added is a trigger to go on after a button has reached the existing “pause at end” option. It seems to me, that if I want to use a page as a rundown I can already do that for 95% - the only thing missing besides the problems described above is a GO-button and the internal logic to repeat loop-scenes and just trigger the next scene if the “number of loops” is set in the scene properties!
I know that most things aren't as easy as they seem from the outside
but maybe some of the suggestion help to make the software even better!Best regards from Germany!
