Re: Interoperability and regions export feature implementation

Ed Ward <[email protected]> Thu, 30 Aug 2018 09:04:38 +0000
Newsgroups gmane.comp.audio.ardour.devel
Message-ID <AM0PR0502MB384456A631EDCF0D3755552CD1080@AM0PR0502MB3844.eurprd05.prod.outlook.com>
--===============0033875581908426326==
Content-Language: fr-FR
Content-Type: multipart/alternative;
	boundary="_000_AM0PR0502MB384456A631EDCF0D3755552CD1080AM0PR0502MB3844_"

--_000_AM0PR0502MB384456A631EDCF0D3755552CD1080AM0PR0502MB3844_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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 compressio=
n. Neither of these you want for your workflow.

You should rather look into FLAC export, or with a post-export script and i=
f you are using floating point WAV files, WavPack.

Regards,
Edouard Saintesprit
________________________________
De : Ardour-Dev <[email protected]> de la part de Maxime =
Lecoq <[email protected]>
Envoy=E9 : mercredi 29 ao=FBt 2018 20:32
=C0 : [email protected]
Objet : [Ardour-Dev] Interoperability and regions export feature implementa=
tion

Hi,

I currently faced the need to inter-operate with others DAW (like Reaper an=
d Protools) for music film mixing (cinema).
The solution our team used was to import/export stems (thanks to the nice A=
rdour export stems feature).
A downside of this solution is the size of the generated stems files especi=
ally when you have to share them using Internet (using a 80KB/s upload conn=
exion!).

A smarter solution would be to export all regions to BWF wav files.
In our case, the size reduction gain was over 70%.
BWF is well supported by Ardour, Reaper and Protools.
(I can't find any Cubase support for this feature).
Additional future BW64/MBWF support would simply this operation.

As you certainly know, regions export can be achieve track by track in the =
current Ardour version (5.12, dev 6-pre0).
I'm now trying to develop an Ardour feature allowing to do it all at once.
As I have seen, the infrastructure is already designed to receive such a fe=
ature (Editor::export_region, ARDOUR::export_handler...).

Please let me know if someone is already working on this?
Also feel free to give me some advice to help me understand the involved so=
urce code.
I have to make sequence diagrams to help me follow the execution flow.

About comments, I can't find so much in the source code.
Is there a particular reason for that?
May I comment/document (Doxygen) what I write directly in .cc files?

Best regards,
Maxime Lecoq.





--_000_AM0PR0502MB384456A631EDCF0D3755552CD1080AM0PR0502MB3844_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Hi Maxime,&nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"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 compressio=
n. Neither of these you want for your workflow.</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
You should rather look into FLAC export, or with a post-export script and i=
f you are using floating point WAV files, WavPack.</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Regards,</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Edouard Saintesprit</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>De :</b> Ardour-Dev &lt;ardour-=
[email protected]&gt; de la part de Maxime Lecoq &lt;maxime.leco=
[email protected]&gt;<br>
<b>Envoy=E9 :</b> mercredi 29 ao=FBt 2018 20:32<br>
<b>=C0 :</b> [email protected]<br>
<b>Objet :</b> [Ardour-Dev] Interoperability and regions export feature imp=
lementation</font>
<div>&nbsp;</div>
</div>
<meta content=3D"text/html; charset=3Dutf-8">
<div style=3D"background-color:#FFFFFF">Hi,<br>
<br>
I currently faced the need to inter-operate with others <i>DAW</i> (like <i=
>Reaper</i> and
<i>Protools</i>) for music film mixing (cinema).<br>
The solution our team used was to import/export stems (thanks to the nice <=
i>Ardour</i> export stems feature).<br>
A downside of this solution is the size of the generated stems files especi=
ally when you have to share them using Internet (using a 80KB/s upload conn=
exion!).<br>
<br>
A smarter solution would be to export all regions to <i>BWF</i> <i>wav</i> =
files.<br>
In our case, the size reduction gain was over 70%.<br>
<i>BWF</i> is well supported by <i>Ardour</i>, <i>Reaper</i> and <i>Protool=
s</i>.<br>
(I can't find any <i>Cubase</i> support for this feature).<br>
Additional future<i> BW64</i>/<i>MBWF</i> support would simply this operati=
on.<br>
<br>
As you certainly know, regions export can be achieve track by track in the =
current
<i>Ardour</i> version (5.12, dev 6-pre0).<br>
I'm now trying to develop an <i>Ardour</i> feature allowing to do it all at=
 once.<br>
As I have seen, the infrastructure is already designed to receive such a fe=
ature (Editor::export_region, ARDOUR::export_handler...).<br>
<br>
Please let me know if someone is already working on this?<br>
Also feel free to give me some advice to help me understand the involved so=
urce code.<br>
I have to make sequence diagrams to help me follow the execution flow.<br>
<br>
About comments, I can't find so much in the source code.<br>
Is there a particular reason for that?<br>
May I comment/document (<i>Doxygen</i>) what I write directly in .cc files?=
<br>
<br>
Best regards,<br>
Maxime Lecoq.<br>
<br>
<br>
<br>
<br>
</div>
</body>
</html>

--_000_AM0PR0502MB384456A631EDCF0D3755552CD1080AM0PR0502MB3844_--

--===============0033875581908426326==
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

--===============0033875581908426326==--