Re: DaVinci Resolve 8.1 -- now with FCPXML roundtrip support

[Simon Ubsdell] "Honestly, Jeremy, this is a bit disingenuous, isn't it? You really believe that the only similarities are "visual"???

I do wonder (and I hope you won't think me rude for asking the question) whether you've actually looked at iMovie to see how non-trivial the similarities are and how deeply they relate to function as opposed to mere cosmetics as you seem to be trying to imply."

I haven't played with iMovie much, no and it's not a rude question. My point about AE and PPro having similar interfaces still stands. They have tabs, the organizing is similar, but yet they are completely different apps. Those tabs also stretch across photoshop and illustrator (and the whole Creative Suite).

As I have said before, they share ideologies, but this does not mean that the programs themselves are structured form the same code which is to say that while the method of FCPX stems from iMovie, it does not mean the FCPX the application has been in full development for the same time as iMovie. That is all. I will maintain it's not iMovie Pro, even if the programs behave similarly. And really, I don't care. Call it iMovie Pro. If iMovie Pro plugs in to an AJA card, then sweet for me.

If it is written from different code, you have to still make sure that code works, it's not just copy/paste, add a secondary storyline feature. Do you have experience with working with software developers at all? Not that I am an expert, but I am just wondering if you know how hard it really is and how long something this complex takes. If FCPX and iMovie were the same, why isn't FCPXML done? It takes a long time to go from concept to production. iMovie was/is the concept.

I hope you know, I am not denying what seems to be similar interfaces and methods, but that link that was sent by Steve Conor seems to point out some really major differences between the apps, including the timelines. They don't even look similar, I just took you at your word.

And the long list of things you mention, is that what really separates a Pro Application from a consumer one? Audio adjustment? Waveforms? A range? These things do not a Pro application make.

And so what, test it on a million consumers before letting me take a shot at it. Siri is now in the hands of at least 4 million people. Think of the data gathering that will make Siri better, and maybe adaptable for something else that will make my professional life better. I am OK with all of that.

And I like most of the magnetic timeline so I'm weird.