Update: Apple fixed the issue with FCPX 1.2.0
When you import video files into Final Cut Pro X, you grant read-write permissions to FCPX to access these files. To make these permissions permanent, FCPX saves it internally as so called bookmarks. Without these bookmarks FCPX would need to ask for your permission each time it reads the files.
In the XML, which you export from FCPX, there are the file paths accompanied by their bookmarks. This way FCPX passes it´s permissions over to ClipExporter. Without these bookmarks ClipExporter can not read any file although it knows its absolute file path. Since ClipExporter is sandboxed (Apple´s security technology) it depends on bookmarks in order to access files and folders.
The bug: I found out that if I create a brand new project and export an XML from it for the first time, FCP X does not write the bookmarks into the XML. This happens only for the first time and if you export again everything is fine. I filed a bug on Apples bugreport system.
In some rare cases some customers reported that they repeatedly tried but had no luck in exporting a working XML with bookmarks. In such cases I recommend using the non Mac App Store version of ClipExporter. You can download it here:
Each RED clip is saved in a unique clip folder. If its a long clip (exceeding the 4GB) this folder contains multiple .R3D files which all together form a single RED clip. FCPX provides bookmark data (see previous FAQ) of the media files so 3rd party apps have permission to read specified files. But when it comes to long RED clips there is only bookmark data for the very first R3D file (out of 3 for example). Therefore the R3DSDK is only able (or permitted) to read one file and the trim operation fails and the announced RED support in ClipExporter looks like a half-baked feature.
Therefore ClipExporter can only export RED files that consists of a single file. I contacted Apple about this issue and they listened.
If you need full RED support I recommend the non Mac App Store version of ClipExporter (only for existing customers) that you can download here:
Such error occurs mostly when you export dropframe videos. The new AVFoundation framework sometimes fails to handle this type of footage BUT the legacy QTKit does. Since the QTKit framework is deprecated and not allowed for App Store apps it recommend to download the non Mac App Store version. This available for existing customers only. You can download it here:
No. The (auto-)counter number is only used to keep file names unique. It does not represent the order of how the clips are laid out in the timeline.
If you require the timecode values of each clip in the timeline, I recommend to take a closer look at the export list that gives you a detailed listing of all the timecode and metadata of each clip.