LiquidSonics: Synced values for pre-delay or echo don't work [solved]

[zerocrossing]

Today, it makes sense:
When the DAW is running, it's sync'd to the DAW. When not, it's sync'd to internal settings you can adjust.

Your proposal:
On startup, it's sync'd to internal settings.
When the DAW running, it's sync'd to DAW
After running, it's syn'd to the DAW's state WHEN THE DAW LAST RAN (not the specific value currently set in the DAW, but whatever the value happened to be last time it ran and updated the plugin).

That is a horrible design. It still doesn't match the DAWs CURRENT STATE, only last run. It has different behavior between startup resting state (use internal) and post having ran resting state (whatever the DAWs value was the last time it was ran).

Imagine this. Reverb internally is set to 120. I run a project, set's tempo to 80bpm. I open a new project set to 120. Reverb runs at 80 (tempo of last project ran). I check my project, it's 120. I check settings, it's 120. But reverb is giving me 80? WTF?

Not a good solution.

I agree, that today's behaviour is more consistent in it's wrongness, than my proposed solution.

But since I do work on the stopped DAW very often and in comparison change the tempo very seldom in a project, my solution wouldn't pain me so much and thus it would be the better one for me. Don't know, if I can speak only for myself or if more guys would think like that.

Anyway, this discussion is pointless and academic, because since it's perfectly achievable, that a plugin syncs to DAW-tempo, also when the DAW is stopped, it should just take the correct set value. That's the common expected behaviour from everyone, I dare to say.

That's what most software I've experienced does.

[SamDi]

LS has provided new versions of all plugins with this issue solved. Wow, that was really fast - great company. Thank you Matt and to the team!

[sqigls]

legends

[Calagan]

Trustful people they are. And beautiful reverbs they do.