[Aaron Kent]

awesome, thanks again man. I notice that if you RAM preview this, it jumps around alot, but appears to render out to QT movie rock steady. . .

AK

[Aaron Kent]

Thanks Dan, I think thats got it working!

I don’t suppose you be open to doing a line by line breakdown of how the sampleImage hack works? I understand some of the code, but I’d love to fully comprehend the why of this one.

Either ways Thanks very Much.

AK

[Aaron Kent]

thanks Dan, that makes it a bit clear still.

AK

[Aaron Kent]

Got it to work. It was some kind of syntax thing. Here is the expression that works.

x = thisComp.layer(index-1).transform.scale[0];

[x-10,x-10]

[Aaron Kent]

Thanks for the response, but I don’t think this is the case.

AK

[Aaron Kent]

Yes, I have tried this. The font is a true type font, it’s definitely working intermittantly. I have trashed and recopied it from our Font database a couple of times. It is no doubt the culprit. I used to play a round a bit with Fontographer and I think the issue is that the copy of the font that was activate when the crash occurred had a particular unicode ID or whatever technical signifier it is and the crashed aep is looking for THAT particular ID/resource and even if I reinstall the font again I think that ID is different. Whether that’s an OSX issue or a FontExplorerX (our type manager software) issue I haven’t had the time to test or do some reading in that regard. Something in CS5 is smarter than CS4, it knows the resource is missing, but rather than trash all the layers in that composition, it simply skips over that layer. CS4 doesn’t run whatever logical process when opening the project to skip this. I think the strangest part is that CS4 decides based on the font from one layer of the particular composition having a corrupt font resource, to delete all layers in that composition (many of which are just solids, precomps, nulls etc.) Ergo, CS4 hits the bad resource and then skips over all information in the project blocked out for that composition and moves onto the next item in the project load. . .

AK

[Aaron Kent]

Tried importing it into a new CS4 project, but I just get the same collection of error messages and the same empty compostion when it opens after all the errors. Good idea though, I was sure it was gonna work.

AK

[Aaron Kent]

I actually just started copy and pasting stuff out to clipboard like mad today to get the comp rebuild as quick as I could. I will try the project import into new project ina sec and post back results. Thanks!

AK

[Aaron Kent]

Output is not my problem. The settings above cause C4D to conform my rendered movie to a specific frame rate (for instance 30 frames to 29.97). What I need is to set the project framerate setting to 29.97, so that when doing a round trip with editorial footage (at 29.97) I am preserving cut points, and clip length at drop or non drop) The maxon site says that C4D is incapable of working at anything but whole numbers (24,30,etc) That said, I’m noticing that if I import footage and then animate and export an accompanying After Effects project I end up with keyframes that fall on subframes in my 29.97 AE project. So, although I will check this setting tommorrow, from what I have read on the forums (here and on maxon site) this still seems like something they haven’t addressed.

AK