[Sandeep Sajeev]

A lot of the stuff I end up getting is double system. I have the exact same beef. What I end up doing is key wording all my stuff separately prior to synchronzing. Then I set up a Smart Collection for the Synchronized Clips – the keywords stay consistent, so I can easily correlate the Synchronized Clips to the Individual Clips, if necessary.

Then I use Auditions a lot to cycle through various takes.

It’s not ideal, and I wish the metadata would carry through, but it doesn’t. So this method works for me. I used it on a project recently with 16 days worth of rushes, multiple cameras each day, in total about 3TB worth of DSLR H264 rushes. Went smoothly.

[Sandeep Sajeev]

Is there a way to select a bunch of clips and clear their PIOP’S ? Or does this have to be done on a per clip basis ?

[Sandeep Sajeev]

I totally agree with you Jeremy. This affects the way I work too.

I thnk if Apple had designed it such that the PiOP’s were deactivated (still visible, but not actionable without a keystroke to turn them back on) it would have been better.

And not showing the PIOP’S in list view is folly. X is tracking them, so why not show them? Forcing us to use the filmstrip view is a problem on a single monitor set up – the new iMac’s for example – in Events with a fair amount of footage. Legacy showed you when clips had I/O set in the Browser, and it was instantly visible.

I can see why this was such a flashpoint with the development team.

[Sandeep Sajeev]

Yeah the PIOP’s thing has been done to death. As you say, spend enough time on anything and it will eventually become second nature.

I’m annoyed now that I have to wait until I finish the current project I’m working on before I can download and try out all this new stuff!

Jeremy, can you confirm that there’s no source time code in the event viewer? What happens when you turn on clip info?

[Sandeep Sajeev]

I can see this sucking. I get what Phillip meant now.

[Sandeep Sajeev]

But you can still have multiple favourite ranges per clip?

That was something I really liked, hope that hasn’t gone.

[Sandeep Sajeev]

Good to know.
Thanks Bob,

[Sandeep Sajeev]

Reading his post again he says

Over the last two months I’ve added keywords to “ranges” I didn’t intent to have because the In and Out were held from the last playback or edit I made. Not what I want. So I have to select the whole clips again, and reapply the Keyword. It gets old after the twentieth time.

So I think you’re right Walter.

Something else that strikes me from his post is that the Dual Viewer implementation doesn’t seem to show source time code in the viewer.

[Sandeep Sajeev]

Great to see native r3d support and dual viewers.
Not sure what the issue was with the old method of creating freeze frames.
Selective copy paste is great.

Looks like Roles hasn’t been expanded upon in this release.

Will have to wait for a couple of weeks to download this update, but it seems more hit than miss. Not sure what Hodgetts issue is with the PIOP’s, has something been lost re keywording or favourite tagging to make this happen?

[Sandeep Sajeev]

-You don’t need the green card.
-You might want to place tracking markers on the 4 corners of the screen if you’re doing a 4 point track. If you’re using Mocha they may not be necessary
-You should absolutely shoot the scene with the reflections and comp them back in once you’ve inserted your screenshot.
-Shoot a reference plate with a screenshot that’s similar to what you’ll end up comping in – this way you’ll know what your scene should look like if was done for real.

Best,
Sandeep