This continues to be an issue for me where I open a project that looked fine when I saved and closed it, but when reopened, the Triggers may appear to be wrong. When I open the Song/Part Triggers dialog, they are correct there and if I click in that dialog on each on, the main panel is updated to the correct values, but they likely will appear wrong again when I open the project the next day.
It seems like a cosmetic issue because when I click on a Part, the Timeline locates correctly to 3.1.1 in this example, even though the Trigger looks incorrect showing 2.4.1.
To correct the problem, I can click on the Trigger list on each line, collapse the Song, expand it, and then the main Window will appear correct.
It’s a bit random at the moment, Song Two is the problem in this one, but Song 1 was the problem when I first opened the project. I corrected that one, restarted, reopened it, and now Song 2 has the problem.
Tried to reproduce this quite a while, but to no avail. Created 4 Songs, 3 with 4 Parts each with different trigger times, keep the triggerlist editor open all the time, save, load, change some…all works as expected.
Would you have any receipt how to reproduce this from scratch (new project, add Song…etc), or a project that reveals this? Just the project file (vlsprj) should suffice, no audio or midi etc required. Thank you!
Thank you very much. It is much easier to fix a bug with a description like this!
Basically, the bug is purely visual. That is because Part triggers are stored (and restored) in seconds, not beats.
From that point of view, what’s missing is an update of trigger time display in both setlist and trigger list when the tempo is changed. We will fix that with the next version, thanks to your findings.
Now you will probably want to keep the beat positions instead. Triggers were initially designed to be linear time related (as opposed to tempo/beat time), for light control. However from a musical point of view, it makes sense to want the trigger beat positions to stay in place.
We will make this dependent on the display type. If the transport display type is set to beats (as in your case), triggers will be shifted to beat positions as displayed (which will change the seconds position), and vice versa.
Once more, thanks a lot for reporting!
You’re welcome Thank you for the description of the error cause and the perspective that in the future the triggers will be restored depending on the display type in this case.
I am getting a similar issue, but it’ s not merely visual.
When clicking those individual parts, they do not go to the correct sections in the songs; the triggers are off.
I imported a Signature track with the project, which incidentally works well as a visual for where the arranger track splits the parts and proves the parts are not playing where they should.
Some of the parts do not even have play icons next to them; see below:
… you said that you are working with an imported Media Project. Could you please be so kind to export your Cubase project and import the Media Project again. Is it still wrong? If yes, could you please give us access to your Cubase project (*.cpr). We don’t need the media.
Thank you Spork. It is still wrong. How do I go about giving you access to the Cubase project? I believe I attached it to this reply, but let me know if I need to do something else.
Thank you so much for your work. This must be frustrating process as you work through issues, but I am looking forward to this being fully functional and I have great expectations for it. So far, besides this issue, I can only think of one other thing that would be useful, and that would be transitions between tracks (continuous play) with possibility to fade, etc.
Yes, exactly. We used a program in a group I was in that allowed you to highlight as many songs as you want (consecutively) to play one after another. Then you can set another set of songs to do the same; multiple times throughout the setlist using different color codes. This allowed for breaks after each set of songs.
Thank you for the description of the error cause and the perspective that in the future the triggers will be restored depending on the display type in this case.
