Looking to see how this is distribution turns out
Pick the one you get 'the most often" from editors
I’ll admit I almost said FCP 7 XML, since Adobe has done very little modification from the FCP 7 format.
apparently enough to make flame freak out? xD
I more mean xmls from actual fcp7 i expect this to be 0 xD
@Slabrie lets see where this goes but i think thats about a real world spread we have here, feels about right at 51% premiere xmls
Most of our editors use Avid, but a few use Premier. So I get both, but I voted Avid since that’s the more common one.
And how likely are they going to stay in Avid for the next 5+ years?
I love Avid, it used to be my NLE of choice. But it’s become harder and harder to justify, especially outside of long-form.
When @Slabrie considers the importance of fixing these issues, it’s part of a question about today, and part of a quesiton about tomorrow. Who know about next year. But tomorrow is relevant.
Beats me, but it’s the younger crowd that use premier
Personally I’m just surprised that anyone at all is still using EDL files like in the 80’s…. Is there some hidden benefit I’m unaware of?
I see a lot of editors moving away from Premiere in favour of Resolve these days..
Adobe Premiere XML, but it looks like everything drifting to Resolve.
i find adobe premiere AAF kinda funny - these dont even carry any repo information at all.
just like resolve AAFs.
finishing and comp too…
It always takes a generation, my generation was pissed off by avid and the death of fcp - so we moved to premiere , so now rhere are lots of very seasoned editors that can do premiere and avid.
But now nobody has been learning Media Composer in the last 10 years, (just like flame really)…
They got raised up with premiere and naturally - nobody wants to deal with adobe garbage anymore so they move to the next thing thats .. resolve.
Resolves pricing really is unfair , idk if yhe boss of BM is just angry at adobe etc and is trying to kill them but whatever it is - they are just the best value proposition out there.
They are not at a “Flame level” yet at all, but they are doing huge steps on every update while we are sitting here talking about .. xml support
maybe ADSK should just throw weight beign OTIO and make it actually useable, or come up with a new open standard for timeline exchange.. make everyone support it and boom. super easy . (lol)
Not only from Premiere. Also from Avid.
We switched from Avid to Resolve a few months ago. Kicking and screaming, but it was the right thing to do workflow wise.
Resolve’s edit capabilities are decent, and with the new BMD Cloud Storage you have one of the simpler distributed workflows at affordable rates. It has still kinks in it and some growing pains, but no show stoppers.
Avid licenses are retired and I’m trying to find a new home for my Nexis. Very little demand in the market for that, especially in the current cash crunch that seems to have gripped everyone.
i only know of a lot of weird longform automations from 1995 that are apparently still innplace other than that - not a clue!
biggest suprise for me here right now is how strong avid still is, i expected it to be below 10% / it has been realistically phased out in my market
Simplicity: take this, put it here. Sadly they can’t handle mixed frame rates or timewarps, otherwise I would use them more.
I’ve commented on that and the cows still haven’t come home.
Yes, Grant Petty had a beef with Hollywood many years ago and definitely set out to proof them wrong. It’s been written about in the press way back. Now the train has so much momentum, that’s less of a motivation. In fact we’re seeing early signs that they might be moving in the opposite direction and charging for major version upgrades going forward, and they’re definitely making more money with the cloud integration.
The fact that they have offered free software for so long has been a real cancer to the market which had many software only competitors. In color you’re down to Baselight and Resolve, and Baselight is fighting for survival. Welcome to your mining town economics going forward with a single viable supplier.
I respect what they’ve done on Resolve from an engineering perspective. I’m not a fan of the fact that their tool is generally the 80% solve, not the industry leading solve, and that most of their features have been ripped off other software. They all copy each other, but BMD has taken more than it has given. So not a fan of them as a company as a whole. But they’re already unavoidable in the current market due to dominance.
There are some other factors at play to, but I’ll leave that for a discussion over beer.
Lowest common denominator is a strong value proposition. It’s the one format every NLE supports. And it’s human readable and scriptable. AAF is opaque, XML is much harder to edit without tools.
AAF works great in Avid ecosystem, hit or miss otherwise. XML, well, that’s the point of this discussion. It was invented by FCP and abused by everyone else.
I really think in 2025 we shouldnt have to manually match every repo and timewarp by hand.
What a ridicolous nonsensical work - hoenstly. its such a core thing for the whole workflow to move sequences from A to B and its still just completely garbage.
Well, OTIO is the correct answer. Tell everyone to get off the seat and make it work properly.