Michael Alberts
Forum Replies Created
-
Thats funny, I just had this problem for the first time last night. The solution was to create a new sequence and paste the old sequence clips into the new sequence. From then on all clips in the Viewer showed their proper track assignments.
I’ve been working on FCP since v1 and this was the first time I had seen this pop up. What a coincidence.Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
I can’t speak to the Blackmagic issue as we use the Kona 3 cards, but are you sure the tape was shot at 24 and not 23.98 It’s rare that someone would chose to shoot at 24 without a very specific reason. 23.98 is much more common. You may be dropping frames due to the computer trying to calculated a 24 frame speed from 23.98 material. Just a thought.
We capture DVCPro HD from HDCAM to a GRAID all the time. No need for fast drives in that scenario.Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
You can’t go wrong with the 8bit uncompressed. You’ll have much less render time with the uncompressed coded as opposed to the ProRes codec which is a render hog. Even with our octo core MacPro with 8GB of RAM something like a simple color correction requires a render before outputting in ProRes.
Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
[George Bazhenov] ”
Not sure bumping RAM will help because FCP cannot use more than 4 GB of it. It may help in separate cases when you have other RAM-hungry applications open though. “Who doesn’t work with multiple apps at the same time? If FCP is allocated 4GB that leaves enough RAM for programs such as Motion, After Effects, Soundtrack, Color, Compressor, Transmit, Episode etc which we routinely have running all at the same time. Not to mention your web browser and email.
We also routinely have multiple HD projects open at the same time. This eats up RAM like crazy. Without a minimum of 4 just for FCP we routinely get crashes.
Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
We’re using both the FXFactory and BCC 5 FX Plugs. I like them both, but have to give an edge to the BCC pack. It costs a bit more, but you get quite a bit more also. Both are excelent.
Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
Has anyone out there in Cow land been able to capture HD-SDI using RS-422 from the Sony HVR-1500. All our attempts have failed. Our Kona3 FCP system can capture fine from the HD-SDI, however every shot captures the wrong in/out points. This leads to clips not being able to reconnect in the timeline when doing an online.
It would appear that Sony’s high-end HDV deck and FCP’s RS-422 handling don’t play well together. Has anyone out there gotten it to work? We certainly haven’t in any of our three rooms.Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
RIP Aurora. We still thing the Pipe Studio was the best SD card/BOB on the market. It had a few bells and whistles that the Kona series never will. Alas, we’ve had to upgrade all our systems to Kona 3’s over the past year to handle all the HD work we do know.
The guys at Aurora have all moved on to other things. It was too bad they didn’t get enough support from Apple. They were great engineers and code writers, but lacked in sales and marketing prowess.
Dan, welcome to the AJA world. You’ll love the tech support you get from AJA.
Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
Some additional thing to try are adding more RAM. Bump it up to 6 or 8GB and put all your old edits into a separate project and keep that project closed. For example, if you have an assembly of all your reels into a 90 minute sequence that will eat up RAM when you launch FCP. Take all the old versions of the reels and assembly’s and move them to a new project and delete them from your main edit project file.
Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
We’ve had similar problems for quite some time. Going back to FCP 3 or 4 we’ve noticed that render times can be improved with a restart. We’re now on FCP 6 and the problem still exists.
After several hours of use the render times increase greatly. For example a DVCPro 50 timeline will require 10 minutes of rendering, which I know, based on the material is way too long. After restarting FCP the same render will take less than a minute. There appears to be a memory leak issue with FCP that has existed for quite some time. That was one of the first things we tested after upgrading to FCP 6 (FCS2). No improvement.
One short term remedy is to add more RAM. We’ve found that more RAM allows you to work longer before the problem becomes noticable. Other than restarting FCP several times during the day we haven’t found a solution.Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net -
Just pre-black and code a minute or so on the BetaSP tape using the black/code button on FCP. You could also do this manually on the Beta deck but you don’t have a manual and we don’t know which model BetaSP deck you have.
Then Assemble edit to the deck by punching your In point in the ETT window. FCP does not output timecode exactly. What it does is cues up the proper In point on the deck via RS-422 and starts laying down from the in point on your sequence or wherever you place an in point on your timeline.Michael Alberts
Ambidextrous Productions, Inc.
http://www.ambidextrous.net