OTIO support

Other software packages will start having OpenTimelineIO. I think DaVinci Resolve should support it before it's an obvious industry standard. AAF and FCP XML weren't (I don't think) designed for the transport workflows they fulfill now. OTIO could naturally make EDL/AAF/XML into legacy formats.

DaVinci Resolve should support OpenTimelineIO as it does with OpenColorIO and OpenEXR.

I totally agree in concept, and I have to believe that BMD is well aware of OTIO, and probably investigating it behind the scenes.

That said, I do recall that as late as September 2020, even the developers of OTIO admitted that it wasn’t quite ready for use as a robust NLE timeline interchange protocol, and has quite a bit of ways to go towards that goal:

Not sure what kind of advances have been made to the project since then, but I have to think that’s it’s still not ready to be a full blown replacement for XML/AAF.

Heres the slightly more recent presentation:

+1

In a way, my prediction is that this format can go two ways:

1) the way of AAF: the promise of any software to open and interchange metadata, ultimately a failure because every software included their little special sauce so you cannot (efficiently) use it in another software….

2) the way of linux… it become good and basically overtake the old UNIX systems… but… now has scores of illegittime childrens (all the different distros) and whoever was profiting from it is doing something else.

So, my take is, personally, I don't think that a company want to risk the second way (become obsolete) because at one point if every free software can do what my software can do, why anybody want to buy my product?
Unless you’re a company that you’re either in decline (and you need a lifeline) or you’re emerging one (and you need to disrupt…).

I dont think BM is either.

BUT… I dont have a degree in economics… sooo.. just my 2c…

Which way of the two OpenEXR went? Or USD? In reality things seem to steer towards the third option: if you don’t implement modern efficient scalable interchange formats you go obsolete sooner or later. And software vendors that try to implement their own bastardised ill-compatible versions of these initiatives should be actively discouraged from doing it.

This has been added since v18.5