[Arne Münch]

oh sorry, I am not a native english speaker..
I just wanted to say, that the fan (I think the one of the graphic card, but maybe also the fan of the processor) runs relatively loud without stopping if AE is running, no matter if there is something to process or not.
If I delete my graphic card from that text file again, the fan doesn´t run permanently.

[Arne Münch]

Hi
I am testing this “hack” with a quite simple “GeForce GT 530”, and it works very good, much faster than cpu rendering.
But if I start AE with this new entry in the “raytracer_supported_cards.txt”, there is a permanent ventilation going on in my PC, which is otherwise not.
Even if there is only one empty composition, which is switched to “Classic 3D”, and there is no action at all, the permanent ventilation doesn´t stop. Any thoughts on that?
Thanks a lot..

[Arne Münch]

Thank you both. The script from Xavier worked perfect for my purpose. Seems to be a bit complicated with the shape layers, though. Thanks a lot for figuring it out..

I was just wondering because the script affected the Position value of the shape, in the category where there is only Position and Size, not the “Transform:Ellipse 1 properies” where you can find Scale and all the others. So change the line to “var propToReplace = “Scale”” won´t work I guess.
For me it worked but maybe its for general interest how to refer to these other values..

[Arne Münch]

Thanks a lot for your afford, that is very good and helpful.

I am new to scripts and I tried modifying your line
prop = layer.transform.position;
To
prop = layer.transform.scale;
or even
prop = layer(“Effects”)(“Fast Blur”)(“Blurriness”);
works nice 😉

One additional question:
How do I have to change the line to access for example the following properties of a shape layer:
Contents/Group 1/Ellipse 1/Transform:Ellipse 1/Position
And this in a for-loop for all Ellipses in this Group(Ellipse 1,Ellipse 2,Ellipse 3,etc.)?

Then I think I could find out how to access every property I want.
thanks again.

leif

[Arne Münch]

Hallo Dan

thanks for your reply, I tested your way and the performance seems in fact to be even worse.

That means that long arrays are not meant to be stored and accessible via expressions in a proper way, aren´t they?

[Arne Münch]

Hi guys
For those who have older versions, here is what I ended up with and I am quite satisfied:

Instead of writing the expression into “timeremap” I used the effect “timewarp” which also has an option for “source frame”. For this I wrote Dans expression, (but without the Math.round for smoother results.)

L = thisComp.layer(“luma”);
p = L.fromComp(toComp(transform.anchorPoint));
s = L.sampleImage(p,[.5,.5],true);
luma = rgbToHsl(s)[2];
maxFrame = 300;
f = maxFrame*luma;
framesToTime(f)

The one problematic difference is, the effect time warp doesn´t look in-between frames in the nested comp, like “time remapping” does, so you will not have the same smoothness, but here is a little trick:
Just use “time-remapping” as well without any expression, and give it a lot of space. For example if your nested comp is 30 Frames long, span this 30 Frames with time Remap over a space of 300 Frames, so the “Time Warp” effect has a lot of real in-between Frames, (not calculated ones through FrameMix or PixelMotion).
Give it a try..

[Arne Münch]

Hi again
I couldn´t figure out how to avoid this nasty message. But I found a way to reproduce the error instantly in my example file.
Make a Ram Preview of MAIN. Go into FORM, grab and pull the In-point of the shape-layer forwards, got back to MAIN Comp and the Error will appear. If anyone could help here, It would be so great.

[Arne Münch]

Change the in and outpoints of the “Luma” layer also, and repeat the steps. The error will appear.
By the way: The problem isn´t this comp, I could easily live with that rarely appearing error message, but if I use this method to drive a grid of layers like in the first post, and have other things going on in the comp, it really gets annoying.

[Arne Münch]

Hallo Dan
Thank you for your help.
I broke down my project to just two layers, and for every item I deleted, the error-message became more rarely, but it is still there.
I attached a very simple AE file. Have the layer FORM in MAIN selected, go into the FORM Comp, change the inpoint or the outpoint of the shapelayer, or the position of the rotation keyframe. Go Back to the main comp and change the color of the circle in the LUMA Layer. Repeat these steps, or change other things, and the error message will occur. I tested here on CS3 and with CS5 at work, several times.
And the more items are in the composition, the more often the error occurs. I get a little crazy I guess.
Here is the project-file:
4387_unbenanntesprojekt.aep.zip

[Arne Münch]

Hi Everybody
I am getting the same error and the whole world of google gives only 8 hits:
https://tinyurl.com/d36t5nz

Dan, your last script doesn´t seem to resolve the error, i am getting the same message like before.
Jay, Did you solve it someow?

THanks for the great support here.