Totally agree. There’s a list of basic info in the WAV/AIFF headers that is already parsed when reading that could simply be dumped out via a list/message.
-------- Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Nov 5, 2015, at 4:00 AM, pd-dev-request@lists.iem.at wrote:
From: IOhannes m zmoelnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Date: November 4, 2015 at 5:29:15 AM MST To: pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at Subject: Re: [PD-dev] sound filer samplerate outlet?
On 2015-11-04 07:17, Dan Wilcox wrote:
to simply output the samplerate out of a right outlet to compliment the sample length from the left outlet?
in which case i would suggest having the 2nd outlet output a *message* that also contains the property-name. e.g. [samplerate 44100, frames 1000(
and probably extend that to all the info that is readily available anyhow: [filename /full/path/to/foo.wav, channels 2, ...(
fgnasdr IOhannes
On Thu, 2015-11-05 at 13:08 -0700, Dan Wilcox wrote:
Totally agree. There’s a list of basic info in the WAV/AIFF headers that is already parsed when reading that could simply be dumped out via a list/message.
+1
And number of channels would be good, too.
Roman