[Mel Matsuoka]

Thanks Reuben…I swear I Google’d the crap for “ffmpeg pulldown”, not to mention searched the ffmpeg/ffmbc manpages but I never found the information in your link until you provided it. For as awesome as the tool is, ffmpeg has the some of the worst/haphazard documentation I’ve ever seen,

[Mel Matsuoka]

[Nuno Garcia] “CP200 panel is old but very cool, works with the old FCP Color, but not with Resolve.
perhaps because ethernet connection”

I don’t think the Ethernet interface is the issue. I use a JLCooper EclipseCX with Resolve, which is an Ethernet-only control surface.

I’d give up various pieces of my own body parts to be able to use the CP200 panels with Resolve. They are unparalleled (besides the BMD panel) in their build quality and quality of touch response. But considering that all traces of the CP200 as a product have been completely removed from Tangent website, I wouldn’t hold my breath for this to ever happen.

[Mel Matsuoka]

Ah, that is a great tip, Walter. Thanks!

[Mel Matsuoka]

Let me be “that guy”, and remind everyone who thinks that $200 is too expensive for Resolve training that this is a product that used to cost six-figures to own and operate only a few years ago.

Paying $200 to get training from a guy like Warren–who has used Resolve professionally since it was first released nearly a decade ago––is hardly a drop in the bucket, if you intend to use this software professionally.

[Mel Matsuoka]

I reported this a few weeks ago:

https://forums.creativecow.net/readpost/3/942755

The workaround is to copy the contents of your sequence into a new, blank sequence that uses a non-ProRes codec (such as the default “I-frame Only MPEG”), then export to ProRes using that sequence, instead of the ProRes native one.

Yes, it’s a total drag to have to do it this way, as you’ll have to re-render everything upon export, but its the only workaround until adobe fixes this.

The other workaround is to replace all instances of Black Video with a selfcontained ProRes Quicktime file containing nothing but Black.

PLEASE submit a bugreport about this to Adobe, so it gets some attention by their engineers:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[Mel Matsuoka]

This has been my biggest pet peeve about Resolve since version 7 on the Mac. It pretty much negates the point of rendering with handles to begin with!

You should send a bugreport to davincihelp@blackmagicdesign.com about this issue. I’m really surprised that this bug has survived in Resolve for at least the last 3 versions. Hopefully the more people that report it, the quicker it’ll get fixed.

[Mel Matsuoka]

Well my question was more about the safety of stringing together seperate–but seamlessly sectioned–assets in a single timeline. I’m fine with pre encoding the assets outside of Encore, if I need to do that.

I’m more concerned that the timeline will stutter at the beginning of each asset if I do it this way, regardless of whether the assets are pre-encoded or not.

[Mel Matsuoka]

[Rohit Gupta] “View menu, UI reset”

Ah, it was right under my nose all that time! Thanks Rohit!

[Mel Matsuoka]

Just out of curiosity, what GPU are you running?

[Mel Matsuoka]

[Lance Bachelder] “Also try turning off GPU (CUDA) just before render and check Maximum Render Quality.”

None of these solutions work. It appears to be a genuine ProRes related bug in CC, because I didnt have these issues with CS6.