Robin Schmidt

looking at the doc of juce::AudioProcessor: https://juce.com/doc/classAudioProcessor i can't find any function like isSynth() or something that which i could have overriden for this. do you know or can you...

hmm...strange. i have no idea. do you have the same problems with your other plugins or is this specific to prettyscope? if so, you could try to figure out, where...

so, they will all be recognized only as instruments and not as effects? hmm...the question would be, what exactly determines, how logic categorizes a plugin. what in our code and/or...

toolchain actually *is* an effect anyway. at least, i don't have the "is a synth" checked in my jucer file (and never had)

btw. - i started a new project. i finally want to write my dream synth for toolchain. a semimodular architecture with 4 sources (with vector-mixer), a dual filter (also with...

perhaps from the new flexibilized runtime module instantiation facilities (which i'm currently working on). ...oh...and polyphony handling.

2D LFO is interesting...but perhaps difficult to integrate into the mod-system. i need to think about, how this can be done. from the user's perspective, it perhaps makes most sense...

> I think it's mainly an interface problem. No need to make teh mod system more complicated. well, you haven't written the mod-system - so how do you know, how...

when i upgraded, it was to the then up-to-date official release version (5.2), i.e. the one that you are directed to on the juce website

strictly speaking, it will have finished only when the signal falls soo low that it will be flushed to zero (by our denormal flush-to-zero code) - which can take a...