Export problems in FCP HD

[David Bogie]

Kernel panics are not minor glitches and they’re not random. They indicate serious weirdness with a file structure or with hardware. Debugging them is nearly impossible but you can start by trying to isolate the problem segment of your total sequence and seeing if that causes the crashes.

Read back over your post, too, a couple contradictory statements.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[Kennon Shain]

Thanks for the reply Bogiesan,

Yeah, I’ve only experienced kernal warnings maybe 2 or 3 times before. But when I say “random,” I mean that the system crashes at DIFFERENT times in the export process each time I do it. It doesn’t always crash at the same point.

So, given the fact that its at random times in the export process, I just have a gut feeling that it is something thats interrupting the process. For instance, I have a program called “Little Snitch,” which tells me each time a program tries to connect to the internet (for updating, etc.).

Most programs are either denied or accepted access automatically because I set it, but it could be a new program or utility that is causing a pop-up window as the export process is going on. I know that exporting and rendering usually takes a lot of CPU power, and interruptions can be bad.

Anyway, I was just curious if this meant something to someone, who possibly might have gone through the same thing. I just trashed the prefs, and set “Little Snitch” to not interrupt on a couple new programs, so I’m hoping that will solve it.

Thanks-

Ken

PowerMac G4 (Quicksilver)
Dual 1 GHZ
1.5 gig RAM
OSX 10.3.5
Final Cut HD

[David Bogie]

I doubt Snitch could bring down your system but unplug your network connection and disable everything that isn’t associated with the project.

If the kernel panic crashes continue, start with permission repairs. You can also harmelssy reset the PMU switch (I don’t think this helps at the kernel level but it doesn’t hurt anything) Then start non-destructive system testing and disk repair from your OS install disks. You also should have received a hardware diagnostics disk with your Mac. Run it.

Wish I had better news or more to offer. The good news is that the possibilities are binary, black and white: It’s either something pesky and harmless that is easily fixed or it’s seriously weird, beyond your imagination, and you need a new motherboard.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[Kennon Shain]

Thanks Bogiesan.

I tried to run the TechTools (3.0.2) diagnostic I received when I got the Apple protection plan, but it crashed twice! And to think of it, I had tried to degrag my main drive (iDefrag 1.0.5), and it had crashed then too. I think my main drive is pretty scattered, but if I can’t get the diagnostic or defrag to work, how do I fix it? Also-I’m trying to export the MPEG-2 to my external firewire drive, NOT my main drive. SO would the main drive affect it, or would the drive that the file is being exported to affect it?

Also-I am going to finish editing my other wedding, and export that. That will prove whether its just the particular wedding I’ve been trying to export, or whether its something else. Fingers crossed….

It probably isn’t Little Snitch-but Snitch had actually crashed my computer a couple times-once when I was transferring music to my iPod, and once when I was rendering something. But it shouldn’t be popping up at all anymore, so that shouldn’t be a problem.

Anyway, are there better diagnostics I should try to get? I mean, if a system doesn’t like to be diagnosed, will it do the same thing to any diagnostic software?

Thanks-

Ken

PowerMac G4 (Quicksilver)
Dual 1 GHZ
1.5 gig RAM
OSX 10.3.5
Final Cut HD

[Kennon Shain]

Also- I’ve been noticing more dropped frames in playback. Could this possibly be related?

Ken

PowerMac G4 (Quicksilver)
Dual 1 GHZ
1.5 gig RAM
OSX 10.3.5
Final Cut HD

[Kennon Shain]

I ran the hardware diagnostic I received with the computer, and the hardware passed fine. So it must be a software problem, and more specifically, a volume structure problem. The Tech Tools program I ran crashed at the “Volume structure analyzing” step both times.

So I ask again-how do you defrag and analyze a drive that doesn’t want to be touched? How is the drive making the diagnostic programs crash?

Thanks again for any help-

Ken

PowerMac G4 (Quicksilver)
Dual 1 GHZ
1.5 gig RAM
OSX 10.3.5
Final Cut HD