Marc Wielage
Forum Replies Created
-
Uncheck Flat Pass and try again.
-
Look at the files in the Media Page and check to see what the file attributes are. If they’re the original files in the original place, then there’s no problem. It’s possible you’re seeing optimized files, and the path location and file type should tell you that.
-
I would bet this is a scratch drive issue. Double-check the Preferences and make sure the drive you want to use is at the top of the Media Storage list, and that there are no permissions problems. At worst, clear out that list, rebuild the list, and recapture all the stills and they should stay put.
Due to some cache files getting a bit out of control, I went to an external SSD scratch drive a year or so ago, and have yet to lose any stills or cache files. (So far.) One thing to remember that while Resolve looks like a color-correction program, but in a way it’s really a big database that keeps track of color, stills, and edit decisions; if the database structure gets even slightly corrupted, bad things happen. When you know that going in, often you can anticipate the problem before it happens.
-
The curve editor did change in the last release or two, but it is what it is. I personally don’t have a problem with it, but I only lean on the curves in very small doses, usually Sat vs. Hue, Sat vs. Sat, or Sat vs. Lum.
-
Very dense blacks are a huge challenge for any compression engine. My response would be to try to go for an image hosting site that has less compression. Vimeo Pro might possibly be a solution.
If you put up some test signals with just a black screen or various shades of gray, you’ll often see the same problems. These are known compression artifacts. Compression is evil.
There are also issues with 8-bit video in general from DSLRs, but if what you see on your own display is good, and it got a lot worse online, clearly the problem is the online compression. Whether you can change your own compression method would be a question of experimentation.
-
Check to see if the “Render Flat Pass” checkbox is on in the Deliver page.
-
Alexis is the only guy I know who has actually done training videos specifically for using Resolve as an editor, and they’re fairly well-done.
https://www.rippletraining.com/products/davinci-resolve/editing-finishing-in-davinci-resolve-12/
Be warned that there are some new editing features in 12.5 that go a long way towards improving the program, so even though this training video is only about 6 months old, it’s already a little out of date. But the basic concepts are still good.
-
Reset the entire GUI and see if the default size is OK. Workspace -> Layout -> Reset GUI Layout.
If not, then I’d consider lowering the monitor resolution to make the on-screen graphics bigger. I’m using 2550×1440 and the Curves window is fine for what I need.
-
Resolve is a demanding program in terms of RAM speed, CPU power, GPU power (and RAM), and hard drive throughput.
Recommended hardware specs are at this link:
-
MTS files are bad voodoo. I would convert them to something easier for a post workflow, like ProRes (for Macs) or DNxHD (for Windows). In theory, the sound should come over with the files.