[Christian Reid]

Hey Dave and Todd, thanks for the replies.

Todd, I’m updating right now hoping it fixes.

Dave, I have already tried that and nothing changes.

I’ve made some other tests with minor changes. None of the things listed below worked:
– Rendering TIFF Sequence/MOV
– Multiple Frames ON/OFF
– Purge from Secret option ON/OFF
– Turning ON/OFF a little expression I did inside each Comp
– I’ve collected the files to another Mac and rendered, nothing!

What HAS worked is:
1. I’ve sent every comp I need to the Queue
2. Unchecked all the items
3. Check and render just the FIRST item
4. Delete this completed item from the Queue.
5. Render the second (that has become the #1 in the list)
And so on…

The thing is, when a comp has rendered, I NEED to remove the completed item, or it won’t reduce the time for the second one. For that, I’ve made a script with help from Dan Ebberts:

{
var rq = app.project.renderQueue;

// unqueue everything

for (var i = 1; i <= rq.numItems; i++){
rq.item(i).render = false;
}

// now queue, render, and delete them one at a time

var myItem;
while (rq.numItems > 0){
myItem = rq.item(1);
myItem.render = true;
rq.render();
myItem.remove();
}
}

It worked once, then it stopped working for no reason at all…crazy tech stuff…

I’m almost hopeless!

[Christian Reid]

Sorry about the question, I’m just trying to understand a real functionality here, not discussing how to do it.

Cmnd-A and Delete doen’t fit the purpose to clean the Render Queue?

[Christian Reid]

I’ve been having the same problem and came here to search for a solution. Obviously didn’t find it!

I have 65 comps of 5 seconds each. If I render only one at a time, it takes about 1 minute to render.
When I try to render multiple, the first one takes 1 minute, second takes 1:40, third 2:10 and so on.

It doesn’t make any sense to me, but what I’m doing right now is stoping the rendering on the 5th item in the queue, deleting the past 4 grayed-out (completed) renders and starting the 5th again.

That way I can keep acceptable render times, but I have to be constantly looking at my screen.

Really sucks! Wish I could get it solved!

I’ve tried using CS5, CS5.5 and CS6…same problem all around!!

[Christian Reid]

Hey guys, thanks very much for the assistance.

I’ve made some testing yesterday and the rolling shutter effect has indeed been reduced with my settings to 1/60 at 30fps. And I tested on a FAST subject, an Audi R8 LMS! Really cool…hehe

I hope it fixes my problems from now on, but it is also true that narrowing your stops options to just 1/30 and 1/60 certainly is a pain when you get an overexposed scene. Had the chance to test that also. You were right Bob!

Thanks again, Chris

[Christian Reid]

You need to change the keyframe value for the null object. The less pixels it moves, the slower it moves along time.

[Christian Reid]

Hey Peter, don’t worry about the english, same problem here.

I know exactly what you’re saying about moving a piece of paper on a desktop scanner and about the slower shutter speeds causing more motion blur.

But what I don’t get is the reason why shooting in multiple numbers (1/60 at 30fps) gives me less rolling shutter than shooting 30fps at non-multiple shutter speeds, even when they are faster, like 1/160.

[Christian Reid]

Bob and Peter,

thanks for the replies! You helped a lot.

There was something Bob mentioned that reminded me of the answer I got from a friend who uses the 5D.
Bob, you said you use 1/50 when recording 25fps, and I was told to use 1/60 or 1/30 when recording my videos at 30fps.

It makes some sense to use the number of stops as a multiple of FPS, but I couldn’t fully understand why he said that.

Why the heck the time it takes to record a frame can affect the way the sensor captures each frame?
And why does one need to be a multiple of the other?

From my point of view, the shortest period of time it takes to capture each frame, the less “rolling shutter” effect I would get.

Pretty complex! Can you give us a theory lesson here?

[Christian Reid]

Michael, the 1 frame duration of your TIFF is definitely a problem.

What the other Chris said about time-remapping only works (or needs to be used) on FOOTAGES or PRE-COMPS, for STILL IMAGES, like TIFF, JPEG, PNG and etc, you just need to drag the end of the layer to the right, simple as that, stretch it along time. The mouse cursor changes to a dual-pointed arrow facing left and right.

Maybe it solves the problem.

[Christian Reid]

Actually I have faced the same problem before.

There is a kind of scrubing that sometimes stops working for me. Even then, the image renders in a very low quality, but for the purpose of pre-viewing the animation before RAM preview, it works. I usually make RAM previews every time, so the scrubing works very well with the rendered preview done.

The problem is something I haven’t been able to find a button to toggle it on and off, but resetting the preferences has worked. Hold the CMND+SHIFT+OPTION very quickly after opening the application.

[Christian Reid]

Actually there is a pretty simple way.

1. Import all your original clips, preferably put them in a folder in AE project, helps keep organized.
2. Select them all and drag to the “create new comp” at the bottom of the project window.
3. In the dialog that appears, select “multiple compositions”
4. This method creates a comp for each of your clips with it’s exact file name
5. Now it’s just hard work, open each one of the compositions and paste the effect you want to the clip inside.

TIP: First, cmnd-C the effect from the “effect control” window. Now, select every COMP in your project, hit the numpad enter to open them all or double click one of the selected comps, and repeat this sequence:

cmnd-A (select all layers, in your case, just one), cmnd-V (paste the effect) and cmnd-W (close the comp window and move to the next)
That should at least make it go faster.

6. Render queue. Done. Just remember that the files will have the same name as the original, don’t export to the same location