Forum Replies Created

Page 1 of 6
  • Resolve remembers the link to your rendered file as long as the Render item remains in the Render Queue. If it’s still there, then an XML exported from the Edit page will link to your graded media. If you removed the item from the queue, then the XML will link to the original, ungraded media. There is no way to get Resolve to remember where the graded media is, you need to rerender.

    Or, if you feel lucky, try this: manually import your graded media into a new Resolve project, then import the XML, but deselect “Automatically import source clips into Media Pool”. It should reconnect to the graded media in the media pool, but only if it’s got proper timecode and reel ID. If this works, then export a new XML.

  • Jean-françois Robichaud

    November 27, 2012 at 7:49 pm in reply to: Shooting Computer Screen for Composing

    The green card is useful if any foreground subjects are located in front of the screen. Unless one likes to do unnecessary roto work.

    Markers on the green card’s corners can be great for tracking (they can be a different shade of green so they will key out).

    Screen reflections could be faked by shooting whatever is supposed to be in the other direction and compositing that as highlights on the computer screen. I’ve done this by roughly animating a still picture of overblown windows, overlayed over the computer screen. The illusion was perfect.

  • Jean-françois Robichaud

    November 27, 2012 at 7:30 pm in reply to: Common Causes of Crashes at Render Time?

    Low RAM could definitely be partly responsible for this, but it’s impossible to know what software of hardware conflicts might exist on your system. Try turning off all Open GL acceleration. Kill all unnecessary processes before starting the render.

    There are a few workarounds you can try. First is rendering as an image sequence. Even if After Effects crashes halfway through, whatever was already rendered won’t be lost. Then you just need to render the parts you’re missing.

    Also, try pre-rendering parts of your composition, and reinserting that into a copy of the final composition.

  • Jean-françois Robichaud

    November 27, 2012 at 7:25 pm in reply to: Propeller blur in post

    You can use ReelSmart Motion Blur in most NLE or compositing application. It got me some pretty good results on video that was shot with a high shutter speed. I guess it really depends on the nature of your footage. You can download the trial first: https://www.revisionfx.com/products/rsmb/

    The standard version is 90$. It’s worth it.

  • Totally agree with this. Having the actor write on the plexiglas for real and flipping the shot in post would yield the most natural result (though maybe not the cleanest in terms of the writing).

    Having the actor pretend to write in mid-air and adding the text in post is a bad idea IMO. When people write for real, they use the visual feedback of what’s already on paper (or plexi) to guide their movement. If you remove that visual cue, the movement will be off (like writing with your eyes closed). When tracing the movement of the pencil in post, the result is distorted letters and overwrite. The tracing must be tweaked and smoothed somewhat to get legible and aesthetically pleasing writing, but that means lines will not appear exactly at the location of the pen tip.

    To OP:
    As for shooting through plexiglass, if you’ve never done it, you must run tests during pre-production and prepare for a somewhat complex lighting setup. Backlight will amplify scratches and dirty areas on the surface: flag your backlights, treat the plexiglass with care and wipe it good between shots. Your actor’s hand should never touch the glass, as it will leave oily residue. Front light will reflect in the glass, so flag it, move it further to the sides and/or up to get rid of reflections.

    You also need to test multiple types of markers to see what looks best, in terms of opacity and colour. It must absolutely stand out from the background.

  • Position uses sub-pixel values, so doing an equality comparison isn’t going to work very well. You could use a tolerance, depending on how close you want to be. For a tolerance of 2 pixels, try this:

    p1 = thisComp.layer(“BloackB”).transform.position;
    p2 = position;
    tolerance = 2;
    if (length(p1, p2) < 2) 100
    else 0

    As for layers that are parented to nulls or other layers, I can never work it out of the top of my head, so I’ll let others work it out.

  • Jean-françois Robichaud

    September 27, 2011 at 6:44 pm in reply to: Damn autosave stops working and I’m pissed

    I upgraded to 10.0.1, but I am still on Snow Leopard.

    By the way, it happened again, I just lost another 30 minutes of work. I can’t believe this!

  • Jean-françois Robichaud

    July 28, 2011 at 2:39 pm in reply to: Where are we TODAY?

    [Neil Goodman] “The fact i have to wait for it to guess what kind of edit i want to do (trim/slip/roll/ripple) depending on where i put the cursor slows me down right there, and there and its extrmely clunky. Picking the best tool and just using it, instead of hoping it knows and waiting for i to tranform to the tool you want, is ten faster. “

    What do you have to wait for? Using the Trim tool, you can perform ripple, roll, slip edits, depending where the cursor is positioned (and slip edits with Option). You don’t need to wait for anything. You also have the ability to nudge cuts, extend them to your playhead with shortcuts, etc. Feels pretty responsive to me.

    [Neil Goodman] ” The Playhead jumps all over when you click in the project or story window or whaever you want to call it. FCP7 only effects the playhead if you click up there, not anywhere in the window. So ill have the playhead set on an inset point, click a clip and the playhead moves there , Not cool at all.”

    This drove me nuts at first until I found out all you need to do is hold OPTION while clicking on a clip to leave the playhead where it is. So it’s cool after all.

  • Jean-françois Robichaud

    July 24, 2011 at 3:29 pm in reply to: FCPX Text Search

    It just comes down to using the wrong tool to achieve what you want. Keywords are useful when they are short and multiple:

    – “Horse” is a good keyword; there will be many instances of “Horse” in your event, and you can create a collection that contains all instances.
    – “the horse was running very fast” isn’t a good keyword. It’s too specific, it’s only going to have one instance, so making it into a keyword isn’t efficient.

    Rather than creating keywords with very long sentences, use the Notes column. First make a selection within your clip and either create a favourite (hit F) or assign a relevant, simple keyword to hit (such as “jockey”). Then write whatever you need in the Notes column for that particular selection. Notes are searchable through text searches. I think this is exactly the behaviour you are looking for.

  • Jean-françois Robichaud

    July 22, 2011 at 8:04 pm in reply to: Would this be possible as effect.

    One way to do it would be to turn the transparency of the first clip on/off rapidly and putting the second clip under the first.

Page 1 of 6

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy