Loading and playing instrument with DSP chains leads to a warning

When you load an instrument and immediately play it on a keyboard, a warning appears in the instrument browser. The warning disappears after you stop and resume playback and does not reappear until you load another instrument into the slot.

How to reproduce:

  1. Load an instrument (e.g., Electric Red).
  2. Play any note BEFORE the instrument’s audio preview finishes (this is the most crucial part).
  3. The warning appears.
  4. Stop and then restart playback; the warning will be gone.

If you wait for the instrument’s preview to finish before playing, no warning will appear.

image

I think that’s normal behaviour. Seems you play notes for the same instrument in two or more different tracks. When using effect devices directly in the instrument’s effects tab, this warning appears, if you set notes on more than one track for the same instrument that has instrument fx chains and the instrument’s track routing is set to “current track”.
As far as i understand, the effects only can be handled by one single track and triggering notes from a second track at the same time can cause weird effect issues. For example, if you use an instrument that uses effect chains directly in the instrument (not track effects) and you trigger the first note on track 1 and a second note a bit later in track 2, it can happen, that e.g. the instrument’s effect tail will be cut by the triggered note of track 2.

To solve this change the routing of that instrument from “current track” to only one single track number (e.g. track 1 or track 2 etc.)

This is what i understand and i also made this experience with cut effect tails when triggering the same instrument from 2 different tracks if the instrument uses effect chains.

If I understand you correctly, I can interpret it as the preview playing on one channel and the note played via the keyboard playing on another channel. Wouldn’t it make sense, however, for the warning to disappear the moment the preview ends?

The warning doesn’t break anything, but it isn’t helpful here either, so it indeed should be removed. I’ll see what I can do here…

1 Like