Sun Feb 09, 2025 12:15 pm
I have no inside info but was a dev for 20 years sometimes running a dev team. So here's my supposition:
Pyxis and the new Ursas are the current flagships so BMD's reputation rides mostly on them right now. They likely have one team that works on a mostly unified OS for the cameras. But there's plenty of code that's specific to the hardware.
Naturally BMD is focusing its resources on getting the new cameras working just right. Any devs sent to other cameras probably take away devs from that effort. That's not even taking into account all the work that goes into validating a new firmware release.
So it's totally understandable that a small dev organization can't effectively work on multiple cameras. The new ones may share enough internals to make them easier but adding in an older generation product right now would probably really hurt their productivity.
I wish it weren't that way but I'm not angry with them for what I imagine are the realities of the situation. I just hope that marketing et al will give them enough breathing room once this cycle is done to go back and integrate the latest OS into the other cameras and fix outstanding bugs.
I do wish they'd share their expected timetable for this. That's one aspect of their policies I don't agree with. Seems to me they could do it without hamstringing their flexibility and get a bunch of goodwill by doing so.
Director, Editor, Problem Solver. Been cutting indie features for 24 years. FCP editor from version 2 to 7.
Resolve 20.0.3B
MacBook Pro 16 M1 Max 64GB RAM, macOS 14.7.2
MacBook Air 13 M1 8GB RAM, macOS 14.6.1
BMPCC4K 8.6 beta
BMCC6K 8.7 beta