bug report: SFZ player instances

[antoniaz]

I'm currently using MU.LAB 2.5.7 Free, and in my typical session I usually
include MULTIPLE instances of RGC:SFZ VST player, one instance per rack.
What I noticed in this version (as well in previous ones)
is that sometimes the current "PROGRAM" setting got lost
inside one or more of the SFZ instances I created.
It also seems that this wrong behavior occurs more often
when stopping and restarting sequencing (playback) from MU.LAB buttons
(Play, Stop, Rewind, ...) but it's not that clear and reproducible.

Thanks in advance for any hints.

[MuTools]

Normally, a VST plugin is like a black box to MU.LAB.

MU.LAB does not have anything to do with the inner workings of a VST plugin.

Besides this 'theory', it's difficult for me to evaluate what could be going wrong as i need more details...

[pljones]

is that sometimes the current "PROGRAM" setting got lost
inside one or more of the SFZ instances I created.

If MU.LAB resets the playback engine and tells all the VSTs to re-initialise, then this may happen - but not just stopping and starting playback, I wouldn't have thought.

The only other thing -- check in the list editor that you don't have "extra" Program Change messages you didn't expect. You may be leaving SFZ in an unintended state when you stop and rewind. (MU.LAB won't look back and forth through your sequences to work out what state you expect SFZ to be in -- you need to make sure it's set correctly.)

Oh, and any Bank Select messages cause SFZ to reset to Bank 0 it seems! (A pain...)

[antoniaz]

Thanks a lot. I will check first for extra Program Change and Bank Select messages. In fact, when I observed the issue I was using imported MIDI sequences not composed by myself.

[MuTools]

Aha, that increases the chance that there indeed are some program changes.

Use MU.LAB's Event List to see in full detail what's in the sequences.