Key-tracking with custom tuning messes up plugin state

[Anastázius Kaejatídarján]

Hi, I like to use custom SCL scala tuning files with vital. If I make a patch that relies on key-tracking, such as key-tracking a filter for white noise to do some physical modelling type thing, it will work beautifully at first. The filter frequency will respect my custom tuning.

But, if I save the ardour project, close it, and return to it again, it's a different story. The filter will behave entirely unlike it did — often a nasty noisy mess — until I reinitialize the patch. I needn't even reset the tuning or reimport my SCL file or anything, but I do need to reinitialize the patch. Weird, right? I wonder if you can reproduce this.

If I save the patch as a vital-internal preset, then when I open ardour and vital is misbehaving, I can reload the vital-internal preset and everything will be in order once again. So I believe that there is a discrepancy between the state vital saves internally to its own presets and the state vital gives over to the DAW to save and reload.

I will try to remember to update this issue with screenshots and audio later, but my house has construction right now and I don't have ready access to that PC.