You can use [timer] to measure the duration between starting to read and when it outputs a bang.  If it's equal to the duration of a single block-- and if your soundfiles are all larger than that-- then you will know there was an error.

-Jonathan

On Monday, May 19, 2014 6:25 PM, patrice colet <colet.patrice@free.fr> wrote:

Hi pd-list,

  when [readsf~] couldn't read a soundfile it throws a dsp error message
to console.
I would like to monitor which file is erroneous *without using stderr*,
is there a way to do it?

For the moment the only way i've found is about modifying d_soundfile.c,
but I'm not sure it is worth to do it, so I'm looking for advices before
putting fingers into source code.


_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list