Does anybody know of a sample looper that uses soundfiler or readsf~ and writesf~ instead of arrays?

I am currently using arrays for my 16 track looper. For saving them to file, I was going to simply copy the array to disk, but it would be ideal if I could loop the sound files instead of the arrays. This would also free up a lot of memory. I'm currently running this on a 4gb rasberry pi, but it would be great if I could get this down to a 1gb pi so other people might be able to use it easier.

From what I can tell, the main problem with .aiffs is the save and load time. My program already uses an input buffer and an output buffer around the looping array, but not for purposes of giving the array time to save and load. It is also constantly reading and writing from the same array. I don't think I can do this with files, right?

Anyway, if anybody knows of an example program out there that successfully uses buffers to account for saving and loading times -- AND / OR -- that allows unlimited overdubs to the loops -- it would save me a ton of time trying to figure this out from scratch.

Thank you

overloop on the organelle uses sound files instead of arrays. https://www.critterandguitari.com/organelle-patches/overloop

@Tombot7 you could also save the arrays with the -k flag, if you always use the same loops (would still use more memory than readsf~ but is more flexible in some situations).
you can overdub them indefinitely, but you can only recall the last saved state.

@seb-harmonik.ar I'll take a closer look at organelle does it - but I if I recall it doesn't actually use overdubbing, you just create new loops out of old ones, right? That still might give me a clue on how to buffer file loading, since it still has to solve the problem of immediately playing the files when you have just finished looping.

@Jona what object would take the -k flag. I'm not familiar? Is this soundfiler? Tabwrite? I'm having trouble locating it. I do like the idea of auto-saving my arrays though. And I don't mind only recalling the last saved state... This sounds very promising.

@Tombot7 its [array define -k $0-something]. Same with text [text define -k $0-something].
Edit: you need to reload the patch to recall the saved array state. So maybe you still need an extra copy to reload it without reloading the patch. Not sure if reading from an array .txt file is faster than reading an aiff. (see the help file for array define).

@Jona I read up on it and see what you mean about saving arrays inside patches. I appreciate it but it's not a great fit for what I'm trying to do. Thanks though