Nate Weaver
Forum Replies Created
-
Ah, nice one Illya. I’ve trying to figure out a way to restrict the vectorscope to read only a portion of the frame, but this will work nicely.
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
Or going from 50 to 51 on the blur knob
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
“I know for a fact that Compressor doesn’t do a good job. Thin lines and fine details will flicker, and it will be kind of jumpy in “crash pans” or fast motions.”
If you’re seeing “jumpy” in pans, you have a framerate conversion issue in your downconvert.
Given all the accelerated hardware at Resolves disposal, I’d be very surprised if between the two scaling algorithms, and a point here or there on the blur panel as a track node, you couldn’t get a very high quality down convert.
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
I find with last years 8 core, ProRes 444 bogs a little bit.
I understand that codec decoding is done on he CPU, but hoping maybe somehow getting another GPU will take some other tasks off the CPU and maybe make things like PR444 quicker?
Or am I full of it?
Clearly these GPU can do a lot of work. I just wish some of these things that are killing us like Red debayering, codec decoding, etc could be done on GPUs instead of the CPU.
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
As i understand it, there are image display parameters that can be embedded in the headers of QuickTime files. I always chalked these differences up to some programs heeding them, some programs ignoring them. Add RGB to YUV conversion issues and sometimes not knowing if a program is writing RGB or YUV to that 444 container, it gets messy indeed.
I just deal with it. ProRes 444 to me is a great thing. Not everything can be uncompressed at the rates they’re paying us these days 🙂
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
I wouldn’t call them magic. Just helpful.
All they do is work like the plain + and – buttons right next to them, but with added softness on the qualifier. I’m finding +S is helping get a qualifier quick, and then if I grab too much then I dial it out on the knobs (or use -S).
I was previously hardcore about using knobs to qualify, but realizing the mouse is better to get it started (and many times better in every way).
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
Funny, my experience is the opposite. I always thought Color was lousy at getting good qualifiers quickly, and then was very happy when learning the Resolves….
I finally just learned what the +S and -S buttons do too, so my qualifiers are getting even beter…
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
I’d hate to see this just die…?
I’ve been reading some of the same sections of the manual over and over and it seems there’s references to ways of doing this, but no info…
…which is bringing me to the one of the most popular questions of late, is this a full panel thing?
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
Just one node in the “track” portion (look next to “clip” in the nodes window) will do your whole timeline.
I keep hearing about rippling changes to multiple clips in the manual, that sounds like they’re talking about something besides the ripple that happens in a created group. Does anybody know more about this?
Specifically, in the “New in Resolve 7.0” section in the manual:
“Color Control Enhancements:
-Apply a ripple by adding a node to the end of node graph
Automatically ripple a grade to any number of clips by adding a node to the end of each clips’s node graph with the ripple grade”
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net -
I have a project with the G13 I started, and have yet to finish.
My goal was to somehow get keys on the G13 mapped to memories currently only available by mousing if you’re using the Wave.
Using QuicKeys, you can map buttons on the G13 to actually perform mouse action macros, which is really only possible because very little on the Resolve GUI moves around with use. In particular the actual thumbnails in the stills gallery.
Anyway, I got as far as being able to recall memories using buttons on the G13 roughly mapped to the grid in the gallery, but soon thereafter realized I needed to do ANOTHER set of macros to be able to capture a still to a given memory (I was using the A-Z memories). At that point I put it down for another day and have yet to pick it up again.
At any rate, this was a very long way of saying that any G13 users should download QuicKeys, as it opens up the possibilities with that keypad greatly.
Nate Weaver
Director/D.P., Los Angeles
https://www.nateweaver.net