Eddy Juillerat wrote:Hello folks.
Reference manual: 3000 pages,
Advanced editing manual: 380 pages,
Fusion manual: 340 pages...
Is it "the more page you have, the more clever you are"?
The manuals are supposed to give you as much information as possible. And that's a good thing. They are extremely well written.
They are not short "How to get started quickly" guides. And they are not meant to be. They are meant to be in-depth references for Resolve.
On the other hand, have a look at Adobe's manuals...they suck.
Resolve's manuals are not "unreadable". On the contrary, they are very pleasant to read, but I agree that it can be heard to search in them because of their size. So additional chapter-based PDFs would be handy.
Eddy Juillerat wrote:Is it just me or I CAN'T READ these manuals?
I started reading big chunks of the Resolve manual last year and found it to be a very entertaining and interesting read with just the right pacing and amount of information. I loved it, so maybe it is just you.
I also started reading the Fusion manual years ago and I enjoyed the amount of information a lot. I learned a lot of things from it.
Eddy Juillerat wrote:When I search for a precise question, i can't find it.
This is not meant in an offensive way: Improve your searching skills.
There's an advanced search in Acrobat Reader. Select "Include Bookmarks".
This way, all bookmarks from the table of contents to sub-chapters will be searched first.
Eddy Juillerat wrote:Search for "Tracker", I step upon dozens of word "Tracker" but not one explain to me how to place the Tracker node in the composition. No example of nodes linked in a way that produce the attended result.
When I search for "Tracker" (including bookmarks), starting at the top of the document, the first result I get is "Using The Tracker Node", which is a 20 page chapter for just using that node including node graphs. That should be, what you were hoping for?
In Standalone Fusion, you could just hover your mouse over the inspector and press F1 and you'd get the help for the selected node. I think that didn't work in previous Resolve versions. You might want to try that in the current version.