Splitting incoming signal

[ustk]

@pcs800 just insert a container.split then add as many chains as you want inside it to split the signal in parallel paths

Side note: for L/R it's a container.multi

[pcs800]

@ustk Thanks for that information. I have the following, which works, but there's a large latency on the chain with the pitch shifter. Is there anything that can be done to eliminate the latency?

[ustk]

@pcs800 any pitch shift algorithm will necessarily bring latency. It need to be compensated in the other chain using a delay node and a converter sample->ms
Now how much you need to compensate for this particular pitch node I don’t know…

[pcs800]

@ustk If I add delay to the other one, then the plugin will cause latency in the audio it's applied to in the daw. No?

[Lindon]

@pcs800 ..and so you must make your plugin report its latency to the DAW...

[pcs800]

@Lindon Yes I have discovered that. I don't know how to find the right latency in ms or how to get the plugin to report it. I will look.

[pcs800]

@Lindon So as suggested by @ustk I have added the converter Sample>ms and it is showing 95.9ms, that's great. But how do I get the plugin to report that to the daw?

[pcs800]

@pcs800 Like this?

Engine.setLatencySamples(95)

[Lindon]

@pcs800 yes

[pcs800]

@Lindon In the interface onIt?

[ustk]

@pcs800 yes, from any script I guess.
Be careful though, this function takes samples as parameter, not ms, so mind your conversions

[pcs800]

@ustk Adding Engine.setLatencySamples(95) to interface onit, compiles without error and the plugin doesn't seem to have latency in the daw.

[Lindon]

@pcs800 well 95 samples would make hardly any difference at all... whats the measured latency of your plugin?

oh hang on youve already said:

95.9ms, that's great. But how do I get the plugin to report that to the daw?

Go read what @ustk said above.....