[Roman Hankewycz]

First, load the clip you’ve worked on into the viewer and go to the filters tab so you see the stack of effects you created. Then create a bin in your browser and name it appropriately (“filters for stills” for example). Now go to the filters tab in the viewer and select all of the effects and drag them into your newly created bin in the browser. You’ll see that the filters are placed into the bin. These filters retain the settings you’ve set and they can be applied to any clip in a sequence by simply drag-and-dropping the bin (filters for stills) onto the clip.
Note. If the order of filters is important (and it always is) then you’ll have to force the filters in the bin into the appropriate order by renaming them; i usually give each filter a numerical prefix (01_Color Corrector, 02_RGB Limit, etc). This way when you drop the bin onto a clip, the filters are applied in the right order.
Hope this helps
Roman

[Roman Hankewycz]

So I have made some progress in figuring out this issue. The double capture is a direct result of modifying clip properties. In preparing my online sequence I used the media manager to create an offline sequence at the correct resolution. Then, because I’m only dealing with video, I modified all the clips in the browser to only contain video. I did this by highlighting the clips, then choosing “Clip Settings” from the “Modify” menu and un-checking the audio check box. The unexpected result of this action is that FCP for some reason starts looking for two media sources for the single clip. If you try to reconnect a single clip you’ll see it’s looking for 2 files; or if you try to digitize a single clip you’ll see it captures the footage twice.
Now I know what’s happening, I’m wondering if anyone knows why or how to work around it.
Thanks,
Roman

[Roman Hankewycz]

Good point although a little presumptuous. My scopes are hooked up to a down-converted SD SDI signal from my Kona3, and my Kona is configured to build in the 7.5 setup on down-convert. So when I say 7.5 ire on the scope, that is the same as saying 0 inside FCP. It’s true that this isn’t the ideal monitoring set up but it does for now.
But your comment brings up a more interesting point. If 0 in FCP is displayed as 7.5 on my scopes, and I was seeing levels of 0 on my scopes, then doesn’t that mean that my clips inside FCP had levels below the digital 0 mark? Is that possible?
Not to mention the most important question of all: Why was back info clipped from my rendered video?
Again I will give an example. If I played one of my clips with no filters put on, I would see the black limit of the video signal reach 0 ire on my external scopes. However, if I applied any filter to the clip, even without adjusting any of the filter’s settings so as not to effect the footage, after rendering everything under 7.5 ire on my external scopes would be clipped. Why?
Roman

[Roman Hankewycz]

Hey John,
the error message i got was “An ACCESS_VIOLATION exception occured…” then it goes on to say where to find the log entry for the error. What you say about not being able to import OMFs into AVID confuses me because AVID uses OMF media files and I’m sure that in the past i’ve been able to swap audio OMFs between Meridian systems. I guess what you’re saying is that it’s not my OMF that’s at fault but it’s that I have no program that can read it. So I’d appreciate any knowlege you can pass on to me.
Thanks