Tom Holland

Hi. I have this delay patch I'm using for an audio plugin. When I listen to it in FL Studio, the audio that has already been fed back once becomes distorted, like white noise, when it gets fed back again. This doesn't happen when testing it in Max. This is pretty much just the patch from the delay tutorial video but with a bit more stuff.

Hi. I have this delay patch I'm using for an audio plugin. When I listen to it in FL Studio, the audio that has already been fed back once...

delay-patch-creating-distortion-in-daw

does [set stop] for [list set stop] work in max 8? it does not in max 7.

Set stop just stops any signals from being delayed and isn't part of the issue as I noticed the distortion/white noise before adding it to the patch.

i was just wondering that it works at all, because [set] is not an object and until now (in max datarate) lists in objectboxes must have started with an integer to be correctly interpreted as [list] object.

however, i suspect something with load order of parameters, did you check for that?

Could you elaborate on what I should do to test how/if that is the problem? I'm not that familiar with it, nor why it would be different in a DAW vs in Max.

i am not firm with RNBO and i have no idea how you connect those parameters to the outer world, how you use it in max, or how you build your VST, locally or with the cycling servers? i only looked at the rnbo patch as regular max patch in v7 to see what you got.

however a host program does a whole lot of things with a VST when it is loaded, mostly asking queries, but eventually also triggering all nonhidden parameters.

you could try to add all kinds of visual controls such as numberboxes or meter~ and make them visible, maybe you find a certain spot where something something stops working.

I don't see how meters or numberboxes would help with anything since in RNBO everything is perfectly fine and working correctly.

Delay patch creating distortion in DAW