In the very first reply, XLColdJ asked “Do you have “All MIDI” selected for the track, or a specific MIDI device?”. This appeared to refer to the track INPUT and seemed irrelevant.
However, I can now confirm that things work fine when OUTPUT is set to a specific MIDI channel but is in error when set to “Any”. Thanks guys for narrowing this down further. I hope this helps the developer resolve things. Clearly it is an error.
The temporary workaround for me appears to be unchecking “Chase not limited to Part Boundaries”.
I cannot readily edit many song projects that all have a special track and part intended to initialise all MIDI channels for things like PAN (and is therefore set to output to “All”).
And it will set a number of Native Instruments and Arturia instruments “Cuttoff” value to zero and you’ll be sitting there wondering why no sound is being played by them.
(1) When the original MIDI part is copied into a MIDI track in a new project, the pan values are correct.
(2) When the original MIDI track is exported to a track archive and imported into a new project, the pan values are correct.
(3) When the original MIDI track is imported into a new project using “Tracks from Project…”, the pan values are incorrect.
(4) When the original MIDI track is duplicated within the original project, the pan values are incorrect.
Therefore the issue likely lies within the original project structure itself.
Thanks ASM. For clarity, in these tests is the output MIDI channel for the track set to ANY (errors) or a specific channel like 1 (works correctly)? You can switch between these to see it working and not working.
Thanks, we know ANY does not work but a specific channel does. For clarity (I’m getting tired!), it would be interesting in one of your “correct” tests to try ANY to see if it then fails and in one of your “incorrect” tests to try channel 1 to see if it then works.
I am understanding you have it working with ANY selected on the track in all of your 4 tests including the good ones….interesting.
I just exported the track to an XML, imported to a new project and it did not work correctly for me (your test 2)? The event sets the PAN but clicking stop after the part sets PAN full right.
I also tried your test 1 and it didn’t work for me.
EDIT: Support request re-opened and forwarded to the developer I’m told.
I am very disappointed that Steinberg has closed my support request. I have insisted it be reopened and that this forum thread be referred to. It is a bug, NOT TO BE IGNORED.
Their reply was:
”Excuse the very late reply!
I am not sure what you were trying to achieve by using CC10 (Pan). However, if you want to use HALion’s internal pan, it is sufficient to enable Read (R) and Write (W). The correct track will then be activated automatically. (screenshot is attached)”
I responded as follows:
”Please reopen this support request. It is not solved at all. Indeed, it has been discussed in the forum and verified by other Cubase Pro users to be a bug.
I already said this is what I do to initialise a project before the first bar of a song. I set all channels to a certain pan and other settings too.
I want one part that resets pan and other settings on all MIDI channels. I do not want to have to rework my library of old projects. The bug is setting pan to 127 instead of 64 and needs fixing,
Please escalate this matter. “
FYI, the bug will be solved in with the next maintenance update.
The issue went away when disabling MIDI > Chase Events > “Chase not limited to Part Boundaries” in Preferences, this could be used a workaround for now.
An irritating further update from Steinberg and my response:
Steinberg:
I have got an update by the developers which is:
“The user does not need to change the mentioned preference from above but should make sure that the MIDI track with the CC data is set to a specific channel - and not to “Any” in the Inspector”.
My response:
Please update the developer…..No No No !
Read the forum messages. I recognise it works when a single MIDI channel is selected. It does not when ALL is selected.
It used to. I have very many songs that have one part containing CC values to initialise all MIDI channels. It is not feasible for me to go thru all these songs and reconstruct that part into 16 separate parts just because Steinberg has introduced a bug.
Be reminded that Pan does reset for the correct channel. However, it resets to 127 instead of 64.
You have already advised me the bug will be resolved in the next maintenance release. Please confirm this as I am unsure why we are having this further discussion.
