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!
I noticed a fix for Chased Events in the new Version History document, hoping it would be the solution for the issue that is the subject of this topic, but the issue still seems to be present in version 2.2.17.
Not true here. Volume in Padshop is 127 as programmed in the MIDI track.
I do exactly as you said, with the project provided. When I select Part 1 of Song 2, then open Padshop editor, its top right volume control shows full. Chase events is activated, Chase Events on Start not.
I may have understood why you behaved differently there: I think you had not enabled the preference Controller Tracking also because I had not given this indication.
In fact, it seems that setting the Controller Tracking preference also affects the chasing behaviour in the Song access scenario on Part 1.
To make sure I put you in the same condition as me, this is the screenshot of my Preferences for the MIDI tab:
Sure.
When Controller Tracking is enabled, a MIDI device output filters (discards) controller events which it has already sent exactly like so. That does happen in your case; the same controller on the same channel with the same data is sent to the same output of the same device
Recommendation is to disable Controller Tracking.
Unfortunately, the solution provided, i.e. using different MIDI devices (in my case, virtual ports) and disabling Controller Tracking, does not seem to solve the problem or else I am missing something in the chasing logic.
I propose a new version of the project for testing
Upon opening the project, Layer 1 of Song 1 presents the HALion Sonic instance with a Main Volume of zero, apparently consistent with the contents of the MIDI Song 1 CC track and the chase function
Click on Part 2 of Song 1: the HALion Sonic instance presents the Main Volume as 50%, consistent with the content of the MIDI Song 1 CC track and the chase function
Move now to Part 1 of Song 2 and immediately after to Part 1 of Song 1: the Main Volume of the HALion Sonic instance presents itself with the Main Volume still at 50%, and this differently from what was programmed in the MIDI Song 1 CC track
The Preferences setting used for this test, in relation to the MIDI tab, were:
Sorry, cannot reproduce any of what you say with your new project.
Whatever I do, and in whatever order, Song1 Part1 shows Halion at volume 0, Song2 Part2 Padshop at 50% and Song2 Part1 Padshop at 100%, same settings as yours.
Set both Halion and Padshop to open at activation to see the results immediately.
I confirm that by enabling the opening on activation of HALion Sonic and Padshop the issue does indeed not arise, but this does not resolve the issue.
It’s really strange that the issue doesn’t occur in your test environment and, to make sure that you reproduce all the necessary steps correctly, I prepared a video:
Let me know if, with the latest versioned version of my test project and the help of the video, you succeed this time in replicating this issue, which systematically occurs to me.
