-
render files problem when going to/from MacBook Pro…
Hi all,
now we have had two projects moving media and or projects to /from MacBook Pro which ended up in problems with rendered files. First project we used two systems to speed up capture. Other puter was an old G4 Powerbook with FCP 4.5. We captured on both MB Pro and Powerbook to save time. Everything worked just fine untill we should render the piece to a selfcontained QT file that was supposed to be showed the same evening from a videoprojector. Some rendered files (clips) played arrounf half, then repeated from start for he rest of the duration. Trying to remove the crossdissolve and re-render just move the problem. Solution where to pull down opacity to 20% (ot whatever), render, move opacity back to 100% and render (to get the puter to render the whole clip). We tryed the usuall trashing prefs, repair permissions and so on. Only the opacity “trick” solved it.
The clips that was captured on the G4 Powerbook was on a firewire drive. The clips captured on the MacBook was on the internal drive. All files DV PAL. All editing was done on MB Pro.Second time we had a project on a G5 (FCP Universal), moved the project and the mediafiles to a FW drive. Did some stuff on the MacBookPro. Got the same problems. Moved back to the G5 and problems seems to have followed (?!?). Only way we found to solve this was to do the opacity “trick” with loads of re-renders….
This project had both DV and some 8-bit uncompressed PAL formats.Anyone alse with similar problems?
P.S. I hate when my “track-pad-mouse” on the MacBook freezes for a second or two….happens 20 times per day.
/Rob
-
2 Replies
-
I may be wrong about this answer, but I believe the way render files work,
you can’t move them around like you are doing. Nobody I know does this.
When FCP makes a render file, it’s referencing to the original media
in the timeline and that media is in a certain place on a certain drive.
It then makes the render file and puts that file someplace else.
Now there is still a reference being made by FCP in the file itself,
that tells FCP that those two files need to be in exactly the same place
as they were when you rendered. Like I said I may be wrong,
but I never put render files on my firewire drive when I move project
files around. I just re render whatever timeline I’m working on
once everything is moved to the Powerbook or the G5.As for your opacity trick, don’t do that. Just trash all render files that
deal with that project. Then render the timeline again.
This, by the way, can solve many problems with FCP playback,
I’ve found over the years.Dan
-
when we move projects we always do that, put renderfiles on same drive as original files.
Never had a problem before. Only with intel MacBook Pro.
As to our solution of using opacity trick, we did it since a trash of render files would
have made the render time much longer, this way we only had to render the places where
we did changes./Rob
Reply to this Discussion! Login or Sign Up