commandline render numbers problem:

[waiswoi3d]

I'm a little bit confused by the numbering of the commandline render output:

PROGRESS: 00091 (91): 0 Seconds
PROGRESS: 00091 (92): 1 Seconds
PROGRESS: 00093 (93): 0 Seconds
PROGRESS: 00094 (94): 0 Seconds
PROGRESS: 00094 (95): 0 Seconds
PROGRESS: 00096 (96): 0 Seconds
PROGRESS: 00096 (97): 0 Seconds
PROGRESS: 00096 (97): 1 Seconds
PROGRESS: 00098 (98): 0 Seconds
PROGRESS: 00099 (99): 0 Seconds
PROGRESS: 00099 (100): 0 Seconds

If I'm right, then the first numer means the rendered image number e.g. blabla.00099.tif and the second one is the internal nth rendered image.
If you look at the numbers they are sometimes double ones on both sides.

First I thought it is a frameRate mismatch, but all framerates are set to 24images per second. It doesnt matter if I write a movie or an image sequece.

Maybe anyone has an idea what's the reason for this behaviour.

thanks for any ideas.

[Mylenium]

I'm a little bit confused by the numbering of the commandline render output:

PROGRESS: 00091 (91): 0 Seconds
PROGRESS: 00091 (92): 1 Seconds
PROGRESS: 00093 (93): 0 Seconds
PROGRESS: 00094 (94): 0 Seconds
PROGRESS: 00094 (95): 0 Seconds
PROGRESS: 00096 (96): 0 Seconds
PROGRESS: 00096 (97): 0 Seconds
PROGRESS: 00096 (97): 1 Seconds
PROGRESS: 00098 (98): 0 Seconds
PROGRESS: 00099 (99): 0 Seconds
PROGRESS: 00099 (100): 0 Seconds

If I'm right, then the first numer means the rendered image number e.g. blabla.00099.tif and the second one is the internal nth rendered image.
If you look at the numbers they are sometimes double ones on both sides.

First I thought it is a frameRate mismatch, but all framerates are set to 24images per second. It doesnt matter if I write a movie or an image sequece.

Maybe anyone has an idea what's the reason for this behaviour.

thanks for any ideas.

Doesn't mean much. It's just the result of the delays/ differences between loading, processing and writing the frames out. The left number is just the start frame of the segment currently being loaded in the renderer while the right one just indicates that frame X of XXXX has been successfully written. It does not provide any correlation to which frame is actually being processed. If you use CS3 with multiprocessing enabled, you will see similarly odd values in the info palette even just for RAM previews - each instance tries to load 4 frames and render them, but frames are written when they are ready out of sequence.

Mylenium

Mylenium

[waiswoi3d]

Thanks a lot. Then I will modify my parser to get a correct result. At least a correct end result.