[David Bogie]

it’s what I’m running on my non-dual core G5s.

bogiesan

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

[David Bogie]

> Don’t you mean, regenerate it? If so, then I recompress and lose quality. This is not uncompressed footage. ALso exporting will take a long time. I will consider your solution, but regenerating clips doesn’t seem too efficient. < No, I don't mean regenerate it although, where you come from, that's what the concept might be called I said export. That's a cloned copy, there is absolutely no reduction in quality. If you change the settings, yes, you will create something new but it would be rendered, not regenerated. Efficiency is relative, you don't have your audio clips, that seems terribly inefficient. Exporting, reimporting and relinking eliminates all that. Setting up your original capture to separate audio from video and capture to separate drives or folders was a common practice with many NLEs back when FCP3 shipped but it was never a good idea with FCP3. bogiesan This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Try puling each one of your clips into an empty sequence and exporting it. Reimport it.

sorry, haven’t used FCP3 for years.

bogiesan

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

[David Bogie]

Certainly the Kona manual came with instructions on how to set up your projects?
There’s a Kona Web site and there’s a Kona forum here on the cow, I think.

bogiesan

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

[David Bogie]

You cna waste a lot of time doing this so make a quick phone call and ask what codec, what bitrate, what file size, what frame size. Try to get answers to at least two of those.

If you’re lucky, the response will not be, “Huh?”

bogiesan

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

[David Bogie]

> It’s a software RAID … done with Apple Disk Utility and I already know the risks. There was nothing on the RAID that couldn’t be reproduced …. luckily. The issue is Disk Utility won’t let me unmount/delete the raid. If I can do that, I can at least get use of the drive that’s working albeit not a RAID set.< Cool, like I said, try not to take it personally. RAID is a terribly misunderstood storage media around here. Since you have accepted the doom scenario, shut down, disconnect the drives, restart. Repair permissions (this seems to ease minds, dunno if it does anythign in this case). Shutdown. reconnect the bad drive. Restart and see if it mounts or if Disk Utility will see it. Do you have any other drive utilities at your disposal? Try them too. If it won't mount there's nothing you can do about it. Go buy another drive and restrip them. If it will mount and you have time, run every possible test and repair you can on it. Especially look for the SMART rating for the drive. Or you can hook the drive up to another Macintosh and run the utilities on it while you get back to work. bogiesan This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

I have no idea what your machine looks like or what it can do but if the camera and lens still work and you have FW or composite out, keep it! Put it on a tripod and use an external deck. You have now become a facility that can do multicamera shoots.

Or get your buddies together with some nice wine and tiny tools and take it apart.

bogiesan

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

[David Bogie]

Call the RAID mfr immediately. You want to know what they suggest for remounting the errant drive. If you’re using software RAID, you’re pretty much toast.. Gather your production crew and begin discussions on how to implement your Worst Case Scenario Plan because it’s happened.

Here’s the problem: Your directory is striped across the RAID just like your data. If one of the drives has failed (or the data has otherwise been corrupted) half of your data is simply gone. There is no way to rebuild the system without a complete backup.

I’m not trying to pick on you personally but most RAID users who post here with their troubles have failed horribly to completely understand the risk tradeoffs of striped data and they are at a complete loss when something goes wrong.

I hope you can restore your drives with a few phone calls. Please keep us posted if you can and let us know what you did and whose RAID tools you are using. Your candor will help those who come after.

bogiesan

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

[David Bogie]

The advice to scan at 72dpi is unnecessary and the concept is usually misunderstood.

There is no dpi in video, there are only pixels. You r video image is about 800×500 pixels depending on your video format. That has nothing to do with resolution or dpi. If you scan your image to be 800×500 pixels, it will fill the screen. If you scan your image to be 1600×1000 pixels, you will need to scale it by 25% to fit it into the screen but you would be able to zoom into the image or pan across it. If you scan your image to create a file that is 400×250 pixels, you will blow each of the pixels up to fit the screen and things will look awful. Scanning to produce an image that is much larger than 4 times your screen size is generally a complete waste of resources.

bogiesan

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

[David Bogie]

You will need to precompose the V2 layer.

bogiesan

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