If I want to change (ex via a slider) the difference in time between When an audio signal goes In to my patch and When it goes Out (esp. to dac~) a delwrite~/delread~ (or vd~) can be used to do the job?

So a delay line...

Is a way to create a time-differential between when my computer "hears" a sound and when it "sends out" its processed audio signal,...so to increase the delay time is to increase the "loop" length.

Sort of like a (artificial) controllable latency?

If yes: awesome.

If no:

How do you do that?

(As I am building a patch that transforms what it hears (and it does not cause feedback) and I want to be able to control how "much"/long it listens to itself before releasing its transformed result back out).

rem: what I am doing does Not cause feedback (via midi transformation). So being able to control how long the loop is would be awesome.

Thanks, in advance.

Peace through knowledge.

-s

@svanya Not sure I understand because it seems you answered your own question at the beginning......... using delwrite~/delread~ (or vd~)
Do you mean outside of Pd?....... I don't think so because you write about your "patch".
So it was just an analogy.

You want to do stuff....... turn the audio into data (midi) for a certain time........ and then use that data to produce audio and send it to the [dac~]
But at the same rate that the audio came in at........ sort of the same "tempo".

So what you need is a data store with a read cursor that moves at the same rate as a write cursor with a settable gap between the two......

That is as far as I have got.
But this is a first thought.

Write your data into an array at a set rate with a metro and a counter that sets the index.
The counter should stop counting as it reaches the max indexes required for the delay and start putting data into the same index...... sounds bizarre I know, but stay with me......

Just before it writes again to that last index...... shift the array to the left....... read the first index and remove it.
From here on the metro reads and removes the first index and writes the last index with new data..... forever.
I know it looks back to front but I think I am correct.

all_about_arrays.pd David.

[tabwrite will be increasing the length by one index every time it writes...... cannot yet get my head around (I have not even tried) how that will affect the patch above...... but I don't think it will.
See you back here if I have a better idea (before someone else?).
Because it's not certain that the operation above would be fast enough.

The maxlib library has [fifo] ...... first in first out...... and it's length can be set...... but how many floats can it store? I tried it set for 10000 and it seems to work.......
There's one in ceammc and zexy too I think....... doing the same?.....
David.

@svanya AAaaaargh......... but possible with [fifo]
Here you go for up to 10 seconds of "data latency".......... delayed.pd

1ms or less data sampling.
It will loop through the air from speakers to microphone of course....
David.

@whale-av
Thank you, for all of this.
It is going to take me a while to digest it. So I will be in touch later about how much I understand .

Thank you, in advance for your help and input.
I really do appreciate it.

Peace through sharing.

-s