I wanted to start off by saying this software has improved immensely in the 1.5 months I’ve been using it.
I sometimes still get crashes and I’m gonna start sending info each time it happens so this can stop happening. I feel it’s ALMOST stable enough to try live. I applaud the developers and appreciate your efforts.
Onto the possible bugs:
Firstly,
My external midi controller is sending a cc on midi ch4 that is assigned to the global video module (Gvm) Start/stop/rtz. It only actually works correctly if I take a series of steps a shown in the first video. For example, the project loads with the Gvm stopped. I should be able to send my command to start it, but it doesn’t respond until after I jump through some hoops.
Second;
Global video always starts and stops when starting or stopping a song. This is true in my tracks that contain midi to control the global player. The midi is firing every time play is pressed, irregardless of the midi information not being present in that spot.
Lastly, Software was stable for a while for me yesterday, and then after a while, it crashed to desktop. Here’s 2 crash reports.
What do you mean by that?
Chase Events will always fire the actual state, which is the last event before the start position (or locate position, if preference “Chase Events on Start” is off).
“What do you mean by that?
Chase Events will always fire the actual state, which is the last event before the start position (or locate position, if preference “Chase Events on Start” is off).”
What do you mean by that?
Chase Events will always fire the actual state, which is the last event before the start position (or locate position, if preference “Chase Events on Start” is off).
I unchecked chase events on start and the behavior is the same. Is there a way to not have it fire off midi that isn’t present in the spot it’s firing it off?
In this example I have a a midi cc at the start of the song to stop the global video, and the same midi cc at the end of the song to start the global video (assuming it was playing before I started the song). I have zero need for it to fire off the previous message from the beginning of the song if I start or stop in the middle of the song. I hope that makes sense.
Also, I had another crash. Was just rehearsing, sending a midi cc to “go to next song and play”, and at the end of one of the songs, crash to desktop. other than that, it’s been solid.
Thanks. Pls try again with the next version and report if it doesn’t fix it.
Thank you and I look forward to see if it works.
Did you guys happen to look at why I need to open the global video module, then go onto the monitor screen and press play and stop in the video module before it will respond to cc #'s?
I think this cropped up in another thread. I’m beginning to see a need for a MIDI “setup” sequence that is only ever executed when the song is selected (i.e MIDI chase ignores it). This is somewhat covered by the Layer Sysex option but that can be a bit limited, plus it’s also a number sequence and difficult to read. Why not add the ability to add a bar to a MIDI track that is only played on song select? Or a “play to here on load” option? Same for DMX.
If in preferences under MIDI, “Chase Event on Start” is deselected, everything in a Track on position 1.1.1 is send when selecting a song. But for DMX I wish this feature also.
That depends how you define “spot”. Chase events is (always) chasing the last state of all controllers older than (or same as) the current timeline position.
When “Chase Events on Start” is off, nothing is fired until started.
Absolutely, we see your point and will add a preference to disable chase events altogether.
