Kevin Morrison
Forum Replies Created
-
Certainly 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…
-
I 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.
-
It 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.)
-
Ah 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…
-
FWIW, I called one of my colleagues who was on the floor at NAB and he went over to the Medea booth to ask them about 10.3.9 incompatibility. They basically said, Yep, we’re working on that. So it’s back to 10.3.8 for me!
-
I have FCP 4.5 running under 10.3.9, but I’ve lost access to my Medea RAID. I think I’ll be doing the OS reinstall shortly…
-
I’m still not back at the computer, but now I see what you’re getting at!
If memory serves, I have two ATI/Rage 128 cards that date back to mid-2000. I wonder if I need to upgrade the drivers? Hmm…
-
yeah, that’s darn good advice. now, do me a favor. get in that de lorean and drive back a few hours ago and email me…
; >
-
ah, yes, the beautiful world of computers. never assume!
okay, i see what you’re saying. i’m not at that computer right now or i’d report on what’w what in its video world, but i wonder if one other item i omitted might be relevant. in one of my many fcp reinstalls i did to try to fix this problem, i paused in 4.01 for a few minutes to see if the computer would have the same problem. it didn’t. however, it’s not really an option for me to stay in 4.01, as i have several large projects going in 4.5.
anyway, in my mind, the problem is software-related, and the problem is in between 4.01 and 4.5. maybe. (never assume!)
-
I have a video card installed, but the log-and-capture problem persists whether I use the card (which I don’t usually use) or the built-in G4 FireWire ports! So, yeah, good idea to check card I/O problems, but it’s probably not the culprit in this case. But thanks for trying!