John Tissavary
Forum Replies Created
-
Dunno if it’ll work, but try removing and re-adding the drive in the preferences database.
JT
John Tissavary | colorist | owner
The Post Collective -
Your point is well made – but auto-save can work if you pipe it to a different location. That said, saves in general take way too long.
I have a project right now that is duplicated in Scratch & Resolve (same number of source media, edits, etc…), with grading in Resolve and comps/ paint in Scratch – all on the same workstation. Takes nearly a minute to save in Resolve, 5 seconds or less in Scratch, both are writing to an SQL variant database on a local (internal) drive.
JT
John Tissavary | colorist | owner
The Post Collective -
Which version of Resolve are you using? I had a problem like that in v8.01 where it would unexpectedly re-conform if I added new media to bins.
If you’re using v9.03 then I’m a bit surprised that this would happen unless you explicitly reconform.
John Tissavary | colorist | owner
The Post Collective -
Had something like that a while ago, was either out of drive space or permissions issue can’t remember…
JT
John Tissavary | colorist | owner
The Post Collective -
You’re missing the point that Joseph made. It’s not the h.264 QuickTime that’s the problem, it’s the QuickTime player itself. If you view the h.264 in resolve, does it look like you would expect? If so, try viewing the QuickTime in VLC and see if that doesn’t look a bit better. If it does, advise your clients against viewing anything you send them in the QuickTime player.
JT
John Tissavary | colorist | owner
The Post Collective -
What I would really appreciate is hierarchical nesting – the traditional parent > child model for animation. That way you’d track one window, and any ‘children’ of that window would follow suit. Re-piping curves and such would be nice too, but this would be the simplest way, imho, and would involve potentially less mouse-clicks and GUI.
John Tissavary | colorist | owner
The Post Collective -
Hi Peter. You say All > Color > PTZR modes are available as a keyboard shortcut, but how can we know that when there is no keyboard shortcut information available anywhere for v9? Is it not high time that this is either folded into the manual or available as a support doc like it was for v8?
So far this is perhaps the single most frustrating part of the V9 release for me. I use the Resolve panels, but I also rely heavily on keyboard mapping, so this is a major headache that could be so easily solved.
thanks,
John T.
John Tissavary | colorist | owner
The Post Collective -
I’ve worked both ways, but prefer to have the feature all sitting in one project. Haven’t had a problem in v9. Obviously load times are longer vs. one reel per project, but then again I don’t have to load 5 or 6 projects to get through a single pass, so it all depends on where you want to do your waiting – all at once or in bits & pieces.
JT
John Tissavary | colorist | owner
The Post Collective -
Not doable in any efficient way. CDL are not anywhere near sufficient for this, so you’d have to at least pass cube luts back and forth. Without some measure of custom development this would mean exporting a lut per grade from Resolve, converting that to a flame compatible lut, and then ignoring anything that had a window or animation keyframe or key or whatever. Seems like quite a headache for something so minimally functional.
JT
John Tissavary | colorist | owner
The Post Collective -
Place playhead at the frame you wish to start the animation.
Create shape / node.
Open node dropdown in Keyframes window (click triangle next to node number) and enable auto-keyframing for Linear Win (or whatever shape you’re animating)
Make an adjustment to the window to set the keyframe, or RMB > Add dynamic keyframe
Move playhead to frame where you wish to set final keyframe
Adjust shape- keyframe is set automatically.
disable autokeyframe by clicking in active ‘A’ icon in Linear Win entry in Keyframes window.
JT
John Tissavary | colorist | owner
The Post Collective