in version 2.2.15 the event chase (with Chase Events enabled and Chase Event on Start disabled in the Preferences), seems not to load correctly any CC/Program Change present at the timeline location accessed by clicking on a Song Part other than the current one.
When opening the project, Layer 1 of Song 1 presents the instance of HALion Sonic with a Main Volume equal to zero, apparently coherently with the contents of the MIDI Song 1 CC track and the chase function
Let’s click on Part 1 of Song 2
We immediately notice that, in Layer 1 of Song 2, the Main Volume of the Padshop instance is equal to zero, and this differently from what was programmed in the MIDI Song 2 CC track
Let’s try going back to Part 1 of Song 1 and check the Main Volume setting: the Main Volume turns out to be set to the maximum possible value and this would seem to denote the incorrect application of the chase
On the contrary, moving to a new Song, on a Part that is not the first one, would seem to lead to correct chase operation.
It is not equal to zero, it is “NOT SET” which means its volume control is ignored. The Layer Volume is a seperate entity and has no function when set to “NOT SET”.
With “Chase Events” on, and “Chase Events on Start” off, take Halion Sonic instead, and open its mixer page where you will see that it receives all Volume controls well.
sorry, unfortunately I think I explained myself poorly, the Volume Control of the Layer isn’t the subject of the issue.
I’ll try to explain myself better by repeating the steps to replicate the issue, but with the help of screenshots and red rectangles to highlight the objects of the issue.
When opening the project, Layer 1 of Song 1 presents the instance of HALion Sonic with a Main Volume equal to zero, apparently coherently with the contents of the MIDI Song 1 CC track and the chase function
We immediately notice that, in Layer 1 of Song 2, the Main Volume of the Padshop instance is equal to zero, and this differently from what was programmed in the MIDI Song 2 CC track
Let’s try going back to Part 1 of Song 1 and check the Main Volume setting: the Main Volume turns out to be set to the maximum possible value and this would seem to denote the incorrect application of the chase
Of course, don’t mind me pointing this out if the issue description is still unclear.
PS: I reiterate that the issue only affects events located at the beginning of the first Part (or, equivalently, at location 0001.1.1 of the Song) and only when the Song is accessed from another Song; in all other scenarios the event chase seems to work correctly
This is a problem of order of tasks. When you select a new Song, transport is located to zero forcibly, which gathers chased events, and if “Chase Events on Start” is not enabled, sends those immediately.
But at that time, shared Layers of the newly selected Part are not yet activated, thus they have not yet connected their MIDI Inputs, and so all those precious chased events go to the current Part (which ignores them, as it is already de-activated).
Long story…we now force locate a second time after the new Part (and its Layers) are activated, Check it out with the next version. And thanks for helping with the project!
