Re: Interoperability and regions export feature implementation
Maxime Lecoq <[email protected]> Fri, 31 Aug 2018 17:29:13 +0200
| Newsgroups | gmane.comp.audio.ardour.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============4228370953361146086== Content-Type: multipart/alternative; boundary="------------6F3D7CDF2A725F4A62D93FB3" Content-Language: en-US This is a multi-part message in MIME format. --------------6F3D7CDF2A725F4A62D93FB3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Le 30/08/2018 =E0 14:40, Ed Ward a =E9crit=A0: > Oh Ok I get it ! Timestamping to replace empty WAV data chunks. My > mistake ! > > 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. > > Regards, > Edouard Saintesprit > > > -----------------------------------------------------------------------= - > *De :* Paul Davis <[email protected]> > *Envoy=E9 :* jeudi 30 ao=FBt 2018 13:33 > *=C0 :* Ed Ward > *Cc=A0:* Maxime Lecoq; [email protected] > *Objet :* Re: [Ardour-Dev] Interoperability and regions export feature > implementation > =A0 > > > On Thu, Aug 30, 2018 at 5:04 AM, Ed Ward <[email protected] > <mailto:[email protected]>> wrote: > > Hi Maxime,=A0 > > 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. > > > 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). > =A0 > > > _______________________________________________ > ardour-dev mailing list > [email protected] > http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org Paul is right, 1 /BWF/ for each region. I have something that does export the selected regions but I wasn't able to use properly the dedicated export /API/. The reason is that /API/ only allows to have the same time-spans for a set of channels. In the case of regions, we need different time-spans for each track. The current solution iterates over the selected regions and calls the /ExportRegionDialog/ stuff without the dialog being showed. In my opinion, a better solution would be to write a dedicated /API/ for exporting multiple regions without breaking the current export /API/ (by calling /ARDOUR::ExportHandler/ methods). But this seems to add unnecessary complexity and could lead to make the export system very hard to use, understand and enhance. I believe the best solution would be to implement multiple time-spans per channel but this seems to lead to redesign the whole export /API/ (or a big part of it). --------------6F3D7CDF2A725F4A62D93FB3 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> </head> <body text="#000000" bgcolor="#FFFFFF"> <br> <br> <div class="moz-cite-prefix">Le 30/08/2018 à 14:40, Ed Ward a écrit :<br> </div> <blockquote type="cite" cite="mid:AM0PR0502MB3844504019A3864678D3B9ECD1080@AM0PR0502MB3844.eurprd05.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style> <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 style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>De :</b> Paul Davis <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> <b>Envoyé :</b> jeudi 30 août 2018 13:33<br> <b>À :</b> Ed Ward<br> <b>Cc :</b> Maxime Lecoq; <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a><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:[email protected]" target="_blank" moz-do-not-send="true">[email protected]</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> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ ardour-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org">http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org</a> </pre> </blockquote> <br> Paul is right, 1 <i>BWF</i> for each region.<br> <br> I have something that does export the selected regions but I wasn't able to use properly the dedicated export <i>API</i>.<br> The reason is that <i>API</i> only allows to have the same time-spans for a set of channels.<br> In the case of regions, we need different time-spans for each track.<br> <br> The current solution iterates over the selected regions and calls the <i>ExportRegionDialog</i> stuff without the dialog being showed.<br> <br> In my opinion, a better solution would be to write a dedicated <i>API</i> for exporting multiple regions without breaking the current export <i>API</i> (by calling <i>ARDOUR::ExportHandler</i> methods).<br> But this seems to add unnecessary complexity and could lead to make the export system very hard to use, understand and enhance.<br> <br> I believe the best solution would be to implement multiple time-spans per channel but this seems to lead to redesign the whole export <i>API</i> (or a big part of it).<br> <br> <br> </body> </html> --------------6F3D7CDF2A725F4A62D93FB3-- --===============4228370953361146086== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ardour-dev mailing list [email protected] http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org --===============4228370953361146086==--