Hi friends. I have to send comps back to color. They are requesting that the EDL/XML/AAF I provide includes timewarp/speed change information. I don’t think that’s possible out of Flame. Can anyone confirm this or correct me?
Publishing tools should allow that. Should be some presets that ship with the software.
EDL can’t handle any ramps 
My AAFs that I send to Resolve from Flame are always messed up if they have a TW. I think this is the same with XMLs 
You’d think we could do this wouldn’t you.
Wouldn’t they be getting that info from offline? Or are you changing things in Flame?
Not changing them dramatically, but this is a new thing for me, roundtripping back through color. Most likely not anything they’d notice.
1 Like
True and they would be sending it back to you without the TW so you can re-apply it with care.
It is just for colour review 
I’m pretty sure it comes out just as well as it does from any other NLE. In a vanilla EDL it will list your timewarp in FPS as opposed to speed percentage. I do this to our colour suites all the time and I haven’t heard complaints…
do it all the time with TWs to color through the export EDL publish in export menu. on occasion if i’ve got a really massive TW (dont want to send 1000s of frames to color) or a ramp that i’ve tweaked to be just so i’ll bake the TW in and publish it to color like it was a normal shot.
EDLS from flame only support static timewarps instead of animated ones
EDL Publishing Remarks
- Animated timewarps are converted into constant timewarps when written to an EDL.The Source In and Source Out written to the outgoing EDL match the span of the media used in the original animated timewarp. The constant timewarp speed in the outgoing EDL is calculated so that the media fits the segment’s duration.
here is a good website with the overview about flames XML/AAF/EDL export capabilities.
https://help.autodesk.com/view/FLAME/2024/ENU/?guid=GUID-A4283A7D-E212-4C7E-80D9-BE55E37D1655
I think all EDLs only support static timewarps, not just EDLs from Flame. The format dates back to the late 1970s.
2 Likes
When I have the painful task of exporting whatever the format, the best results for me are aaf or edl. Xml is unusable in my experience. I believe that for statics timewarps, both edl and aaf work. Although they both are single-layer. So it may be necessary to do multiple exports per version.
But what I always have to do is export a reference movie, import the edl or xml in Resolve, reconform, and fix the infinite issues. It requires a little of learning of resolve, to be able to match offlines. Then I export to xml and I’m pretty sure it won’t give any problems wherever I have to deliver.
Very painful.
Just to be clear, thats not a Flame limitation. EDLs as a format dont have keyframes at all.
*sorry. i see @hBomb42 beat me to it.
3 Likes
haha yea bad phrasing, anyhow.
Flame cannot export animated timewarps in whatever format, which isnt … great.
1 Like
I’ve cheesed it by copying timing curve keyframes to an axis’s x.position or something and spitting it out an FBX, but that’s probably more trouble than it’s worth for sending stuff to color.
2 Likes
The thing I like about EDLs is that they are human readable. I have edited and fixed many EDLs in a text editor in the olden times.