[Paul O’brien]

In my pond, blackmagic design (BMD) started off as a small, almost non-existent whisper, but this year the company’s new content stirred up a pretty good thread amongst the local shooters and cutters and for the first time people took notice or Resolve (15) . Mind, it’s a small group, but the consensus was such that “Adobe is no longer an enjoyable solution, it’s just what we use, more begrudgingly than otherwise. And I can use FCPX too.” At Adobe’s monthly/yearly subscription model, I think a certain type of fatigue has hit. So an alternative is at least welcome.
That, and my experience has been that Adobe software/premiere pro has gotten more and more buggy, glitchy, and unreliable over the last couple years even after getting a new up-to-date system. But no, across computers from 2012 (decidedly old and time to be set to pasture) to 2018 (new, and nothing odd about the setup in anyway), Adobe stuff has constantly been the only thorn in my computers’ proverbial sides.
I dabbled with Resolve 14, and it was OK as an alternative, not bad, but I couldn’t switch over just at that time (blast Adobe and their legacy!). I haven’t touched 15, but in my personal life, I’m going to have the opportunity for a hard, clean break of everything Adobe (asterisk I have a legal license for Creative Suite 5.5 so, no CC for me, that is) and switch off Adobe cold turkey to try out Resolve (and maybe the other programs in the package). Plus he pocket cinema camera 4k is very intriguing, and barring horrible reviews it’ll be my next purchase as I also have the good fortune to wait and see if Canon will update their full frame hdslr (or mirrorless, I’m indifferent to the camera format) with competitive 4k video.

[Paul O’brien]

Thanks all for your input.

I see how this could be useful for P2. My media these days is all hdslr .mp4/.mov so nothing particularly intensive. I’d be interested in knowing what metadata comes across via the premiere pro media browser compared windows explorer.

As for the media browser jumping and flashing, I followed that thread of that issue. It seems the media browser wants it cache on the C: drive . But my C: drive isn’t large (256GB) and it’s not for media cache because I’ve done that and the C: drive fills up in a week after even a light, low asset number project. That’s frustrating.

Ah well. Thank you for sharing your experience and workflows.

Cheers,
Paul