[John Michaels]

Thank you for the response!

I seem to remember that creates subclips though, and what I’m looking to do is to “update” the master clip itself, because our editors have already began to cut with the footage (they maintain the MOS channels at first), so ideally the updated audio flows right in to their timelines as it does currently with the re-ingest from tape.

[John Michaels]

Same thing in Switch an Quicktime X.

I’m doing this in Vantage (not Episode) using the Quicktime (Telestream) encoder. For my Resize filter, I’ve tried both “Crop (Center Cut)” and Manual, with 0 crop and padding on top and bottom, and 240 pixel crop in from left and right. Both resize settings yield the same result. I do have the VBI settings enabled (which is the default) for 4 upper and 2 lower. I’m sure disabling this (setting it to full frame active picture) would get rid of the bars, but again, aren’t they supposed to be there for 486 material?

[John Michaels]

If you would prefer to maintain the folder structure as it exists on your SD card, you can right-click the top-level folder in Resolve and choose “Add Folder and Subfolders to Media Pool” to go in and find all the footage for you.

Note that at this point, you should have already copied the contents of your SD to a hard drive of some sort so that you’re working off a drive. Davinci won’t physically copy any files, and you certainly don’t want to be working off your SD card.

[John Michaels]

Thank you all. I figured it out for myself; it was a dumb mistake. For those Googling this: I saw that my project settings were set to 10-bit monitoring, when obviously it should be set to 8-bit since that’s all the Intensity Shuttle is capable of.

[John Michaels]

[John Vaudin] “purchase additional licenses to enable running multiple jobs simultaneously on different processors (or cores)”

Ah, that’s what was confusing me, since I’m licensed for one processor, but was assuming I could put different jobs on different cores on that one processor. That’s ridiculous, but thank you for the info.

[John Michaels]

Thank you for the insight. I was thinking it was an issue resolving the paths of the referenced files, but the timestamp issue makes sense, too. However, shouldn’t flags such as +genpts and +ignoredts solve this issue? In my experience, setting these flags does not solve the issue.

[John Michaels]

If you have a good relationship with the DP, you might gently suggest softer lighting and some kind of mist filter in front of the lens (I’m partial to the Hollywood Black Magics from Schneider) for future projects. I’ve never shot film/4K closeups without SOME kind of filter, unless I needed an intentionally grating look.

But unfortunately for you, this current problem is now yours to deal with. Try tracking her face with an oval window, and within the window, try to flatten out the skin tones so the blemishes aren’t as noticeable. Then apply a blur and go a little overboard. With all your adjustments in this node, go a little overboard. Finally, adjust the alpha of the node to back it off and bring in a little of the original skin texture before your adjustments (you probably don’t want completely smooth, plastic-y skin).

Play around with that a little; maybe it could help?

[John Michaels]

I am still experiencing this problem intermittently, though not as often as I used to. I’ve gotten in the habit of transcoding any long GOP stuff (such as DSLR footage, where I’m most likely to encounter this error) to a high-bitrate DNxHD. While I’d much rather work with original footage, this is one way around it.

I’m curious: does anyone encounter this problem with footage that does not have audio tracks? Or while audio is disabled in Resolve?

[John Michaels]

Hmmm. While I’m glad it has solved your problem, I am not so sure it’s completely the solution.

For several projects, I had written a script to use FFMPEG to repackage all the videos from MOV to MP4 containers, just to see if maybe Resolve would use a different decoder than QTDecoder (which it did not). I still got the errors, and I am certain there are no corrupt videos in the project. Even if there were corrupt original MOVs, ffmpeg would have written proper headers and such to make the new copies stable.

[John Michaels]

[Anish Prithviraj] “When you say that QTDecoder stops responding, is this happening as soon as you add a 5D or 7D H264 file to the media pool? We tried that on our setup here but did not run into a crash/give the error.”

In my situation, I have already added H264 clips to the media pool and into timelines. The error seems to occur when it is building the thumbnails, because it only occurs when I am on a Page that is displaying thumbnails. For example:

– In the Media page, if the Media Pool is set to Thumbnail view, QTDecoder stops responding after it has loaded a few thumbnails in the Media Pool(such as when I first open my project since it starts on that page).

– In the Media page, if the Media Pool is set to List view, everything is fine until I switch over to the Color page which displays Thumbnails in the timeline. QTDecoder will stop responding at that time.

Attached is a screenshot so you can see it has loaded most of the thumbnails in the timeline, except for the last three or so on the right, at which time I got the error.

I will email Blackmagic Support about this. Thank you.