Greg Nosaty
Forum Replies Created
-
[morgster] “my Kona card was working fine before when I had it in slot 4… and had no sonnet card.”
I would put the Kona back were it was and find a new slot for the eSATA card. I’m running a KONA 3 with 2 Sonnet 5 bay eSATA raids and have no sync problems with FCS2.
-
I can’t tell you why it happened but I think I can help you restore your project. Open FCP and go to the File menu, select restore project and select the last Autosave of the project.
You could have some bad media or you may just be experiencing the same, unexplained “out of memory error” that many of us get regularly. What version of FCP? what computer and drives are you using? What kind of media are you editing? Maybe its just the full moon!
-
[Russell Lasson] “What kind of RAM do you have in your machine?
Your machine seems abnomally unreliable. It quite possiblely be mid grade RAM that’s causing your issues. What brand is it and where did you get it?”
It happens with all the desktop systems I work on, each with different amounts and brands of memory installed by the Apple reseller.
-
[crane.director] “Using the log and transfer with P2. Everything is fine until I “add clip to queue”. It goes into the queue ok but just sits there and doesn’t ingest to the bin in the browser. Help.”
Right click on the bin icon in the browser and select “set logging bin”
If you have added the clip to queue several times you should check your capture scratch disk to make sure you haven’t ingested the clips multiple time to your hard drive.
-
I also experience FCP crashes when working in high res. My workaround is to restart the computer and software once or twice a day. The best I can figure is that it is some kind of cache problem. If i’m working with thumnail views in my browser and doing alot of test renders it seems as if the cache gets overloaded. Then the system starts to become sluggish and you can almost see the crash coming. Thats when I know its time to save and reboot.
I’ll have to try my MacBook Pros as render stations, thanks for the tip.
BTW- all my drives are eSATA, Sonnet 5 bay mostly and they make a groovy 34mm PCI slot adapter so you can use the raids on your MacBook Pro.
cheers,
greg -
I useually render in segments as I color grade and add effects to test how things look. And your right, i helps you find corrupt media or effect files. But once I’ve completed the online I like to trash the huge amount of segmented render files and do clean pass for output.
cheers,
greg -
Everything related to each of my projects is stored on it own 2TB raid, media and render files. I’ve been running FCS2 for a couple weeks now with no NEW issues, only the same OLD ones.
I also trashed the prefs last week but it made no difference.
cheers,
greg -
How would you like me to serve my renders… rare, medium, with garlic butter?
The reason I’m re-rendering is because I have trashed the old renders and want to have a clean pass for output. The shows are 45 – 52 minute broadcast docs with lots of color correction and effects filters. They can take more than 3 or 4 hours to render in standard def, I don’t even want to talk about HD!
cheers,
greg -
I’ve deleted my preferences and it doesn’t help. its also a pain because it resets a bunch of other setting, like effects “favorites” etc.
I know several other FCP users here that experience the same problem.
cheers,
greg -
Wait a minute… removing the pulldown ith P2 import won’t help. That will take the 59.94 media and turn it into 23.98 but what I want is to end up with 29.97! I need to convert 59.94 to 29.97, 60 frames to 60 fields per second, it sounds so simple. I still think my best bet is to output to tape and re-capture via my Kona 3.
cheers,
greg