Finding clip in bin

[Edit Bay rat]

Well…you don’t. At least not as far as I know. It’s one of the great mysterys of life that you can drag a precompute into the source monitor from a bin but can’t source it back from the timeline.

If you just need to cut the key into another spot on the timeline and don’t want to spend the time searching for the original, mark it in the sequence and sub it out to a bin. The sub-sequence will function the same as the original clip.

If you actually need to find the original, put on your hip waders or hope that somebody here knows something that I don’t (I’ll be watching and hoping).

This is why each of my projects gets a dedicated “titles and fx” bin out of the box.

The Rat

[Michael Thomson]

Aaargghhh !!!

Isn’t it bad when you can’t remember something.

Apparently the AVID can interpret the pre-computes the same way as footage, natively but the kind people at AVID disabled it for some reason.

So you can load then to the monitor.

The way to enable it is through console. I can’t remember the command, but i know that it isn’t listed in the help list.

I was told about it by an AVID trainer, but unfortunetly i cannot remember…

Anyone else heard of this?

[Philip Boal]

If you’ve already made an edit with this particular matte key, you can just scroll to it on your timeline and then double click on it to load it up into the effects editor. from there you can make a copy of it, drag it to a bin, whatever you need to do.

If you haven’t already edited with it. Open up the Media Tool, turn on all of the choices and you should see all of your matte keys lumped together and you can find it quickly. (it helps to add labels to the mattes)

hope this helps.

[Edit Bay rat]

And there you have it…sometimes hoping and watching pays off.

A trip to the L tells me that the console command that allows precomputes to be loaded into the source monitor is as follows:

subsys monpane debug

I’ve tried it and it works perfectly. To turn it off, restart the application.

As usual, caution is advised when working in the console; you can do a lot of damage if you’re not careful.

The Rat

[Michael Thomson]

Well done RAT,

I thought i was going insane for a moment.

CHUMP

[Jason Brown]

Kudos…very well done Rat.

I appreciated all the info about workarounds to this, I always thought that when I copied a file to the source monitor, that it created some new media files (I am still fairly aloof to the way avid handles files).

I’ll take the question one step forward. Another reason I wanted to do this was because when I delete media and clean off the drives, I see a bunch of very non-specific pre-comps named the same as the project and have no way to tell what they are. How does everyone else deal with deleting pre-comps — Do a media relative to the sequences and if it’s not related to any of those delete it?

-Jason

[Michael Thomson]

Jason

Yes pretty much. I will open the media tool, do a select media relatives on the sequence, reverse selection and delete.

Another little nugget in the console is renaming the files on the media drives.

Type the command “renamemediafiles” and all the files in the media drives will reference the names given in the bin.

Cheers

[Mike G.]

Great thread, and great solution Rat! OK, I want to make sure I have this straight: if I access Console, and type in “subsys monpane debug”, then I’ll have the ability to match-frame Matte Keys?
[I’m always a little nervous doing anything in Console, so I want to make sure I’m not screwing myself if I try this.]

Furthermore, Rat wrote “To turn it off, restart the application.” I take this to mean that my ability to match-frame Matte Keys is de-activated every time I restart the application. Is there a way to permanently enable this option in my User Settings?

[Edit Bay rat]

Not only will you be able to match frame, you will be able to double-click or drag and drop normally unloadabe precomps from a bin.

As far as I know, this function is reset everytime you restart the application and there is no way to make it permanent, however (as this thread has clearly established) I don’t know everything.

You are wise to be nervous about working in the console and we should all be cautious about using this function. There was a warning with the post on the L that it might cause some problems with batch capture or decompose if you’re working at a low resolution and planning to up-rez, so if that’s how you’re working you might want to run a test. There’s probably a reason Avid has left this function off for all this time. I’d hate to have someone cut a huge project and discover the reason why at the very end.

Proceed with caution, but by all means, proceed.

The Rat