MSB in layers and saving songs (may be bugs)

[OleganB]

1. The MSB bank number in the layer is passed to the instrument when I change it manually, but when I reload the project, it is not passed to the instrument until I manually switch it. (Tested on Sylenth1).
2. When I save a song, the groups disappear in mixer when I load it into another project, and the tracks lose their connections to the layers and instruments.

[fkalmus]

@OleganB

When I save a song, the groups disappear in mixer when I load it into another project, and the tracks lose their connections to the layers and instruments.

Layer's input devices are not saved in song [2.2.54]

ports are managed by the project. There is no context (different project) to restore those.

[musicullum]

@OleganB

The MSB bank number in the layer is passed to the instrument when I change it manually, but when I reload the project, it is not passed to the instrument until I manually switch it. (Tested on Sylenth1).

Whenever a Part is activated (selected), its Layers send MSB, LSB, and Pgm Chg.

Could be you have preferences “MIDI/Track Controllers” activated. In that case it may only get sent once and then not again until it changes.

[OleganB]

MSB Bank is lost when saving “Layer Controls Map”. LSB is saved, but MSB is reset after saving and opening the project. This happens regardless of the value set in the layer itself.

[musicullum]

@OleganB

MSB Bank is lost

What do you mean?

• new project
• add Layer
• open cc, set bank msb values on, 13, on…
• save, load, all good.

What do you do?

[OleganB]

1. I open menu Layer → Layer Controller Map
2. I change MSB value (for example 3) and LSB value (for example 4)
3. I save the project and open it again.
4. I see value 0 in msb and my value 4 in LSB

Any values in msb are reset to 0 after saving and opening the project, but other values are fine. I have found a temporary solution to this problem. I use LSB and map it to MSB, as LSB data is saved when I close the project, but this is not a very convenient solution.

[musicullum]

@OleganB

• I save the project and open it again.
• I see value 0 in msb and my value 4 in LSB

I do exactly that with a new project, and see value 3 in MSB (and 4 in LSB).

Note that Bank Select is also set in Layer, possibly you changed it there before saving?

[OleganB]

I started with that. At first, after restarting the project, the msb value was not transmitted to Sylenth1, so I started looking a way to send this parameter to the tool without losing it. In the Layer Control Map, I saw that after restarting the project, the MSB was reset to 0, but… everything is working fine now, I haven’t figured out what happened yet, but msb is saved and transmitted. If the situation repeats, I will take a screenshot.. Maybe updating the versions of the program helped.

[OleganB]

I think I’ve figured out the reason for the unstable switching of programs and banks. The issue is that if I change the program or bank value to the same value, nothing is transferred to the tool. For example, if I have program 3 set in the layer, but the vsti is set to program 4 when I open it, and I select program 3 again, nothing is transferred to the tool. I need to change the program number to a different value before the setting is applied. It would be nice if any change to the program, even without changing the value itself, would transfer the parameter to the tool. The same goes for banks.

[fkalmus]

Can this relate:

[2.2.64] Controller Tracking and Program Change

For both of your projects, tried output to Virtual Midi Out 7 and MIDI Monitor to Virtual Midi In 7 to observe output. With, or without Track Controller setting, it transmits all Program Changes just fine, no matter which Song is selected in which order. In fact, without Track Controllers enabled, it sends the Program Changes twice, which appears to be a bug (it locates twice when a Part is selected, and Chase Events chases twice, provided “Chase on Start” is disabled). But that should not caus…

[OleganB]

@[2.2.64] Controller Tracking and Program Change

For both of your projects, tried output to Virtual Midi Out 7 and MIDI Monitor to Virtual Midi In 7 to observe output. With, or without Track Controller setting, it transmits all Program Changes just fine, no matter which Song is selected in which order. In fact, without Track Controllers enabled, it sends the Program Changes twice, which appears to be a bug (it locates twice when a Part is selected, and Chase Events chases twice, provided “Chase on Start” is disabled). But that should not caus…

Doing like you say.

[musicullum]

Cannot quite see what you want to show. “Same value” will never do anything with any value whatsoever (at least when selected from a menu), it is rejected immediately after the menu closes sayin “nothing changed”.

But you appear to mean something different. Pls use Halion Sonic which is delivered with VST Live, set its “Options” “Program Change” to “GM” and try the same, then describe step by step what you do, it’s muche easier than trying to figure out what a video is supposed to show, thanks.

[musicullum]

Just found something…hold the line.

[OleganB]

Thank you!!! It is about a multi preset, it is the settings inside it, it should not be affected by the general volume fader midi

[musicullum]

You lost me.

Anyway, checked again, if the mixer channel is set correctly (that was our problem here), it all works as expected. To repeat, selecting a value from the menu in any item with menus (not just program change) will reject setting it to its current value. Nothing will happen if you select “2” from a menu whose value is already “2”.

[OleganB]

Sorry. Last message was sent to the wrong threat. It was about Halion and its volumes.

[OleganB]

I’ve found a solution for myself - I don’t use bank and program numbers at all. VSTI saves its parameters in a layer, and program numbers alone are not enough for high-quality control. It’s possible that there’s a conflict between the saved state of the instrument and the bank and program numbers being transmitted. I’ll create a separate layer for each part without specifying the bank and program numbers. For a physical instrument, simply specifying the bank and program numbers is not enough. My Yamaha sends entire MIDI messages when I switch presets, and I need to send the entire package to the instrument to set the desired state.

Thank you for your reply!

[Spork]

… to jump in here : We have improved the MSB/LSB/PGM communication from the Layer to a Plug-In. Please give it a try with the next Pre-Release (2.2.28).

Thank you,
Michael

[OleganB]

Thank you very much!!!