Placeholders ignore frame step #42246

New Issue

Maverick · 2014-10-15T21:16:42+02:00

Maverick commented

2014-10-15 21:16:42 +02:00

System Information
all

Blender Version
official 2.72

Short description of error
As simple as that.
When rendering an animation blender checks if every single file exists, even if the frame step is very big.
This generates a huge slowdown for both local render and network rendering.

**System Information** all **Blender Version** official 2.72 **Short description of error** As simple as that. When rendering an animation blender checks if every single file exists, even if the frame step is very big. This generates a huge slowdown for both local render and network rendering.

Maverick commented

2014-10-15 21:16:42 +02:00

Changed status to: 'Open'

Maverick commented

2014-10-15 21:16:42 +02:00

Added subscriber: @dragostanasie

Maverick commented

2014-10-15 21:22:55 +02:00

Additional note:

If the folder happens to be over a network it is impossible to stop blender during this file check loop. Only way it is to kill the process.
(at least on windows 64bit 7 and 8.1)

Additional note: If the folder happens to be over a network it is *impossible* to stop blender during this file check loop. Only way it is to kill the process. (at least on windows 64bit 7 and 8.1)

Campbell Barton self-assigned this 2014-10-19 15:35:29 +02:00

Campbell Barton commented

2014-10-28 11:44:31 +01:00

I couldn't redo this behavior.

Please include a simple blend file.

With this file & command on Linux 64bit test.blend

  strace ./blender.bin /d/test.blend -b -a 2>&1 | grep "\.png"

Output: P157

I couldn't redo this behavior. Please include a simple blend file. With this file & command on Linux 64bit [test.blend](https://archive.blender.org/developer/F120050/test.blend) ``` strace ./blender.bin /d/test.blend -b -a 2>&1 | grep "\.png" ``` Output: [P157](https://archive.blender.org/developer/P157.txt)

Campbell Barton commented

2014-11-03 19:14:09 +01:00

Moving to unconfirmed, unless someone can redo will archive.

Maverick commented

2014-11-03 19:34:04 +01:00

Can be reproduced 100% in windows (all machines must run windows):

1.default scene
2.set end frame to something huge, like 10000 frames
3.set frame step to 5000
4.set the output path to be over the network on a windows machine: \windows_laptop\render
If this fails somehow just render a bunch of files with a frame step of 2 and retry the steps.

The idea is that blender loops over every single frame (which is ok since it is needed by various systems like physics, fluid, etc).
But it also checks if the file exists over the network for every single frame.

This file existence checking causes 2 problems:
A.It makes it impossible to stop blender unless you kill it from task manager
B.Slows down the rendering for a render farm or local network

Thank you

Can be reproduced 100% in windows (all machines must run windows): 1.default scene 2.set end frame to something huge, like 10000 frames 3.set frame step to 5000 4.set the output path to be over the network on a windows machine: \\windows_laptop\render\ If this fails somehow just render a bunch of files with a frame step of 2 and retry the steps. The idea is that blender loops over every single frame (which is ok since it is needed by various systems like physics, fluid, etc). But it also checks if the file exists over the network for every single frame. This file existence checking causes 2 problems: A.It makes it impossible to stop blender unless you kill it from task manager B.Slows down the rendering for a render farm or local network Thank you

Campbell Barton commented

2014-11-04 00:45:43 +01:00

How are you testing which files are checked during render?

Maverick commented

2014-11-04 00:51:38 +01:00

Simple, it goes so slow that you actually see the frame number changing 1,2,3,4,5,6...etc.
You cannot stop it with ESC or regain control over Blender in any way until it finds a missing file to render or reaches the end frame.

Simple, it goes so slow that you actually see the frame number changing 1,2,3,4,5,6...etc. You cannot stop it with ESC or regain control over Blender in any way until it finds a missing file to render or reaches the end frame.

Maverick commented

2014-11-04 00:52:47 +01:00

btw: this bug is not listed in my authored bugs list (maybe some issue with phabricator ?)

Campbell Barton commented

2014-11-04 10:29:08 +01:00

Where do you see the frame numbers change?

I checked the code and its highly unlikely that windows is behaving differently to Linux in this respect.

Please don't assume the cause of the bug, just report the errors you observe, in detail - so we can investigate.

Where do you see the frame numbers change? I checked the code and its highly unlikely that windows is behaving differently to Linux in this respect. **Please don't assume the cause of the bug, just report the errors you observe, in detail - so we can investigate.**

Bastien Montagne commented

2014-11-12 19:15:46 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-11-12 19:15:46 +01:00

Bastien Montagne commented

2014-11-12 19:15:46 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2014-11-12 19:15:46 +01:00

No news since one week…

Maverick commented

2014-11-13 10:59:05 +01:00

When you move the mouse during rendering the frame number on the timeline changes so you can see how it goes over every single frame.
It goes so slow that you can see the frames being evaluated one by one regardless of the frame step.

This is one of the oldest and ugliest bugs in Blender well known for windows users.
Anyway I am too tired to give additional details since you are not reproducing the bug as reported.
Instead you are making assumptions about how the code works...

When you move the mouse during rendering the frame number on the timeline changes so you can see how it goes over every single frame. It goes so slow that you can see the frames being evaluated one by one regardless of the frame step. This is one of the oldest and ugliest bugs in Blender well known for windows users. Anyway I am too tired to give additional details since you are not reproducing the bug as reported. Instead you are making assumptions about how the code works...

Campbell Barton commented

2014-11-14 12:10:11 +01:00

I monitored disk access during render, so the bug (as you reported it), I can't redo.

Please always submit a blend file & exact steps to redo, maybe there is some other reason for disk access which depends on the blend file.

Its also possible the frame stepping is slow (which may be a bug), but is unrelated to network/disk access.

You really have to give us the exact scenario showing the problem you have, so we can redo the error.

I monitored disk access during render, so the bug (as you reported it), I can't redo. Please _always_ submit a blend file & exact steps to redo, maybe there is some other reason for disk access which depends on the blend file. Its also possible the frame stepping is slow (which may be a bug), but is unrelated to network/disk access. You really have to give us the exact scenario showing the problem you have, so we can redo the error.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Placeholders ignore frame step #42246