<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;">
<p></p>
<div><i>>[soundfile_info] seems the better choice and</i></div>
<p></p>
<p></p>
<div><i>is able to read all files that are read by [readsf~]/[soundfiler], from</i></div>
<p></p>
<p></p>
<div><i>what I can tell. </i></div>
<p></p>
</blockquote>
<p></p>
<div><br>
</div>
<div>In the past I found discrepancies on *sound file length*:</div>
<div><br>
</div>
<div>[soundfiler] != [sounfile_info] </div>
<div>[soundfiler] == soundforge</div>
<br>
<p></p>
<p><br>
</p>
<div id="Signature"><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Pd-list <pd-list-bounces@lists.iem.at> on behalf of Roman Haefeli <reduzent@gmail.com><br>
<b>Sent:</b> Wednesday, February 22, 2017 8:19 AM<br>
<b>To:</b> pd-list@lists.iem.at<br>
<b>Subject:</b> Re: [PD] soundfiler features</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On Die, 2017-02-21 at 11:01 +0000, Ed Kelly via Pd-list wrote:<br>
> <br>
> Since this information is contained within the header of each file<br>
> (although it's a pain with the different formats), would it not be<br>
> sensible to have a second outlet in soundfiler that delivers the<br>
> number of channels, before the number of samples in the file is<br>
> delivered from the left outlet? Perhaps also other info, but what<br>
> would be relevant to a patch? I think channels is a necessary piece<br>
> of information. <br>
<br>
I, too, think that [soundfiler] should output some sound file<br>
properties instead using them only internally. It would be good to be<br>
able to make patches where the patch creator doesn't need to know<br>
beforehand what exact formats are going to be opened by the patch user.<br>
<br>
I'd like to know the following properties (in descending order of<br>
necessity):<br>
* number of channels <br>
* sample rate<br>
* bit depth<br>
<br>
There are at least two externals, that provide this info: ext13's<br>
[wavinfo] and [soundfile_info] from iemlib. In my experience, the<br>
former doesn't read correctly all wav files that are read by other<br>
programs or by Pd, I believe it assumes a certain layout instead of<br>
truly parsing the header. [soundfile_info] seems the better choice and<br>
is able to read all files that are read by [readsf~]/[soundfiler], from<br>
what I can tell.<br>
<br>
Roman<br>
</div>
</span></font></div>
</div>
</body>
</html>