[Andrew Yoole]

Not a true solution, but a workaround when recording to tape from a point of black:

Insert a single frame black slug at the sequence in-point.

Set your tape in point back 2 frames.

For example in PAL: to record sequence from TC 00:01:00:00, set your deck in-point to 00:00:59:23.

This will record the black frame across two frames of tape, then the correct program material at 00:01:00:00.

There is no workaround for inserting segments into an existing program on tape. If you have to replace the final shot into a 90 minute program with no breaks in it, you’ll have to record the entire 90 min program to tape, using the workaround above.

Blackmagic guys, this issue needs your IMMEDIATE attention – it’s an absolute disaster for my facility at this time.

[Andrew Yoole]

On Mac, AE will recognize up to 3.5GB per process.
On Win XP/Vista AE will recognize up 3.7 GB total
On Win64 AE will recognize up to 4GB per process.

That’s per process. On all platforms, AE CS3 can run multiple render processes in the background – each process utilizing its own 3.5 -4 Gb RAM. A Quad-core CPU will run 4 processes simultaneously, using 14 GB RAM or thereabouts. Additional RAM will also allow you to run multiple applications simultaneously.

There is no virtually no difference in content or features between the new CS3 Production Premium bundle for Mac and PC platforms.

[Andrew Yoole]

Forgot to add in my previous post, using offset adjustments in Device Presets does NOT solve the problem.

[Andrew Yoole]

Kristian and all at BM,

I have exactly the same issue as mentioned above – I’ve just spent all day trying to find the cause, and am now certain this has happened as a result of FCP 5.1.4 update and/or Decklink 6.0/6.1 update.

Edit to tape results in a duplicated first frame on tape, pushing the entire program one frame late. I’ve found I can work around it by recording one frame early, then black-erasing the first frame manually with the Digital Betacam deck controls.

I have this error consistently on 3 separate systems as listed:

Mac Dual 2Ghx G5, 4Gb RAM, Decklink Pro, ATTO UL3D SCSI
Mac Quad 2.5 Ghz G5, 4 Gb RAM, Decklink Extreme PCIe, ATTO UL5D
Mac Pro 3Ghz, 5Gb RAM, Decklink HD Extreme, Internal 3-drive SATA RAID

The error occurs using internal SATA drives, internal SATA RAIDs, and Medea external SCSI RAIDs. All projects tested are Standard Def PAL.

This issue was definitely not happening prior to the FCP 5.1.4 & Decklink 6.0/6.1 update.

I don’t need to tell you this is a major headache in our workflow. All assistance GREATLY appreciated!

[Andrew Yoole]

What I meant to say was:

Don’t forget you can always make a feature request direct to Adobe:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

And if you REALLY want a powerful gradient editor within AE right now, consider GradientWerks from Zaxwerks:

https://zaxwerks.com/werks_vol1/index.shtml

[Andrew Yoole]

Don’t forget you can always make a feature request direct to Adobe:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

And if you REALLY want a powerful gradient editor within AE right now, consider GradientWerks from Zaxwerks:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[Andrew Yoole]

In order of priority:

1 – CPU Speed
2 – RAM
3 – Display card

You’ll definitely get better value from better CPU speed. Plus, you can update the display card at a later date, you can’t upgrade the CPU.

[Andrew Yoole]

Nope, I experience this issue in Tiger as well. This interface lag problem is fairly commonly talked about here and in other Forums. I think we’re stuck with it until an update is released.

[Andrew Yoole]

There’s no de-compose button as such, but the process is pretty easy. Open the precomp, select all, copy, open main comp, select precomp layer, paste, delete precomp layer.

[Andrew Yoole]

Nope, shutter angle is a function of MB. It doesn’t effect anything else. The default is 180 degrees. Try it at 360.