Multiple image files imported as animation are strangely linked with another imported subsets of these images #91443

New Issue

ichlubna · 2021-09-15T19:53:44+02:00

ichlubna commented

2021-09-15 19:53:44 +02:00

System Information
Operating system: Arch Liunx

Blender Version
Broken: 2.93.4, branch: makepkg (modified), commit date: 2021-08-31 09:23, hash: b7205031ce
Also confirmed in: 3.0.0 Alpha, branch: master, commit date: 2021-08-28 20:38, hash: 4256eeeec4

When importing a sequence of frames in the Compositor into an Image node the settings such as Start frame in this node affect other similarly loaded node which works with the same input files that were separately selected. I would expect these to behave as two independent resources, especially when the animation doesn't event consist of the same data (subset of the original one).

Exact steps for others to reproduce the error

Go to Compositor
Add Image node
Load image sequence there
Set Start frame to a value greater than zero
Add new Image node with a subset of the previously used frames
Look at the output of this new node in frames that are before the Start frame of the first node

I have included the project file, short animation and a video showing the problem in the attachment.
frames.zip

**System Information** Operating system: Arch Liunx **Blender Version** Broken: 2.93.4, branch: makepkg (modified), commit date: 2021-08-31 09:23, hash: b7205031cec4 Also confirmed in: 3.0.0 Alpha, branch: master, commit date: 2021-08-28 20:38, hash: 4256eeeec4ca **When importing a sequence of frames in the Compositor into an Image node the settings such as Start frame in this node affect other similarly loaded node which works with the same input files that were separately selected. I would expect these to behave as two independent resources, especially when the animation doesn't event consist of the same data (subset of the original one).** **Exact steps for others to reproduce the error** 1. Go to Compositor 2. Add Image node 3. Load image sequence there 4. Set Start frame to a value greater than zero 5. Add new Image node with a subset of the previously used frames 6. Look at the output of this new node in frames that are before the Start frame of the first node I have included the project file, short animation and a video showing the problem in the attachment. [frames.zip](https://archive.blender.org/developer/F10420383/frames.zip)

ichlubna commented

2021-09-15 19:53:44 +02:00

Added subscriber: @ichlubna

ichlubna changed title from ~~Multiple image files imported as animations are strangely linked with imported subsets of the images~~ to Multiple image files imported as animation are strangely linked with another imported subsets of these images

2021-09-15 19:54:13 +02:00

Omar Emara commented

2022-02-09 12:45:29 +01:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-02-09 12:45:29 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Omar Emara commented

2022-02-09 12:45:29 +01:00

It seems image sequences are identified by the path of the first image in the sequence, so if you select a subset of the images whose first selected image is the same as a previously selected sequence, no new image sequence will be added and the nodes will share the same sequence. However, each user of the image sequence keeps its own structure of properties like Start/Offset/Frames. You can also create a copy of the image sequence by pressing the user count button.
So this doesn't look like a bug to me, but an expected behavior. Though a developer should take a look just to confirm.

It seems image sequences are identified by the path of the first image in the sequence, so if you select a subset of the images whose first selected image is the same as a previously selected sequence, no new image sequence will be added and the nodes will share the same sequence. However, each user of the image sequence keeps its own structure of properties like Start/Offset/Frames. You can also create a copy of the image sequence by pressing the user count button. So this doesn't look like a bug to me, but an expected behavior. Though a developer should take a look just to confirm.

Philipp Oeser commented

2022-02-09 15:52:58 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-02-09 15:52:58 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Philipp Oeser commented

2022-02-09 15:52:58 +01:00

Having trouble isolating what the problem is here

Look at the output of this new node in frames that are before the Start frame of the first node

For me, the image is held at frame 1 for the left node on all frames > 1 (it does not disappear for me)
In your video, these seem to disappear (e.g. on frame 3), is this the issue you are reporting?

Dont think this has to do with the fact that the image datablocks are shared, the imageuser (Start/Offset/Frames) is on the node, so that should be separated already.

