Activity › Forums › Apple Final Cut Pro Legacy › Downgrade 4.5 to 4.01?
-
Downgrade 4.5 to 4.01?
Posted by Kevin Morrison on April 27, 2005 at 3:18 pmI’ve been having weird problems where FCP 4.5 quits after every log-and-capture session. I’ve tried a zillion solutions — every version of the OS from 10.3.2 to 10.3.9 — reformatted drives — different drives — different RAM configs — and the only thing that works is this: FCP 4.01. If I install FCP 4.01 from my original disks and DON’T upgrade to 4.5, I have no problems.
However, I have a dozen projects in FCP 4.5 that I need to work with. Is it possible to save those projects as 4.01?
Kevin Morrison replied 21 years ago 4 Members · 8 Replies -
8 Replies
-
Jerry Hofmann
April 27, 2005 at 5:48 pmNot really… I’d get to the bottom of the crashing though, it’s not happening here anyway. Might post more about your setup… is it all DV or? capture card? how are you controlling the deck? what drives are in use as scratch disks and how are they formatted?
Jerry
Apple Certified Trainer
Author: “Jerry Hofmann on Final Cut Pro 4” Click here
Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D
-
Kevin Morrison
April 27, 2005 at 6:38 pmAh well. It was worth asking.
The specs on my system below, but first a quick word about this problem: I posted about it here and on 2pop last week and heard back from four other editors who had the same problem. They circumvent the problem (like I do) by saving everything after log-and-capture and then restarting the software after the (inevitable) crash.
My system: G4 with dual 1.2 GHZ, 1.5 GB memory. Boot drive is a Barracuda. Scratch drives are Lacie firewire external drives purchased within the past year. (I also have a second internal ATA drive which I tried as a scratch drive, thinking the firewire drives might be the problem. No dice.) Currently at OSX 10.3.8, although I’ve upgraded incrementally from 10.3.2, hoping to find a release that works.
I capture DVCAM from a Sony DSR11. I use the unaltered vanilla NTSC DV preset.
I keep hoping there is some thing — a firmware upgrade, a subsidiary chipset incompatibility — that can be identified and circumvented…
-
Kevin Morrison
April 27, 2005 at 6:40 pmIt might be worth mentioning that all the crashes are ‘thread 0’ and identify ‘kern protection failure’ as the culprit, followd by a long list of plugin and carbonlib blah-blahs. (I believe blah-blah is the correct technical term.)
-
Bryce Whiteside
April 27, 2005 at 10:14 pmI always understood the Sony DSR11 DVCAM and the firewire drives needed to be on seperate firewire channels requiring an additional firewire adapter since all the firewire ports on G4’s and the G5’s are the same channel no matter how many physical plugs are available.
Just thinking out loud,
BryceDon’t worry Mr. B. I have a cunning plan…
PowerBook 1.67 Ghz ATI 9700 128 MB 2 GB
Final Cut Pro HD
DVD Studio Pro 3
Motion -
Francois Stark
April 28, 2005 at 2:16 amYou say you tried different RAM configs. I hod lots of RMA-related problems on a G4 before. Have you tried with the base ram that came with the system alone?
I found that running with 512MB was often the most stable.
Kernel crashes are most likely caused by RAM, motherboard or CPU problems, especially if there are many other users out there with the same software/hardware combos without problems.
Regards
Francois -
Kevin Morrison
April 28, 2005 at 2:18 pmI tried taking the scratch drives off the firewire bus (by using a USB 2 capture card on the PCI bus) thus leaving only the DSR11 on the firewire bus. That didn’t work — same problem.
The RAM configs have been variable. The fact is, until about six months ago, the original 384 Megs worked fine. Then the log-and-capture problems started, so I upgraded RAM in various ways. No dice.
I lean toward the notion that this is a problem related to OSX or FCP software, especially the upgrade from 4.01 to 4.5, simply because 4.01 works and 4.5 doesn’t! That said, heck, I have no idea. I’m stumped.
-
Francois Stark
April 28, 2005 at 7:35 pmI disagree.
It must be a system-specific hardware problem, since there are so many users out there running FCP 4.5 on many versions of hardware and operating systems without getting your problem.
FCP 4.5 is triggering some hardware problem on your system that 4.1 is not triggering.
Have you tried a different DV deck?
Regards
Francois -
Kevin Morrison
April 28, 2005 at 9:52 pmCertainly it could be a hardware problem. Indeed, that was my first instinct, and that’s why I’ve tried so many different hardware fixes. And it’s a good idea to try a different deck — that’s one I haven’t thought of! I’ll give it a go with a different deck tonight.
I wonder about the notion of upgrading to 10.4 and FCP Studio and seeing if THAT will fix it. If it weren’t for the necessary $$$, I’d try that tonight, too…
Reply to this Discussion! Login or Sign Up