Michael already referenced the issue with the EDL. The issue with using 30 year old technology (CMX EDL) and new workflows. The EDL specifies that a source can not have more than 8 characters and no more than 254 sources total, and no more than 999 events. Well that doesn’t really work in the new millennium. The File_16 and File_32 templates were created to support newer workflows while still available as an EDL. The File_16 was designed for RED to allow the full 16 characters of the filename to be used as source. File_32 for formats that use more than 16 such as Arri Alexa, SI2K, etc. The number of sources was changed to be unlimited since every clips was now its own source, and the limitation as to the number of events was removed.
FCP always stuck to the EDL specification while every other manufacturer quickly adopted the new EDL format. So FCP still has the 8 character limit which is why you see the ALE contain the 8 character file truncation when exporting from RXC Pro to Avid. I asked RED they include that so MC could track both methods of source allowing one to go to FCP or other third parties.
AMA has its own extraction of metadata from the RED SDK – I can’t recall whether it does the 8 character representation or not – I don’t think it does – but just use the File_16 template for all workflows not involving FCP.
AMA also requires that a transcode be done before you can export an AAF file – which is a bit stupid, and is also the reason why you can’t send sequence to EDL Manager as it uses AAF to communicate between the two applications. Opening the bin directly from EDL Manager skips that communication protocol.
But, you can check “use edit protocol” on the AAF settings on export and it will allow you to export an AAF. Edit Protocol is a simplified version of the composition, closer to an EDL than the full metadata of everything that goes into an AAF file, but for what Resolve and many other applications support, it works fine.
Michael
Michael Phillips