The fact that the whole output of the nodetree is black is the result of the mix nodes factors all at 1, so only the second/right node's output is considered, but that is not the point in this report, right?)

Having trouble isolating what the problem is here > Look at the output of this new node in frames that are before the Start frame of the first node For me, the image is held at frame 1 for the left node on all frames > 1 (it does not disappear for me) In your video, these seem to disappear (e.g. on frame 3), is this the issue you are reporting? Dont think this has to do with the fact that the image datablocks are shared, the imageuser (Start/Offset/Frames) is on the node, so that should be separated already. The fact that the whole output of the nodetree is black is the result of the mix nodes factors all at 1, so only the second/right node's output is considered, but that is not the point in this report, right?)

ichlubna commented

2022-02-09 18:53:00 +01:00

In #91443#1304885, @lichtwerk wrote:
is this the issue you are reporting?

I think that @OmarEmaraDev described the problem well and I believe that it is a bug. It's to be expected that when I add a sequence, it would behave as new. This apparently makes it impossible to create some specific effects and scenes without additional hacks like copying the source files to a different location etc.

> In #91443#1304885, @lichtwerk wrote: > is this the issue you are reporting? I think that @OmarEmaraDev described the problem well and I believe that it is a bug. It's to be expected that when I add a sequence, it would behave as new. This apparently makes it impossible to create some specific effects and scenes without additional hacks like copying the source files to a different location etc.

Philipp Oeser commented

2022-02-09 19:34:13 +01:00

It's to be expected that when I add a sequence, it would behave as new.

Sorry if I am misunderstanding: what is not behaving as "new"?

> It's to be expected that when I add a sequence, it would behave as new. Sorry if I am misunderstanding: **what** is not behaving as "new"?

Omar Emara commented

2022-02-09 19:55:18 +01:00

To clarify, we can't really replicate the issue you described, that is, a different image node having no output when its current frame is lower than the start frame of another node using the same image sequence.
Two image nodes are still independent and new in their use of image sequences, they can sample the sequence at any time independent of each other. You can still copy the sequence itself as described before, but it doesn't provide any advantages in this case in particular. The sharing of the underlying sequence can be noticed when you change the offset of the node, even though you opened a single image, you can sample any other image in the sequence.

To clarify, we can't really replicate the issue you described, that is, a different image node having no output when its current frame is lower than the start frame of another node using the same image sequence. Two image nodes are still independent and new in their use of image sequences, they can sample the sequence at any time independent of each other. You can still copy the sequence itself as described before, but it doesn't provide any advantages in this case in particular. The sharing of the underlying sequence can be noticed when you change the offset of the node, even though you opened a single image, you can sample any other image in the sequence.

ichlubna commented

2022-02-09 20:01:24 +01:00

@lichtwerk @OmarEmaraDev Hmmm it seems like this issue is fixed in the most recent version of Blender. I can't reproduce it either as I captured it in the video at the beginning of this thread.

In #91443#1305004, @OmarEmaraDev wrote:
they can sample the sequence at any time independent of each other.

That was the problem. I couldn't achieve this before which seems to be working now.
Thank you anyway!

@lichtwerk @OmarEmaraDev Hmmm it seems like this issue is fixed in the most recent version of Blender. I can't reproduce it either as I captured it in the video at the beginning of this thread. > In #91443#1305004, @OmarEmaraDev wrote: >they can sample the sequence at any time independent of each other. That was the problem. I couldn't achieve this before which seems to be working now. Thank you anyway!

Philipp Oeser commented

2022-02-10 05:32:02 +01:00

Changed status from 'Needs User Info' to: 'Resolved'

Philipp Oeser closed this issue

2022-02-10 05:32:02 +01:00

Philipp Oeser self-assigned this 2022-02-10 05:32:02 +01:00

Philipp Oeser commented

2022-02-10 05:32:02 +01:00

Oki, thx getting back, lets call this resolved then.

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

Multiple image files imported as animation are strangely linked with another imported subsets of these images #91443