Just thought you might want to post errata to the manual found by readers.

Page 137 Using Proxies to Improve Performance

Turning on one of the proxy resolutions reduces the working resolution by either half or a quarter of whatever the current Timeline resolution is for your project. Working at a temporarily reduced resolution increases your workstation’s real time performance, while the resolution independence of Resolve guarantees that veryevery window you draw and sizing operation you make scales correctly to the actual resolution of your project.

List Backups:.... When you load an autosave backup, the current project is lost, and completely replaced by the autosaved project.

In DR 12.3.2 the Load of an autosaved project copies the autosaved project and creates a new entry in the Project Manager. The current project doesn't close nor gets replaced, even the windows still stay open.

btw. If this behaviour stays I would recommend the feature of loading the backups also to be in the project manager, as at the moment you would need to load a project (it doesn't even matter which one, in "last backups" you can access backups of other projects as well) for loading a backup.

i've been going through the manual and there are literally hundreds of typos. I'm going to do my own write up and send it to BMD. I could make a huge thread with all of them in but it might be a little dull.

Tom Early wrote:i've been going through the manual and there are literally hundreds of typos. I'm going to do my own write up and send it to BMD. I could make a huge thread with all of them in but it might be a little dull.

Thanks TomEasier to just send it or a link to it to me via PM given I'm the one who need to allocate resources to update it.

Tom Early wrote:i've been going through the manual and there are literally hundreds of typos. I'm going to do my own write up and send it to BMD. I could make a huge thread with all of them in but it might be a little dull.

Thanks TomEasier to just send it or a link to it to me via PM given I'm the one who need to allocate resources to update it.

Peter

I PM'd you about the first 100 pages worth last November is that format OK to use for the rest? I also have the pdf with the relevant sections highlighted that could go with it.

Same for me. The PDF does seem to somehow get 'installed' with the software, but it's never there in the ZIP file on Windows. The only file in that ZIP is the executable, which begs the question, why ZIP it? You don't save enough room to be worth it. There's only one file. Just link to the .exe.

Jim Simon wrote:Same for me. The PDF does seem to somehow get 'installed' with the software, but it's never there in the ZIP file on Windows. The only file in that ZIP is the executable, which begs the question, why ZIP it? You don't save enough room to be worth it. There's only one file. Just link to the .exe.

I don't know if this is the reason here, but many organizations do not permit the downloading of .exe files for security reasons.

According to the August 2017 manual, you can shift-click on Custom Curves to add a control point at the horizontal position of the pointer, but you cannot

p790 mentions changing a window’s centre of rotation, but this isn’t possible

p790 also mentions changing the size/aspect of a power curve or polygonal window by cmd-dragging a control point, but this isn’t possible

These problems aren't new to this version mind (either of the manual or software), and I've reported them before. So is this a problem with the manual or bugs in the software? I've been using the Mac version, Studio mostly

Link groups (Fairlight page) are only mentioned a couple of times in the manual, but their role and importance is never described.

As this thread shows (viewtopic.php?f=31&t=63130&p=359135#p359135), this really needs to be addressed. Also in the same thread is a trick involving using Boom in conjunction with lowering the level on a given channel to negative infinity, which may also be helpful to include.

Page 1125 (Fairlight) mentions "Using the Vertical Zoom Slider" twice. I assume the second one should refer to the horizontal zoom slider.

A few paragraphs down, I think that "Using scroll controls of your pointing device to scroll horizontally:" should be higlighted (similar to the paragraph after it) instead of "Using the scroll wheel (or"

Page 1185:"To apply an audio filter to a track or bus in the Mixer" seems to have the same text as "To apply an audio filter to a clip" on the previous page.

The manual not only doesn't mention this, but it never even mentions ACES LMT once in any of the text, nor in the ACES processing flow diagrams. These details of ACES really should be given proper coverage in the manual.

On page 742 in the manual it says that: "The default Intensity of 100 results in that curve exerting its full effect on the image, while an intensity of 0 results in that curve having no effect on the image."

For me at least it appears that a value of 0 in fact reverses the effect of the curve adjustment, while a value of 50 results in the curve having no effect on the image.

Actually it probably would make more sense that a value of 0 would be neutral, as it is written in the manual, and -100 would reverse the adjustment.

Tom Early wrote:In the grading order of operations diagram it doesn’t mention offset

I am fairly certain that Offset is considered part of Primary, so it would be in that stage of the order of operations.

This diagram is about the order in the processing pipeline before/within/after nodes, not the operations a colorist performs. Offset comes after Lift/Gamma/Gain, so this tells you that you don't want to be adjusting luminance with Lift/Gamma/Gain after making a colour adjustment with offset in the same node, since doing so will change the balance and you will have to adjust offset again.

This diagram is about the order in the processing pipeline before/within/after nodes, not the operations a colorist performs. Offset comes after Lift/Gamma/Gain, so this tells you that you don't want to be adjusting luminance with Lift/Gamma/Gain after making a colour adjustment with offset in the same node, since doing so will change the balance and you will have to adjust offset again.

Yes but, I'm pretty sure that mathematically if you do LGG then offset, or offset then LGG the result will be the same.

This diagram is about the order in the processing pipeline before/within/after nodes, not the operations a colorist performs. Offset comes after Lift/Gamma/Gain, so this tells you that you don't want to be adjusting luminance with Lift/Gamma/Gain after making a colour adjustment with offset in the same node, since doing so will change the balance and you will have to adjust offset again.

Yes but, I'm pretty sure that mathematically if you do LGG then offset, or offset then LGG the result will be the same.

If doing them in the same node with fixed values then you are right (at least, for lift/gain/offset; gamma may be different*).

But in the real world this assumes you will be adjusting offset literally at the same time as lift/gain. Take a solid colour clip (for illustration its easiest if it's a single colour rather than a tinted greyscale or proper image), and make an offset colour adjustment. In the same node, now adjust gain and/or lift luminance controls. Looking in the vectorscope, as you do this you will see that saturation isn't the only thing that changes, but hue does also. Therefore you will need to rebalance. On the other hand, if you adjust lift/gain first (can include both colour and luminance changes), and then adjust offset luminance, then neither saturation nor hue changes. If you are doing this with a proper image then the results may at first seem less obvious, but just compare the behaviour of adjusting lift/gain luminance in the same node as an offset colour adjustment with what happens if you do so in a subsequent node.

[*If you take an image, make adjustments to Lift/Gain and Offset (adding Gamma to the mix actually seems to lead to funky results) in the same node, then add 2 new versions which split the Lift/Gain and Offset into 2 nodes, one with Lift/Gain first and the other with Offset first, then the version that has an offset node before a lift/gain node will be different to the other two, which will be the same as each other. They will also be the same as a node structure that places Lift/Gain and Offset nodes in parallel. For some reason, if you add gamma operations then no node structure will match the result of the single-node operations, not even when done in parallel, and when ensuring no clipping takes place at any point. Note that this test needs to be done either with a tinted greyscale or a proper image, rather than a solid colour].

I'm new to this app but have spent a good deal of time in the manual lately. I believe both the screenshot on page 84 and a few of the related options presented on page 85, need to be revised. Everything I've read suggests there are now (in the app) fewer options than there were before. Specifically,

Use Display GPU...Use GPU for Red Debayer, and Use Red Rocket...

are no longer applicable as far as I can tell. If its the case they're only applicable to the studio app, it needs to be made clear in the section intro or a sidebar, but I've not read anything in the manual intro or elsewhere that suggests this is the case.