David Heidelberger
Forum Replies Created
-
This was a bug that was fixed in 6.0.2 (thanks for pointing this out JeremyG). If you’re running an earlier version, see this post for how to fix: https://forums.creativecow.net/readpost/8/963808 . You can just conform it to 23.98 using Cinema Tools. If you’re running 6.0.2, that’s probably a problem, but you can try this fix anyway.
– David
-
Weird. What a strange thing. And it also solved the DVCPROHD exports needing to render bug before, as you so rightly pointed out, 6.0.2 took care of it. Cinema Tools conform seems to be worth a shot for almost any Quicktime problem.
-
I’ve had the same problem on every DVCPROHD 720p project I’ve worked on for quite a while, using the FCP Text tool. I was beginning to think it was just me! Interestingly, it doesn’t seem to do this if I compress to MPEG-2 for DVD, but Sorenson, H.264, etc, no matter what the dimensions, yes. It also does this to other generators, like shapes.
The only reliable workaround that I know of seems to be to export a reference movie from FCP and bring that into compressor. Usually, this is fine, but sometimes it’s a less than ideal workflow.
– David
-
Thanks for the suggestions. I set Samples Per Frame as high as it would go to 64 and Adaptive Sample Limit to its max, 128. No change.
Unchecking Collapse Transformations does introduce the proper motion blur, but obviously loses the benefits of vector-based scalability.
Finally, I think I may have found a solution, although I don’t know why it works, and I’m not sure if it would have an adverse effect on certain projects. I set all my layers in my precomp to 3D layers and that made the motion blur work properly. I’m not sure what, if any, problems this could cause in a project where the nested comp is placed in a 3D environment, but at least for 2D projects, this is a workaround.
Is anyone else able to duplicate this problem or does it work fine for you?
– David
-
I don’t think there’s a single cause for the problem. That may be one cause, but there are others as well. I was able to narrow it down in one of my timelines to one clip that didn’t need rendering in the middle of multiclips with effects on them. Export only frames within the normal clip, or only frames in the multiclip and it was fine. As soon as I exported anything with both of these clips, I got the bug.
– David
-
Thank goodness. Looking forward to updating in a week or two when this project is done.
– David
-
Hi Charlie,
Sorry to come late to the party on this one. I got the same stuttering that you seemed to be having. Then I opened it up in Cinema Tools and conformed it to 23.98. It briefly flashed offline in FCP and then reconnected and now it renders fine. I’ve sometimes seen Quicktime movies improperly tag their internal timebase, particularly when they render out of a third-party app. I think this is the problem that you’re having. For example, I’ve done a little bit of Javascript programming for Quicktime and if I render a 24p file, it sometimes tells me that the timebase is 29.97 (even if Quicktime’s “get info” tells me that the frame rate is 23.98). This is speculation, but I think conforming it to 23.98 in Cinema Tools, in a case like that, basically just resets the tag inside the file so that everything is on the same page.
Hope that helps,
– David -
Are you talking about just Mini-DV stuff? Or the HD as well?
For SD Mini-DV firewire, I wouldn’t recommend using a Canon camera. Don’t know if it’s a universal problem with Canons, but the three that I’ve captured with in the past (XL-1, XL-2, and a ZR-60, I believe) hog your firewire bus so that you can’t capture to a firewire drive unless you buy a firewire PCI card to get a second bus. I believe that other brands won’t give you this problem.
If you’re talking about HD from the H1, I’m not going to be able to help you.
– David
-
When I have this problem (usually doing AE re-renders of a graphic and it tells me the file is in use), I delete it in the Finder. If I try to empty the trash, it won’t let me because the file is in use, but if it’s in the trash, I can save a new file with the same name to where it was and reconnect in Final Cut. Then, once the new file is reconnected, I can empty the trash.
– David
-
Happened to me for the first time the other day and I was able to narrow it down to one DVPRO-HD non-multiclip clip that didn’t have any effects or anything on it in a multiclip timeline. The weird thing was, if I exported just that clip alone, it was fine. As soon as I exported one more frame on either side of it, I got the red-bar etc.
As I mentioned in an earlier post, I may have a workaround that doesn’t (I don’t think) involve recompress. I didn’t notice a quality loss, but compression experts might be able to tell further. Export the whole timeline as normal, then open the new Quicktime movie in Final Cut and export that clip to a Quicktime movie. The second Quicktime movie opened fine, fit in my timeline, and, as I said, I couldn’t see any difference between the first and second.
– David