I forgot is even simpler (no need for an array)
[read foo.wav( | [soundfiler] | | | [print stuff] | [print n of samples]
--
Mensaje telepatico asistido por maquinas.
On 1/28/2022 3:36 PM, Lucas Cordiviola wrote:
You can get that info with [soundfiler]
[array define myarray]
[foo.wav( | [read -resize $1 myarray( | | [soundfiler] | | | [print stuff] | [print n of samples]
--
Mensaje telepatico asistido por maquinas.
On 1/28/2022 3:31 PM, Miller Puckette via Pd-list wrote:
Hi PA -
Are you doing stuff that "soundfiler" doesn't? If so, it would be better to add to the soundfiler object than to add a new object with its own name.
cheers Miller
On Fri, Jan 28, 2022 at 06:17:21PM +0000, Pierre Alexandre Tremblay wrote:
Hello again
So I was missing an object that is quite useful when dealing with audio files in batches. Attached is the ugly file in progress to read (with [file]) the header of audio files and demingle it to get the number of channels and number of frames and sampling rate… what the Max object [sfinfo~] does.
Now I notices that the pd API offers me the headers to recode it in C - so I have 2 options here
- I don’t bother anyone and I coder it as fluid.sfinfo
- I code it as [sfinfo~] and make a PR and pray that the dev gods
pick on it and in the meantime I just include my PR version.
I looked in decken and couldn’t find that string (soundfile, sound file, etc) so I’m pretty sure it is not there.
In all cases this is a very useful object to have. I offer my pd attempt in sacrifice to the people who want to have a laugh. It kind of works… but that ‘extended’ format (80 bit float anyone?) is a pain to detangle :)
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list