Take the 2-minute tour ×
Video Production Stack Exchange is a question and answer site for engineers, producers, editors, and enthusiasts spanning the fields of video, and media creation. It's 100% free, no registration required.

I want to import Cues from an external source (CUE-File or mp4chaps Simple Chapter Text file) to Audition, or even better yet, permanently stick them to WAV files.

Looking through old documentation for Audition 3 (Windows), I noticed that there used to be an "Import" function for Markers or Cues.

This function is no longer available in Audition CS5.5, and I don't know if CS6 will bring any new functionality.

share|improve this question
add comment

1 Answer 1

And as I spent the last two days hunting down a solution, I'll share it with you right away:

tl;dr: Use this cross platform & open source tool by the US Government (ya, really) to stick XMP Metadata in the WAV File. http://bwfmetaedit.sourceforge.net/

WAV Files support the "cue " chunk, and this chunk is written by Audition, but I couldn't make it read from this chunk, and related chunks containing the cue names.

But Audition also writes the XMP Metadata, including a somewhat redundant copy of the Cue chunk. And it will also read it back.

So, by generating an XMP file containing the cue information, and sticking it in the XMP chunk of a WAV file, you can import that data to Audition.

For example:

<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.2-c003 61.141987, 2011/02/22-12:03:51        ">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:xmpDM="http://ns.adobe.com/xmp/1.0/DynamicMedia/">
         <xmpDM:Tracks>
            <rdf:Bag>
               <rdf:li rdf:parseType="Resource">
                  <xmpDM:trackName>CuePoint Markers</xmpDM:trackName>
                  <xmpDM:trackType>Cue</xmpDM:trackType>
                  <xmpDM:frameRate>f254016000000</xmpDM:frameRate>
                  <xmpDM:markers>
                     <rdf:Seq>
                        <rdf:li rdf:parseType="Resource">
                           <xmpDM:startTime>18645250f44100</xmpDM:startTime>
                           <xmpDM:name>Marker 01</xmpDM:name>
                        </rdf:li>
                        <rdf:li rdf:parseType="Resource">
                           <xmpDM:startTime>69088263f44100</xmpDM:startTime>
                           <xmpDM:name>Marker 02</xmpDM:name>
                        </rdf:li>
                     </rdf:Seq>
                  </xmpDM:markers>
               </rdf:li>
            </rdf:Bag>
         </xmpDM:Tracks>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:dc="http://purl.org/dc/elements/1.1/">
         <dc:format>audio/x-wav</dc:format>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>

The format should be self explanatory.

If you want to write your own tool to automate this, follow the XMP specs from Adobe concerning WAV files and the XMP chunk, which, ironically is named backwards:

The XMP in […] WAV is in a chunk with the ID "_PMX", encoded as UTF-8. Note that the ID is backwards, due to a bug in the initial implementation concerning processor byte order.

Here's an iOS App that will generate Audition-compatible XMP files: http://itunes.apple.com/us/app/xmp-marker/id525322095?ls=1&mt=8

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.