Shrinivas Ramani wrote:Can you add a URL for the industry standard definition?
Closest I have is Autodesk documentation.
https://knowledge.autodesk.com/support/ ... 1-htm.htmlAs far as I've seen, like in the Fusion implementation, quotes are ignored and if a path isn't supplied, the file is assumed to be relative to the .IFL file. Relative paths are hit and miss for support.
Shrinivas Ramani wrote:Out of curiosity, is there a reason a script with logic like this wouldn't work?
- Code: Select all
with open(ifl_path) as f:
for line in f.readline().split(' '):
image,length = line if len(line) == 2 else fallback_logic(line) # not sure of rules
#...
clips = mediaStorage.AddItemsToMediaPool(images)
mediaPool.AppendToTimeline(clips)
I don't think it would solve the issue. I expect most users would want the .IFL to be treated as a clip in the media pool and timeline. The explicit sequencing in the IFL file would be difficult to maintain if the linked files were pulling in individually. A potential compromise might be automatically generating a compound clip.
One thing to consider is that there is nothing restricting the IFL to containing the same file types. Resolution, color depth, metadata, etc. might be changing per frame. Resolve handles that "just fine" when Fusion outputs that to the timeline, so maybe it could be handled the same way with automatic resizing and such.
A super awesome implementation in Resolve would include supporting IFL as an output format in the Deliver tab.