Sophia Poirier

Thank you @mrbfrank! They shall be reborn...

This seems to be a new side-effect of the workaround added to address #19 #29. Removing the workaround resolves this issue, however that first and more serious issue still requires...

Oh and I should have mentioned: reverse and ad hoc varispeed modes are not yet implemented for TOMSOUND.

...and then after I wrote that comment about how math that's too hard for me and how maybe accumulating rates in a map could be an option, I thought about...

rebased on main for the latest fix there (I found that sometimes when modulating "distance" a bunch on a stereo instance, the right channel DSP core might see a newer...

It is great getting your thoughts and experience with this so far! Some replies and other thoughts inline: > Thanks for trying to fix that glitchy thing. Any of these...

I was just thinking about the Bezier curve suggestion, and applying that to _ad hoc varispeed_, but then I realize that the tricky thing would be determining the `alpha` value...

I would also guess probably not too much work (we use relatively little platform-specific code, and the underlying GUI framework that we use supports Linux), however it is not work...

To provide some code that I am working with that demonstrates the problem: ``` class SettingsDataPackage final : public VSTGUI::IDataPackage { public: SettingsDataPackage(std::byte const* inSettingsData, VstInt32 inSettingsDataSize) : mData(inSettingsData, std::next(inSettingsData,...

VST3 support would also provide a viable option for cross-platform session sharing.