<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<font face="Courier New">Just a thought: nbits should never have
been an input argument of a playback function, since the precision
of the internal data is much higher than even 24 bit, the higher
bit resolution usually found in audio playback systems (not to be
confused with the internal representation of many digital signal
processors; I mean D/A converters). By the way, 24 bit means 144
dB signal/noise ratio, much higher than currently attainable
analog performance. <br>
<br>
The only situation where that could be of some interest would be
to demonstrate in the classroom the effects of reducing the number
of bits per sample. But as such case is very specific and quite
rare, it would be better just to requantize de original signal
getting entire control of the situation, being able to measure
noise and /or distortion, plot the stair-like waveform and listen
to the result.<br>
<br>
Federico Miyara <br>
<br>
</font><br>
<div class="moz-cite-prefix">On 02/03/2020 13:03, Samuel Gougeon
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ac76dbcf-aad0-41c0-7bcd-63a8e1c326f3@free.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div class="moz-cite-prefix">Le 02/03/2020 à 16:45, Perrichon a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:!&!AAAAAAAAAAAuAAAAAAAAAHTRbxuKTONJuQv%2FnFKuTP8BANlTnCJhprtFudq2LHCBs8EBACQA%2F%2F8AABAAAACsh3yvPNI7QqvegiubT4T9AQAAAAA=@wanadoo.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.tlid-translation
{mso-style-name:tlid-translation;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span class="tlid-translation"><span
lang="EN">Ok but this is a strange way to handle
backward compatibility</span></span></p>
</div>
</blockquote>
<p><br>
</p>
<p>I agree. This is why i asked for confirmation to a second
reviewer before removing nbits, <br>
when the first reviewer asked me to remove it.<br>
nbits was never implemented (never actually used in the
function), just present as a dead input.<br>
But it was not disturbing.<br>
Now, i guess that sometimes it's useful to clean the code. I
think that the next input argument "aplay"<br>
after nbits is (very) rarely used (it addresses "only" Linux and
MacOS users (15%), and only if<br>
its default value is not convenient (? 5% of 15% ?). Most often,
only the first 2 arguments are used.</p>
<p><br>
</p>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:users@lists.scilab.org">users@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/users">http://lists.scilab.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>