-
New MacBook Pro and Final Cut 2 (sucks?)
-
-
Ha ha ha. That was cheery. Yep, I love this little ol’ town.
Yes, my experience was with the MBP. I just blundered in with Qmaster, set it to two instances (duh) and tried it. The batch basically appeared to hang. Turned of sharing and it was fine. It seems to support your post quite well.Thanks!!!
Final Cut Pro 6.0.4, Mac OS-X 10.5.5, Quicktime 7.5, Adobe Prod Prem CS3, G5 Quad 2.5, Kona-LHe V6, 8.5GB RAM, Nvidia GeForce 7800-GT 256MB, G-RAID 2x1TB FW800, 6TB RAID-5 (Enhance E8-ML, Highpoint 2322), Panasonic HVX-200P P2. Also MBP 17″ Core 2 Duo 2.5, 4GB, GeForce 8600M GT 512MB.
-
Yep I have repaied directories and everything. It still gave me the extended time.
Are there amy other new MBP users out thereexperiencing this phenomenon? -
[Justin McClusky] “Yep I have repaied directories and everything. It still gave me the extended time.
Are there amy other new MBP users out thereexperiencing this phenomenon?”Have you tried this with regular video instead of mp4 960×540? Have you tried using another piece of software such as MPEG streamclip for this?
Jeremy
-
I really think it’s a codec issue. Meaning that you have a pretty non-standard timeline there. Let me make sure I understand…your sequence is set to 960×544, h.264, aac audio? If so, it’s a complete crap shoot as to how FCP will handle it. You should get it into a standard editing format first, then cut in FCP.
-
Yeah that sounds about right.
In the end I managed to reformat the out-of-the-box MBP and reinstall just FC. I’m really not sure what was wrong, but now it seems to work just fine. The export to a standard DV format took only 2 to 3 hours.
I really appreciate all the help from everyone!
Now to finagle Qmaster into working properly…
-
I’ve had similar problems with Compressor with my older MBP. Did anyone mention to trash prefs?
Reply to this Discussion! Login or Sign Up