specific integration with preset manager

trogluddite · 1 Apr 2012

You can yse the "Before Preset Change" and "After Preset Change" wireless outputs from the Preset Manager for this. They are timed so that they always happen before and after all of the parameters are changed, so can be used to drive a blocking mechanism. Here's a mod to your schematic using that idea - seems to work when tested here.

tester · 2 Apr 2012

Thanks. Now a small question about trigger killer. I noticed, that Param primitive inside preset also has two nodes for before/after change trigger. I assume they perform similar functions as the ones in preset manager module. Am I correct? I.e. if so - then what is the practical difference between using the pair set from preset manager and "param" primitive inside the preset? Timing?

trogluddite · 2 Apr 2012

I would have to check, but I seem to remember that there is a subtle difference - IIRC, the "change" outputs of the preset parameter are triggered by any kind of change (e,g, VST automation etc.) and not just preset changes from the manager.

trogluddite · 2 Apr 2012

Confirmed - in fact, it's not a "subtle" difference at all! - any change to the preset value, including just wiggling the GUI knob, sends triggers from the extra "VST Parameter" primitive outputs. There is a precedent in other components for this (e.g. MIDI split, Integer loop etc.) - the extra trigger outs can be useful because their processing order is always predictable, whereas messing around with links can be a right pain for changing the trigger order in ways you don't notice.

tester · 2 Apr 2012

Okay, thanks.