But I've never had the time to really do a deep dive into Resolve. I've never warmed up to the magnetic timeline - usually I put music on that track and just edit like any other NLE (hence my liking the Cut page and wanting to use the Speed Editor) and FCP is a little weak on the audio side - which is why I've been split. I'm pondering if it's worth my time to look into developing custom macros or whatever to get around these.Īll good points. Specifically, Resolve has a number of UI features that can't be assigned to Keyboard Shortcuts, or are usable in one page but not the other (eg, Cut page vs Edit page). I'm starting to really get acquainted with the controller and my work workflows and editing style now and I'm actually contemplating starting to hack together a controller setup of my own to "bypass" some of the Resolve restrictions. They are focused on the big studios and the "little guys" are the poor cousin who isn't well catered for They are a hardware company first and "cripple" Resolve to push you down the path of buying their hardware They have a way they expect you to work and even though they could alter features to let you work a different way they keep the features so they work their way and make zero sense any other way On the other hand, BM are a very take-it-or-leave-it company: On the one hand, the power of the colour page is unquestionable and the sheer quantity of features in the other pages is undeniable. I have a love/annoyance relationship with Resolve and with BM. The Cut page seems to do rather odd things sometimes (maybe this will be fixed in future versions, but I'll believe it when I see it) The Speed Editor is designed for the Cut page, and while certain things work in the Edit page a lot (most?) functions don't work there, or don't work in the way you'd predict / want You tried Resolve before and it didn't take I'd suggest that you investigate controller options for FCPX.
0 kommentar(er)
