<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 style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Oh Ok I get it ! Timestamping to replace empty WAV data chunks. My mistake !</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Though it is worth noting that these empty WAV chunks are obviously very well compressed when converted to FLAC/WavPack for a quick "as-is" solution to the problem at hand.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Edouard Saintesprit</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>De :</b> Paul Davis <paul@linuxaudiosystems.com><br>
<b>Envoyé :</b> jeudi 30 août 2018 13:33<br>
<b>À :</b> Ed Ward<br>
<b>Cc :</b> Maxime Lecoq; ardour-dev@lists.ardour.org<br>
<b>Objet :</b> Re: [Ardour-Dev] Interoperability and regions export feature implementation</font>
<div> </div>
</div>
<meta content="text/html; charset=utf-8">
<div>
<div dir="ltr">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="x_gmail_extra"><br>
<div class="x_gmail_quote">On Thu, Aug 30, 2018 at 5:04 AM, Ed Ward <span dir="ltr">
<<a href="mailto:edwsaintesprit@hotmail.com" target="_blank">edwsaintesprit@hotmail.com</a>></span> wrote:<br>
<blockquote class="x_gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hi Maxime, </div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
correct me if I'm wrong but if your BWF files are smaller than the original WAV files, that is beacause of either a downsampling or an mpeg compression. Neither of these you want for your workflow.</div>
</div>
</blockquote>
<div><br>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">I believe that his point was that having a set of BWF's, 1 for each region, with timestamps, would be less data than a set of WAVs, 1 for each track (timestamps irrelevant since they
all span the entire timerange).</div>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>