Michael Garber
Forum Replies Created
-
I have been experiencing a similar bug whereby I cannot modify any clip in the info tab when I select it in the library. Is this the same thing you’re experiencing?
Or are you unable to see the properties of the multicam clip when inside the compound clip?The issue I am experiencing occurs when I’m using two displays. My workaround is to set the view back to single screen and then change it back. Then all the properties show up and I can change them in the infopane again.
Michael Garber
5th Wall – a post production company -
The Mystery of the Misplaced R. We could write an Encyclopedia Brown book based on this 😛
What was interesting about this scenario is that it was only the multicam that wouldn’t relink before I jogged it. There were other HD clips that relinked fine.
Michael Garber
5th Wall – a post production company -
-
I think I fixed it. Even though the project showed up that it was referencing the correct event, I went in to modify event references, anyway, and clicked on the correct event, again (it was the only event active and available to choose).
Even though I modified the event references when I duplicated the event, since I didn’t turn off the original drives after duplicating, X must’ve somehow kept it’s reference to those drives active in some way, even though it said it was referring to the new duplicated event. Either that, or there was some other bug relating to this R3 & R7 issue in the XML, as it was referencing the correct event.
Anyway, just good to know that I was able to reconnect properly and work without too much down time. Phew.
Michael Garber
5th Wall – a post production company -
Hi Jeremy,
Sorry, by that I meant that the original drives that I cut the project on still exist. I have a duplicated version of both the event library and the projects. I used FCPX to duplicate it. However, I did not unmount the original drives to test everything 2 weeks ago.
I made some headway. I exported an FCPXML and used Textedit to change this line:
media id=”r4″ name=”Annual Meeting” uid=”CWMAixgTS2+KyQYepBeSpw” projectRef=”r3″/
to
media id=”r4″ name=”Annual Meeting” uid=”CWMAixgTS2+KyQYepBeSpw” projectRef=”r7″/I noticed that all the other media that was linking properly was set to “r7”. So I just changed that and it relinked pretty quick. That said, it came from an XML, so I’m not sure if everything translated properly. I did this via remote desktop and will be able to check it out in an hour or so.
Michael Garber
5th Wall – a post production company -
Thinking about this some more. I think with a faster system that can handle the effects in RT, then yes, this is a good thing. But what if you need to render something globally (in my case a simple broadcast safe) and you just want to play the timeline down without stuttering at full-res? In my case, I need to make sure all the interlacing is correct. I don’t want to have to export for 10 minutes. re-import. Find an error. Re-export, etc…
Anyway, this wasn’t meant to sound like an argument against your excellent advice. Just thinking out loud about why rendering is still good in a lot of cases.
Michael Garber
5th Wall – a post production company -
Ah, great to know. Different way of thinking about it. Thanks for that.
Michael Garber
5th Wall – a post production company -
I get about 8-9 minute export time. What about your render time? My tests were on render times in the timeline.
Michael Garber
5th Wall – a post production company -
Hey Oliver,
Funny, I did a similar test before reading your post just yesterday. I had a whopping 2 hr render with basic color correction and broadcast safe on 10 minutes of XDCAM footage. I compared render times between FCPX, 7, and Premiere CS6 on the same system.
Clip was a single 10-minute XDCAM EX 1920x1080i 29.97 clip.
In FCP7 and Premiere, I added a Broadcast Safe and Three-Way Color Correction (with a minor correction attached) filters. Here are my findings:
FCPX: 2 hrs
FCP7: 10 minutes (set timeline to render to Prores)
FCP7: 30 minutes (set timeline to render to XDCam)
Premiere: 20 minutes (set to render to I-Frame MPEG)
Premiere: 25 minutes (set to render to Prores)
Premiere: 25 minutes (set to render to XDCAM)My system specs:
Mac Pro 3,1
16GB RAM
Radeon 5870
RocketRaid eSATA card
LaCie eSATA drive
Kona 3
Lion 10.7.4Michael Garber
5th Wall – a post production company -
Hey Andy,
I thought about doing it this way, but there are two problems. First is your new compound clip is set to your timeline dimensions, not the original image dimensions. Second, you lose the ability to slip and extend handles. You’d have to go into the compound clip to change the duration. If you have dissolves already set, this could throw your timeline off.
I think, given this scenario, your better bet is to open the still image in it’s own timeline (from the primary timeline), first. Change the crop. Then go back and apply the Ken Burns.
I wonder how Ken Burns, the person, feels about being applied to all our movies without even being asked properly. 😉 Maybe he could make a documentary about it.
Michael Garber
5th Wall – a post production company