This was raised 18 days ago as support request #740987 but I’ve received no response at all.
I have provided a Cubase 15 test project with just 1x part containing 1x CC10 (pan) event for Halion channel 1. This is a very simplified version of what I would do to initialise a project before the first bar of a song.
Looking at the mixer page in Halion, the pan is set correctly when the event is encountered but moves far right when stop play is pressed. If stop play is pressed within the part, pan remains the same. If stop play is pressed after the part, pan moves far right for no apparent reason.
Also, manually editing the CC10 in the List view (values of 0, 20, 64 and 127) causes immediate incorrect behavior in Halion.
I understand that prior events can be followed but this panning far right must be an error!
Just moving the cursor manually will trigger incorrect CC messages–you don’t even have to play, or stop. If you move it anywhere within the event, it sends the value 64; if you move it to somewhere past the end of the event, it sends the value 127. In both cases, the Position value is incorrect (0:00:00:000).
The issue here is MIDI Chase Events. When manually moving and releasing the playback cursor, with MIDI Chase enabled, a MIDI event (e.g. MIDI CC 10) is searched for towards the beginning. If it is found, its value is output.
The error in C15 lies in the empty area following the MIDI part. Here, the value 127 is output instead of 64 (as defined in the event). In C14, the value 64 is correctly output, independent from the position.
The disadvantage without MIDI Chase is that manually adjusted controllers (e.g. modulation wheel) are not automatically set to the correct value recorded in the track when playback starts somewhere after the event.
Thanks guys for confirming that 127 is sent incorrectly instead of 64. I agree that un-checking “Chase not limited to Part Boundaries” seems to resolve the issue. However, I am unaware of the implications and confirm there seems to be a reset value error here.
Aside from the fact that it’s an obvious bug in C15, disabling the Chase not limited to Part Boundaries setting can at least prevent the output of incorrect MIDI Controller & Expression values outside of parts.
I think it is some error with the project. If I recreate the set up, 1 midi part with CC10 at 29 it behaves as expected. I checked using midi insert midi monitor. Your project sends out CC10 127 when clicked beyond the part, mine sends out CC10 29 everytime I click in empty space.
Tried 2 times with create empty project from hub and even more times with your project.
I also created this project as a new test project however I copied very little (the part or event) from my other old songs. I wonder if we can identify the difference between my test and yours.
Once we find any difference I would need to correct (work-around) many old song files…
If you do get the same results, I think it is impossible to fix the old projects. It is not in the visible part. I will try the same with a fresh part started in C14 and then open in C15
Another interesting observation that still needs interpretation: If you set the MIDI output channel of the track from “Any” to a channel number (1-16), the correct pan value is output.
AAAAAAH that is the trigger, mine was set to Channel one. As soon as I set to any I get the same behavior in C15, not in C14. So a bug or an unknown new eh function lol.
