Joseph Owens
16
COW Coins
16
DaVinci Coins
Forum Replies Created
-
Feel your pain…
all the way back to the Renaissance. Scene Detect hasn’t really changed much at all.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Ross Shain] “Would love to hear more thoughts from other Resolve users. “
You know I have been running back and forth between the BMD and Mocha booths at NAB almost every year now since like 2010 trying to figure out which one is the mountain and which one is the Prophet. (Please don’t kill me, I didn’t say the Prophet’s name.)
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[leaning less] “Also I want to discover what should I do to get MOV file on timeline in the Edit Selection after adding MOV file in the Media Pool?”
AS to GUI there should also be a rescale selection in the Resolve preferences.
Moving media to the the timeline works in a similar way to most NLEs, but for a fast primer, there is a brief overview of the editing functions available in Resolve 11 here:
https://www.blackmagicdesign.com/products/davinciresolvejPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Sascha Haber] “That workaround works only when the images are rendered as it seems the tracker works before the nodes.
“I think you are right about that, and for that reason, it does not pay to try to track windows into a clip until you have stabilized it, if you are going to do that –> you would need to re-track after the stabilize.
It would be better if there were a “region of interest” box that could be pre-defined. I have never been able to “add” tracking points (believe that to be a ResolvePanel mode), otherwise most of what I do would turn out to be 3- and 4- pointers. Generally, my approach is to go into interactive mode, let the application create numerous points, and then selectively trash everything that is likely not going to contribute to either my window or overall stability — ie, actors nodding or flailing around in an epileptic fit. Or helicopter rotors.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
You should be able to type in almost any number, bearing in mind, of course, that the application will round off to some nearest number, just like they all do.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
Carrying on from Glenn and Juan, there is another useful detail in that if you have an existing grade node tree on a clip, similar to something else, but want to update a tweak to a particular node, “reveal”ing a source correction, selecting one of the nodes to bring forward can be “added” or “appended” to the destination correction… or if there is somewhere it should be inserted to update a particular node, it can be dragged and dropped into that node — essentially “dropping” it into the well. It will overwrite the contents of that node only.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
Its a “Human” thing…
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Athanasios Kamaretsos] “How can you relink the already graded clips from your 1st edit so that you don’t start to grade from scratch”
Generally, that is what the ColorTrace function is for.
jPo“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[lou cann] “Color pick the nose area,”
Uh….
If you had been using some previous versions of Resolve, the default behaviour was to apply a grade to all the instances of a source clip, and if you wanted to do something different with other trims, you would have to create a “Use local” elective or create a second treatment.
Copying grades with all of the processes intact is something we rely on for efficiency, and can be accomplished in more than a handful of ways. Stills, Relative copy, stored memory, colortrace(tm), reveal node tree… it was what this application was made for.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
I was wondering about this a bit myself… H.265 is apparently almost ready…
but a quick search ( you know, the “type some words and click on search-thing”) reveals a couple of thousand hits and even the Microsoft support site states fairly unequivocally that H264 supports up to 2048×2048.
Anything higher will generate a “something went wrong” error message.
I do understand that H264 is nice and compact, but I would question its use as an intermediate edit format, as it is a) processor intensive (because an NLE can interpret it does it mean it is a good idea for editing) and b) Lossy. I mean really lossy. And in UHD or above? Are you previewing your export on a UHD-or-better full-screen display or…?
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.