Apply the same Clone Fix in every frame
Is there a way to apply the same Fix to every frame in a segment?
I have a piece of dust sticking into the frame and I'd like to cover it up using a Clone Fix. Because it's a static shot, I can literally apply the exact same fix (Local Clone, X-Offset 150pixels) in every frame and it would be great if I didn't have to do this manually in each and every frame.
-
Hi guys,
There are different ways to apply DVOs to multiple shots:- On the right side of the interface, click on the Mems button, it'll open a panel on the left side with new options
- With the Mems button open, You'll see two buttons, Shot and Notes. Here, you can choose several ways to see the shots on your timeline; if you select Event, it'll show the cuts (events) on your timeline. Here, you can click on an event, and, on the top-right part of the interface, you can see everything that has been done to a shot, including grades and FX layers. The yellow square is the selected event and the blue square is the current timeline event.
- If you select a shot that has a Tool applied, select the effect using your mouse on the top-right menu and click on Rec; this will recall the effect.
- You can select multiple shots on the timeline using the mouse and then click on Rec to recall multiple shots
Another method is to click on the Notes button, where you can save notes and select them to apply to multiple clicks using the same method.
To save a note, click on the button with the down arrow on the right of the camera icon.
-
Ian Smith Thanks for the info. I saw this in a different thread already but could not believe that's actually the answer.
Why is this so horribly convoluted and inside-out?
Here's how this SHOULD work. I should be able to right-click an effects track on the right hand side of my screen, find a menu entry that says "Copy effects" and click that one. Then I should be able to highlight and select all the cuts I want to apply it to in the timeline, right-click the mouse and select "Paste effects."
It's a straight-forward action I am trying to perform and you guys make it unnecessarily difficult, complicated and convoluted for no good reason. You shouldn't try to re-invent the wheel. Thousands of other software packages have established and refined this kind of procedure over the years. As I mentioned elsewhere, the usability of Phoenix is nightmare, and for absolutely no good reason.
That aside, whoever thought REC should be a valid abbreviation for RECALL should really pick up a book about software UX/UI design to learn some of the basics. REC is universally recognized as RECORD, which is diametrically opposite to what your recall function does. And whoever came up with the term "Recall" to begin with? The universally established term for this kind of action is APPLY, so why did you feel the need to brew your own nomenclature?
-
Select Pan and Scan effect.
Select Shapes then draw a mask around the dust.
Then go back to the Pan and Scan tool to adjust the X - offset 150 pixels.
It will hold on to every frame in a segment.
You might need to use REC to save these settings if it reappears in another segment
Phoenix is an amazing tool with world-class support. It's the restoration community that needs to share ideas of how to use the tools in order for us to all grow as artists.
-
Michael Coronado Thanks for the tip, Michael, but it did not work Part of the problem might be that I'm already tracking a different shape in the same shot and Phoenix just can't seem to properly handle multiple shapes at the same time. I tried your process with "DVO Fix" instead of "Pan & Scan" because that's what I want to do—fix, not pan&scan—but it did absolutely nothing.
I thought Shapes affect the Matte painting layer only, anyway, so I wasn't surprised. I've never seen it used for anything but Matte painting, but I'm no expert, so perhaps there is a feature hidden in there that's been undocumented or unnoticed by me.
I totally agree that Phoenix is an amazing tool but unfortunately, it's a tool that is working in a reverse-engineered kind of way. It solves a technology problem and then tries to build some sort of a UI around it to allow people to use it. What it should really do is, ask "What are restorationists trying to achieve?" and then build a sensible goal-oriented UI around that process and only THEN go down to the technology level, because as amazing as it is, in terms of usability, Phoenix is truly not quite there, making everyday processes unnecessarily convoluted and obfuscated.
-
