I might have it all wrong, but this way I was able to do gap-less playback on older machines:
created readsf~
[readsf~ 2 *all bytes of the file*]
first open the file via [open file.wav(
and then go anywhere with:
[open file.wav *some-onset*, 1(
Mensaje telepatico asistido por maquinas.
On 10/20/2017 12:09 PM, Lucas Cordiviola wrote:
Well is useful because if you preloaded everything to the RAM you can instantly move to whatever onset.
OTOH if you didn't preload, it will be slower to move from an onset to another because the hardrive has to go and look for it in the file.
I guess you can see it as a [tabplay~].
Mensaje telepatico asistido por maquinas.
On 10/20/2017 11:55 AM, Alexandre Torres Porres wrote: so it kinda behaves a bit like soundfiler, hmm, interesting. And how would that work in detail? Still unclear to me.
thanks
2017-10-20 12:47 GMT-02:00 Lucas Cordiviola <lucarda27@hotmail.commailto:lucarda27@hotmail.com>:
You can create an internal array for [readsf~] so you can have preloaded a lot (or all) of the soundfile and the jump to any point with no gaps. Something like that.
Mensaje telepatico asistido por maquinas.
On 10/20/2017 11:40 AM, Alexandre Torres Porres wrote: Hi, I don't get what "buffer size per channel in bytes" means or does for readsf~
any help?
thanks
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list