[David Cabestany]

I have a somewhat related issue.

I have a display tag applied to a cloner, the visibility was keyframed from 100% to 0% over a second or so, and it worked fine, much like the opacity property in AE, everything faded out as expected.

Then I revised the scale property in a step effector applied to the cloner (I actually enabled and animated the scale on the step effector, before it was only affecting the rotation) and then the display tag stopped working. The keyframe values still go down from 100 to 0 over time, but the actual rendering shows the cloner disappearing from one frame to the next one at the very end, when the keyframe reaches 0.

I deleted the tag and reapplied it and the problem persists. I made a new document with a cube and the same tag and it works fine.

Any ideas?

[David Cabestany]

That must be it. the machines I used are vastly different, I’m far from having a render farm or anything like it. I used my i7 quad-core imac, and two macbook pros, one with an intel i5 processor and the other with an old intel core duo processor, that one render the least amount of frames.

I had originally rendered that same sequence using only the imac, and it rendered out fine, but took almost 30 hours, I thought that by using Net Render and several revisions I made for the second round I would be on the clear, but 25 hours and a useless render afterwards showed me otherwise.

Thanks.

[David Cabestany]

Instead of using the clipping mask command use the transparency panel and use black and white shapes.
You are going to need an outer shape that cover your original mask, in order to invert it.

It’s more steps, but as far as I know that’s the only way available in Illustrator.

[David Cabestany]

Hi Tylor, nope, I checked it as thoroughly as possible and couldn’t find anything out of the ordinary. I looked from compound paths, clipping mask, double fills/strokes, unclosed paths, effects, etc, etc, nothing seemed to be wrong with it.

I ended up retracing that shape and adding the fill again, it worked fine.

Maybe it was a semi-corrupted file or something like that.

[David Cabestany]

Command -U

[David Cabestany]

I made a 2nd screencast, this time highlighting the text instead of selecting the entire layer, the problem persists.

AE font/type color bug

Would you please watch this video and tell me if you ever ran into this issue? It has me very puzzled.

Thanks.

[David Cabestany]

Hi Vishesh,

I don’t think that was the issue, I installed the fonts provided by the other studio. The issue happened across 4 different machines.

However I was able to fix it, I repaired permissions, ran a fsck -f on the computer, trashed AE’s preferences and restarted AE holding tab, then quit it and restarted it again with Caps lock enabled and the issue went away, the fonts are reading properly now.

Thanks to Dave LaRonde who mentioned this unknown key combinations in another thread.

Best,
D.

[David Cabestany]

The cache indicators are crucial for work, some comps take 3 seconds to ramp review, some others take 5 minutes, I can’t disable them and not know how far I am from having a preview ready. Is there any other way or a bug fix in the works?

[David Cabestany]

In my experience the shift key shortcut works fine with small projects that have not many comps nested into others, as soon as the file gets a little complex or you have a comp that is nested several steps the shortcut stops working.

I submitted a bug report too, twice I think.

[David Cabestany]

In searching an alternative to add a Cuda card for my iMac I found this thread, and upon further research I found this post on the Sonnet website:

No, the NVIDIA Quadro 4000 is not Thunderbolt-compatible. Apple and Intel have prescribed specific connectivity standards for products with Thunderbolt technology interfaces. These include drivers that are recognized by Thunderbolt and allow the product to connect and disconnect while the computer is running (hot plug/unplug). Products with Thunderbolt interfaces are tested by Intel and Apple and certified as compatible with these standards.

For PCIe expansion chassis to function correctly in this Thunderbolt-connectivity paradigm, the drivers for PCIe cards used in the chassis must also be updated to support these requirements. In most cases, each card manufacturer is responsible for updating the drivers for their cards. For the Quadro, it is Apple that controls the driver in OS X.

Intel has required all PCIe chassis manufacturers to agree to list only compatible cards that have been tested to support these standards. Apple has determined that for now, there are several technical reasons why it is not a good idea for a GPU card–including the Quadro–to connect over Thunderbolt. Therefore, GPU cards do not have Thunderbolt-compatible drivers. Until Thunderbolt-compatible drivers are released for GPU cards, they will not work over Thunderbolt.

So it looks that, at least for now, we’re out of luck.