[Michael Gissing]

Thanks for that Shawn. Good to know.

[Michael Gissing]

[Herb Sevush]..”it seems to be a lot of feature catch up – object removal, morph efx, auto music ducking are all recent Ppro features.”

Smooth cut/ morph has been in for well over a year. Not sure why that was demoed other than to show it works well. Object removal is fairly new. The demo was more to show how to set it up using the node structure and create the clean plate. I think a lot of editors just didn’t know how easy it was to track and drive.

Same with the music ducking. Using the dynamics on the Fairlight page with side chaining (what they call listen) has been in since Fairlight was introduced, again over a year ago. Same deal that editors might not have been shown how to drive it.

The main updates have been on the Cut page. The others aren’t catch-ups, but reminders and mini tutorials.

[Michael Gissing]

Thanks Oliver. Although I use Resolve mostly to grade, it is always nice to see new features demoed to gauge relevance.

[Michael Gissing]

I must admit I am surprised it has taken any company so long to embrace fcpxml. I know it has gone through some iterations but Resolve seems to have been able to keep up. 8 years is a long time to work out that flavor of xml.

[Michael Gissing]

Can Resolve over ride your Windows default settings?

[Michael Gissing]

[Bill Davis] “Unless you really rig it out, I found it pretty terrible to operate other than on sticks.”

Did you have the OLED viewfinder? With the viewfinder on the shoulder is so much easier than any DSLR held in front with rear screen. I’m old school shoulder shooter and hate having to hold a camera DSLR style with glasses to try and see a screen in bright daylight. Again a classic example of the same gear being loved or not depending on how you prefer to use it.

[Michael Gissing]

I’ve worked with Carsten & Giesla on some of their natural history docos in the days when they had budgets for separate sound post. I know he thinks long and hard about his choices and I totally respect what he says.

Using his logic, I have made different choices of camera & post systems because we all have to be comfortable with our tools and within budgets. It’s just great that we have options that are allowing us all to have the freedom to travel and work remotely. I’ve just had 3 weeks traveling 6,000 kilometres to the Simpson Desert to film a pilot of a TV series, Remote Kitchen. I had 5 days walking over 60 kms following camels and scientists up and down sand dunes. When you have to carry cameras most of the day it makes you think long and hard about ergonomics, weight and reliability.

My choices were Blackmagic cameras, the Ursa Mini 4.6k and the BMPC4K on a Moza gimbal. I didn’t need to edit on location but the editor is switching from Pr to Resolve to streamline the edit process to hand back to me for grade & sound. BRAW allowed me to shoot 4k at a similar data rate to ProResHQ HD. I don’t agree you can zoom 200% without losing resolution however. There might be the right number of pixels but your optical resolution will diminish. I watch everything on my 65″ 4k OLED monitor and I’d like to dispel that idea. Yes you can punch in but 200% causes softening. I otherwise agree about shooting 4k for HD delivery.

[Michael Gissing]

No software is forever so all of us, young or old have to be nimble and adaptable. Those creative 12 year olds will not be using X in ten years because X will EOL before then given the way the software world works, AVID, Pr & Resolve might be gone by then too, who knows.

Stubborn preference for software is an available luxury when you are running the shop, not being an editor for hire. Expecting that software to stay the same or to remain the best fit is folly.

[Michael Gissing]

Edit page or Fairlight page? If you need to get into waveforms and serious audio editing use the Fairlight page and make the tracks as big as you need.

[Michael Gissing]

[Sacha Engel] “It’s clearly connected to the updated DVR, since that’s the only thing
That changed before the problem started.”

When I updated to 16 it specifically asked for an up to date NVIDIA driver. My guess is the old 980 card and driver running in Mac OS is part of the issue. The fact that Mac OS doesn’t support NVIDIA drivers might be the issue. The other thing is 6gig of GPU ram is less than recommended for 4k files.

The reliably better performance of 16 will only be apparent if the GPU and drivers are more recent perhaps. I’m running a PC with offcial NVIDIA drivers and a GTX1080 and your problem is not a known bug.
If you did the install and kept V15 as I suggested you can always stay on 15 until you can sort this out.