Tom Wolsky
Forum Replies Created
-
I take it all back. I was wrong about my first comments. I’m sure I saw that in an earlier version, but I’m not getting that in 5.0.2.
-
Tom Wolsky
July 20, 2005 at 9:34 pm in reply to: Can someone explain the 960×720 DVCPRO HD thing to me?It’s a kludge that Panasonic built into their cameras to reduce the bandwidth. It’s not anamorphic in the strict sense because the material is not being squeezed. Panasonic has some euphemism for it, but basically it doesn’t effect the output in anyway. When you record back to DVCPRO HD the material is processed down to this size for recording.
-
Tom Wolsky
July 20, 2005 at 9:29 pm in reply to: 1. My report on manglement in fcp4.5 versus fcp5 and 2. ….help!That seems to be the case for anything it sees as variable speed change. It shouldn’t do it for a constant speed change, but if a clip uses time remapping just to make a freeze frame or a constant slomo, it’ll be treated the same way.
Material brought from sequences created in earlier versions may not MM properly. I never had a chance to try that enough. The wrong section of material for speed changes is a common problem with material that’s captured in lengths of more than 10-15 minutes. It still may be a problem with some material in v5.
-
Tom Wolsky
July 20, 2005 at 6:10 pm in reply to: 1. My report on manglement in fcp4.5 versus fcp5 and 2. ….help!Time remapping requires you to capture all the material for that piece of media. The way time remapping works is you select a frame number and position it at different frame number in the clip. Because this is based on the whole piece of media you can’t change the number of frames in the media or the time remap will kludge. That’s why you’re getting so little file size reduction when you MM. This was changed in v5 because speed was such a mess in media manager in earlier versions. It’s not a great solution, but it’s the only one they’ve come up with.
-
Tom Wolsky
July 20, 2005 at 5:23 pm in reply to: 1. My report on manglement in fcp4.5 versus fcp5 and 2. ….help!Can’t help you I’m afraid. Can’t see why it doesn’t work on your machine and does work on mine. Maybe something about the way the material’s captured, but I can’t think what. Mine’s captured in long blocks and it works as it should, at least as far as consolidating and deleting unused goes.
-
Tom Wolsky
July 20, 2005 at 12:04 pm in reply to: 1. My report on manglement in fcp4.5 versus fcp5 and 2. ….help!Just tested it again. Didn’t need to make clips independent. This may have changed in 5 or 5.0.2. Thirty second commercial with a copy function cut down to 3.5G from 12.6G.
-
Tom Wolsky
July 20, 2005 at 11:43 am in reply to: 1. My report on manglement in fcp4.5 versus fcp5 and 2. ….help!Did you use “Make sequence clips independent”? Uncheck other affiliate clips or whatever it says down there?
-
Did you scale, rotate, reposition the image in any way? It’s always best to do garbage mattes to image at full size and resolution before applying motion effects. The garbage point mattes are based on the image in relation to the canvas and have no bearing on its current position, size or orientation.
-
That’s more helpful. There have been issues with media manager and multiclips. Did you collapse the multiclip? I think 5.0.2 addressed some of that.
-
I can’t help. I’ve not seen that.