[Ardour-Dev] Interoperability and regions export feature implementation

Maxime Lecoq maxime.lecoq.a at wanadoo.fr
Fri Aug 31 08:29:13 PDT 2018

Le 30/08/2018 à 14:40, Ed Ward a écrit :
> 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 <paul at linuxaudiosystems.com>
> *Envoyé :* jeudi 30 août 2018 13:33
> *À :* Ed Ward
> *Cc :* Maxime Lecoq; ardour-dev at lists.ardour.org
> *Objet :* Re: [Ardour-Dev] Interoperability and regions export feature
> implementation
> On Thu, Aug 30, 2018 at 5:04 AM, Ed Ward <edwsaintesprit at hotmail.com
> <mailto:edwsaintesprit at hotmail.com>> wrote:
>     Hi Maxime, 
>     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).
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> 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).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20180831/0b69e38b/attachment.htm>

More information about the Ardour-Dev mailing list