Interoperability and regions export feature implementation

Maxime Lecoq <[email protected]> Wed, 29 Aug 2018 20:32:23 +0200
Newsgroups gmane.comp.audio.ardour.devel
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============6873567648241560131==
Content-Type: multipart/alternative;
 boundary="------------1A61B86A0A3FFC975CF5A2B3"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------1A61B86A0A3FFC975CF5A2B3
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,

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

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 on=
ce.
As I have seen, the infrastructure is already designed to receive such a
feature (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
source 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.





--------------1A61B86A0A3FFC975CF5A2B3
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#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
    especially when you have to share them using Internet (using a
    80KB/s upload connexion!).<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>Protools</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
    operation.<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 feature (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 source 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>
  </body>
</html>

--------------1A61B86A0A3FFC975CF5A2B3--

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

--===============6873567648241560131==--