<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div>So (donc)</div><div id="yui_3_16_0_ym19_1_1487765452774_6861"><br></div><div id="yui_3_16_0_ym19_1_1487765452774_6949">What are uniform parameters of a soundfile? Only these are necessary to enhance soundfiler. <br></div><div id="yui_3_16_0_ym19_1_1487765452774_6981"><br></div><div id="yui_3_16_0_ym19_1_1487765452774_7140">1) Channels is primary - an audio file can be any number of channels, but the soundfiler object needs to know in advance how many arrays to write to. This is non-negotiable i.e. an absolute fact.</div><div id="yui_3_16_0_ym19_1_1487765452774_7254"><br></div><div id="yui_3_16_0_ym19_1_1487765452774_7315">2) Sample rate is secondary, and any file recorded at a particular sample rate can be played back at any other rate, but it would be nice to know this, but it is negotiable within the patch.<br></div><div id="yui_3_16_0_ym19_1_1487765452774_7433"><br></div><div id="yui_3_16_0_ym19_1_1487765452774_7494">3) Bit rate - perhaps for saving this might be useful, although since saving is a generated process rather than a parameter specified within the header of a file (discuss), it is probably of little importance. The soundfiler object can already read 16, 24 and 32 bit files, and I can't see a future for 64 bit audio (although electronics manufacturers will certainly try to sell this in the future, despite the fact that most DA conversions are Sigma-Delta making bit-depth more-or-less irrelevant).</div><div id="yui_3_16_0_ym19_1_1487765452774_9301"><br></div><div id="yui_3_16_0_ym19_1_1487765452774_9433">Thoughts?</div><div id="yui_3_16_0_ym19_1_1487765452774_9432">Ed<br></div><div id="yui_3_16_0_ym19_1_1487765452774_6836"><span></span></div><div id="yui_3_16_0_ym19_1_1487765452774_6837"> </div><div id="yui_3_16_0_ym19_1_1487765452774_6701" class="signature">_-_-_-_-_-_-_-^-_-_-_-_-_-_-_<br><br>For <b id="yui_3_16_0_ym19_1_1487765452774_6700">Lone Shark </b>releases, <b id="yui_3_16_0_ym19_1_1487765452774_11363">Pure Data </b>software and published <b>Research</b>, go to <a id="yui_3_16_0_ym19_1_1487765452774_11364" rel="nofollow" target="_blank" href="http://sharktracks.co.uk/">http://sharktracks.co.uk</a> </div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> On Wednesday, 22 February 2017, 12:09, Lucas Cordiviola <lucarda27@hotmail.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv3468639400"><style type="text/css">#yiv3468639400 #yiv3468639400 -- P {margin-top:0;margin-bottom:0;}#yiv3468639400 </style><div dir="ltr">
<div dir="ltr" id="yiv3468639400divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri, Arial, Helvetica, sans-serif;">
<blockquote style="margin:0 0 0 40px;border:none;padding:0px;">
<div></div>
<div><i>>[soundfile_info] seems the better choice and</i></div>
<div></div>
<div></div>
<div><i>is able to read all files that are read by [readsf~]/[soundfiler], from</i></div>
<div></div>
<div></div>
<div><i>what I can tell. </i></div>
<div></div>
</blockquote>
<div></div>
<div><br clear="none">
</div>
<div>In the past I found discrepancies on *sound file length*:</div>
<div><br clear="none">
</div>
<div>[soundfiler] != [sounfile_info] </div>
<div>[soundfiler] == soundforge</div>
<br clear="none">
<div></div>
<div><br clear="none">
</div>
<div id="yiv3468639400Signature"><font size="2" face="Courier New, Courier, Monospace">Mensaje telepatico asistido por maquinas.</font>
</div>
<br clear="none">
<br clear="none">
<div class="yiv3468639400yqt6158181027" id="yiv3468639400yqt76231"><div style="color:rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block;width:98%;">
<div dir="ltr" id="yiv3468639400x_divRplyFwdMsg"><font style="font-size:11pt;" face="Calibri, sans-serif" color="#000000"><b>From:</b> Pd-list <pd-list-bounces@lists.iem.at> on behalf of Roman Haefeli <reduzent@gmail.com><br clear="none">
<b>Sent:</b> Wednesday, February 22, 2017 8:19 AM<br clear="none">
<b>To:</b> pd-list@lists.iem.at<br clear="none">
<b>Subject:</b> Re: [PD] soundfiler features</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
</span></font><div class="yiv3468639400PlainText">On Die, 2017-02-21 at 11:01 +0000, Ed Kelly via Pd-list wrote:<br clear="none">
> <br clear="none">
> Since this information is contained within the header of each file<br clear="none">
> (although it's a pain with the different formats), would it not be<br clear="none">
> sensible to have a second outlet in soundfiler that delivers the<br clear="none">
> number of channels, before the number of samples in the file is<br clear="none">
> delivered from the left outlet? Perhaps also other info, but what<br clear="none">
> would be relevant to a patch? I think channels is a necessary piece<br clear="none">
> of information. <br clear="none">
<br clear="none">
I, too, think that [soundfiler] should output some sound file<br clear="none">
properties instead using them only internally. It would be good to be<br clear="none">
able to make patches where the patch creator doesn't need to know<br clear="none">
beforehand what exact formats are going to be opened by the patch user.<br clear="none">
<br clear="none">
I'd like to know the following properties (in descending order of<br clear="none">
necessity):<br clear="none">
* number of channels <br clear="none">
* sample rate<br clear="none">
* bit depth<br clear="none">
<br clear="none">
There are at least two externals, that provide this info: ext13's<br clear="none">
[wavinfo] and [soundfile_info] from iemlib. In my experience, the<br clear="none">
former doesn't read correctly all wav files that are read by other<br clear="none">
programs or by Pd, I believe it assumes a certain layout instead of<br clear="none">
truly parsing the header. [soundfile_info] seems the better choice and<br clear="none">
is able to read all files that are read by [readsf~]/[soundfiler], from<br clear="none">
what I can tell.<br clear="none">
<br clear="none">
Roman<br clear="none">
</div>
</div></div>
</div>
</div></div><br><div class="yqt6158181027" id="yqt64076">_______________________________________________<br clear="none"><a shape="rect" ymailto="mailto:Pd-list@lists.iem.at" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br clear="none">UNSUBSCRIBE and account-management -> <a shape="rect" href="https://lists.puredata.info/listinfo/pd-list" target="_blank">https://lists.puredata.info/listinfo/pd-list</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>