Speaking of bangs doing the job, I wish [tabread] had a right outlet that banged when you gave it an out of bound index. I was trying to make a vanilla version of [tabdump] and that would allow me to know when I've read the whole table without needing to know it's size explicitly.
On Oct 1, 2013, at 6:00 PM, pd-list-request@iem.at wrote:
From: Jamie Bullock jamie@jamiebullock.com Subject: Re: [PD] writesf~ time to flush to disk…? Date: October 1, 2013 5:26:49 PM GMT+08:00 To: Thomas Mayer thomas@residuum.org Cc: pd-list@iem.at
On 1 Oct 2013, at 09:27, Thomas Mayer thomas@residuum.org wrote:
On 30.09.2013 17:22, Jamie Bullock wrote:
Could an outlet be added to writesf~, outputing the number of samples written to disk?
The parent patch could then use this outlet to establish when writesf~ is ready to receive another "open".
I like the idea, but the outlet could just output a bang, when it is done, otherwise how do you determine that writesf~ has written all samples to disk?
I meant that it should just output the _total_ samples written after it has flushed to disk. This would be consistent with the behaviour of [soundfiler] I believe.
But yes, a bang would do the job.
best,
Jamie
Dan Wilcox @danomatika danomatika.com robotcowboy.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-01 18:47, Dan Wilcox wrote:
Speaking of bangs doing the job, I wish [tabread] had a right outlet that banged when you gave it an out of bound index. I was trying to make a vanilla version of [tabdump] and that would allow me to know when I've read the whole table without needing to know it's size explicitly.
so far i know of are two options:
tablesize at runtime (without requiring the user to provide it manually)
more powerful replacement for [tabdump]
most compiled objects within zexy are there because i haven't found a way to implement them in vanilla (some are there because a vanilla implementation ist simply to slow; and the rest is there for vaniyt reasons)
fasrm IOhannes