Video texture / Image Sequence not refreshing under eevee #57457

New Issue

Eric Serpi · 2018-10-28T18:18:04+01:00

Eric Serpi commented

2018-10-28 18:18:04 +01:00

{F5282778}System Information
Mac OSX and gtx 980 ti

Blender Version
Broken: 2.80.0 3bc8bc0709

When navigating in timeline, shader with video texture doesn't refresh with eevee , but it's working when I switch to cycles

EDIT: same result in viewport or render (ctrl F12)

{[F5282778](https://archive.blender.org/developer/F5282778/test.zip)}**System Information** Mac OSX and gtx 980 ti **Blender Version** Broken: 2.80.0 3bc8bc0709a **When navigating in timeline, shader with video texture doesn't refresh with eevee , but it's working when I switch to cycles** EDIT: same result in viewport or render (ctrl F12)

Eric Serpi commented

2018-10-28 18:18:04 +01:00

Added subscriber: @Ericserpi

blender-admin commented

2018-10-28 18:18:04 +01:00

#61680 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60878 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60728 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60716 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60644 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#56715 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60414 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60371 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60297 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#59394 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60255 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60035 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#60026 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#59148 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#59277 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#59139 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#58418 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#58804 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#58724 was marked as duplicate of this issue

blender-admin commented

2018-10-28 18:18:04 +01:00

#58052 was marked as duplicate of this issue

Philipp Oeser commented

2018-10-29 10:51:51 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-10-29 10:51:51 +01:00

Please always provide a simple .blend file that demonstrates the issue.
(It takes time setting these up -- also it makes sure we are all on the same page then)

also: is this about viewport rendering (or F12?)?

Marking as incomplete until we have these...

Please always provide a simple .blend file that demonstrates the issue. (It takes time setting these up -- also it makes sure we are all on the same page then) also: is this about viewport rendering (or F12?)? Marking as incomplete until we have these...

Philipp Oeser commented

2018-11-04 16:34:43 +01:00

Added subscriber: @fclem

Philipp Oeser commented

2018-11-04 16:34:43 +01:00

Confirmed.
Before digging deeper: @fclem: is this a known limitation atm.?

Confirmed. Before digging deeper: @fclem: is this a known limitation atm.?

Clément Foucault commented

2018-11-04 18:36:15 +01:00

Nope. It's something that seems to have been remove when removing the BGE. I know nothing on how it was done before and what would be the best way to reimplement this.

Clément Foucault commented

2018-11-04 18:45:05 +01:00

Well I hoped something like that would work:

diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c
index e9d874bd1ee..2cf3494802d 100644
--- a/source/blender/draw/intern/draw_manager_data.c
+++ b/source/blender/draw/intern/draw_manager_data.c
@@ -40,6 +40,8 @@
 - include "BLI_link_utils.h"
 - include "BLI_mempool.h"
 
+#include "DEG_depsgraph_query.h"
+
 #include "intern/gpu_codegen.h"
 
 struct GPUVertFormat *g_pos_format = NULL;
@@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct
 			GPUTexture *tex = NULL;
 
 			if (input->ima) {
-				double time = 0.0; /* TODO make time variable */
+				double time = DEG_get_ctime(DST.draw_ctx.depsgraph);
 				tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time);
 			}
 			else {

But GPU_texture_from_blender does not do anything with time...

Well I hoped something like that would work: ``` diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c index e9d874bd1ee..2cf3494802d 100644 --- a/source/blender/draw/intern/draw_manager_data.c +++ b/source/blender/draw/intern/draw_manager_data.c @@ -40,6 +40,8 @@ - include "BLI_link_utils.h" - include "BLI_mempool.h" +#include "DEG_depsgraph_query.h" + #include "intern/gpu_codegen.h" struct GPUVertFormat *g_pos_format = NULL; @@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct GPUTexture *tex = NULL; if (input->ima) { - double time = 0.0; /* TODO make time variable */ + double time = DEG_get_ctime(DST.draw_ctx.depsgraph); tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time); } else { ``` But GPU_texture_from_blender does not do anything with `time`...

Philipp Oeser commented

2018-11-04 19:32:10 +01:00

Will also have a look tomorrow [cycles seems to be updating -- in rendered view...]

Philipp Oeser commented

2018-11-27 14:37:58 +01:00

Added subscriber: @MarceloBeck

Philipp Oeser commented

2018-12-05 10:55:13 +01:00

Added subscriber: @mhcall

arn drul commented

2018-12-05 12:05:15 +01:00

Added subscriber: @al.mijn.email

Martin Harth commented

2018-12-05 18:18:08 +01:00

Hi Philipp,

I have added a testfile Kati_test.blend.

The Clip I could not pack into blender, so I add the mp4 clip in addition (zip).
The Video texture is 2009 12 26 Kati 2_1.zip.

No timeline reresh and no frame refresh with Ctrl+F12.

Hi Philipp, I have added a testfile [Kati_test.blend](https://archive.blender.org/developer/F5837460/Kati_test.blend). The Clip I could not pack into blender, so I add the mp4 clip in addition (zip). The Video texture is [2009 12 26 Kati 2_1.zip](https://archive.blender.org/developer/F5837620/2009_12_26_Kati_2_1.zip). No timeline reresh and no frame refresh with Ctrl+F12.

Brecht Van Lommel commented

2018-12-05 18:34:08 +01:00

Added subscriber: @vistula_waves

Daniel Salazar commented

2018-12-06 20:27:38 +01:00

Added subscriber: @zanqdo

Daniel Salazar commented

2018-12-06 20:27:38 +01:00

Hi, any update or workaround on this issue? We're being hit by it :)

Daniel Salazar commented

2018-12-06 22:20:14 +01:00

Well in case anyone else needs it urgently, for now I've hacked it with a frame change handler. It works in viewport and render but only if the image editor is present :p

Well in case anyone else needs it urgently, for now I've hacked it with a frame change handler. It works in viewport and render but only if the image editor is present :p ![image.png](https://archive.blender.org/developer/F5861336/image.png)

Martin Harth commented

2018-12-06 22:56:05 +01:00

Hi Daniel,

Thank you very much for taking care!
The script runs well in the Image Editor, however I couldn't manage to run it in the render view, please see my test Image added here.
May be I made a mistake…?

Hi Daniel, Thank you very much for taking care! The script runs well in the Image Editor, however I couldn't manage to run it in the render view, please see my test Image added here. May be I made a mistake…?![clip_test.jpg](https://archive.blender.org/developer/F5861512/clip_test.jpg)

Sebastian Parborg commented

2018-12-07 16:03:32 +01:00

Added subscriber: @Zacc

Daniel Salazar commented

2018-12-07 19:57:46 +01:00

@mhcall You have a typo in line 4.

Martin Harth commented

2018-12-07 20:58:59 +01:00

Thanks, Daniel!
Repaired… nevertheless… no Ctrl+F12 result… stucks at one Frame.
Scrolling timeline, the Image Editor refreshes well, though.

Thanks, Daniel! Repaired… nevertheless… no Ctrl+F12 result… stucks at one Frame. Scrolling timeline, the Image Editor refreshes well, though.

Martin Harth commented

2018-12-07 20:59:53 +01:00

and.. which built is in use at your site?

Daniel Salazar commented

2018-12-08 00:31:15 +01:00

@mhcall It does work with rendering animation for me

Daniel Salazar commented

2018-12-08 00:33:33 +01:00

@mhcall I see you have 2 copies of the movie, the one your referencing in the script is Kati.mp4, the one in the image editor is Kati.mp4.001

The image editor has to have the same movie displayed.

@mhcall I see you have 2 copies of the movie, the one your referencing in the script is Kati.mp4, the one in the image editor is Kati.mp4.001 The image editor has to have the same movie displayed.

Martin Harth commented

2018-12-08 00:55:50 +01:00

Yes, you're right. I reloaded the orgingal 'Kati.mp4'.. however, it won't seem to work in the render view.
This is my current blender Version

And this was - at least at my place here - the last 2.8x blender Version, which worked well with animated textrues:

Eventually this hint might help to locate the "bug" (?)....t.

Yes, you're right. I reloaded the orgingal 'Kati.mp4'.. however, it won't seem to work in the render view. This is my current blender Version ![blender_version.jpg](https://archive.blender.org/developer/F5876620/blender_version.jpg) And this was - at least at my place here - the last 2.8x blender Version, which worked well with animated textrues: ![blender_version-2018-04-10.jpg](https://archive.blender.org/developer/F5876738/blender_version-2018-04-10.jpg) Eventually this hint might help to locate the "bug" (?)....t.

arn drul commented

2018-12-09 16:25:08 +01:00

for easy copy paste:

import bpy

def clipReload(scene):
    bpy.data.images['pasteclipnamere.mp4'].reload()
    print('Clip Reloaded')
    
bpy.app.handlers.frame_change_pre.append(clipReload)

for easy copy paste: ``` import bpy def clipReload(scene): bpy.data.images['pasteclipnamere.mp4'].reload() print('Clip Reloaded') bpy.app.handlers.frame_change_pre.append(clipReload) ```

Philipp Oeser commented

2018-12-10 21:37:51 +01:00

Added subscribers: @VFX_Man, @StephenSwaney

Daniel Salazar commented

2018-12-10 23:04:01 +01:00

I don't know what else to say :) The hack works for me. Did you actually execute the script? In my original screenshot I have the Register option enabled. This makes it so that the script is executed automatically on load. Also the Auto Run Python Scripts preference must be enabled..

Daniel Salazar commented

2018-12-12 02:05:34 +01:00

This comment was removed by @zanqdo

*This comment was removed by @zanqdo*

Daniel Salazar commented

2018-12-12 02:14:31 +01:00

OK I found a hack for the hack :) When rendering doesn't work, you can render a "Playblast" with View/Viewport Render Animation.

The problem is the viewport render doesn't respect sample settings..

OK I found a hack for the hack :) When rendering doesn't work, you can render a "Playblast" with View/Viewport Render Animation. The problem is the viewport render doesn't respect sample settings..

Brecht Van Lommel commented

2018-12-13 00:24:15 +01:00

Added subscriber: @jmekiff

Brecht Van Lommel commented

2018-12-13 00:24:23 +01:00

Added subscriber: @MarcelLegindi

Relja Trajković commented

2018-12-17 22:02:22 +01:00

Added subscriber: @ReljaTrajkovic

Arsen Mikitov commented

2018-12-19 06:30:50 +01:00

Added subscriber: @ArsenMikitov

Arsen Mikitov commented

2018-12-19 06:30:50 +01:00

In #57457#571701, @zanqdo wrote:
Well in case anyone else needs it urgently, for now I've hacked it with a frame change handler. It works in viewport and render but only if the image editor is present :p

Thank you, great man! This way works for me! At first there were problems, but I saw the "Register" switch in the text editor. When I turned it on, the script worked. Now I see animated textures :) Super.
Blender 2.80 beta. Linux Ubuntu x64. Eevee. RTX-2080Ti.

> In #57457#571701, @zanqdo wrote: > Well in case anyone else needs it urgently, for now I've hacked it with a frame change handler. It works in viewport and render but only if the image editor is present :p > > ![image.png](https://archive.blender.org/developer/F5861336/image.png) Thank you, great man! This way works for me! At first there were problems, but I saw the "Register" switch in the text editor. When I turned it on, the script worked. Now I see animated textures :) Super. Blender 2.80 beta. Linux Ubuntu x64. Eevee. RTX-2080Ti.

Vladimir commented

2018-12-19 18:15:10 +01:00

Added subscriber: @VladimirKunyansky

Vladimir commented

2018-12-19 18:35:19 +01:00

@zanqdo , I tried your option and it works, thanks!

BUT!

Having tested several versions (now checked on the last 1fc75dbbce) and video texture is updating only when several conditions is true:

only the active object is updated, but not selected (provided that there are several objects with different video textures in the scene);
the texture is updated only if a node with a texture is selected in the shader settings window;
the texture is updated only when the N-panel is open (in shader window) and when the "Properties" tab is expanded.

If all conditions are met, the texture is updated even when rendered.

Update:
Oh. Sorry. "If the image editor is present" - i see.
The working variant for several objects with video textures is to open several working windows with image editors and in each of them open different textures.

@zanqdo , I tried your option and it works, thanks! **BUT!** Having tested several versions (now checked on the last 1fc75dbbceea) and video texture is updating only when several conditions is true: - only the active object is updated, but not selected (provided that there are several objects with different video textures in the scene); - the texture is updated only if a node with a texture is selected in the shader settings window; - the texture is updated only when the N-panel is open (in shader window) and when the "Properties" tab is expanded. If all conditions are met, the texture is updated even when rendered. **Update:** Oh. Sorry. "If the image editor is present" - i see. The working variant for several objects with video textures is to open several working windows with image editors and in each of them open different textures. ![video_texture_update_2.jpg](https://archive.blender.org/developer/F6008593/video_texture_update_2.jpg)

Deen commented

2018-12-21 19:50:31 +01:00

Added subscriber: @De3n

Vladimir commented

2018-12-24 19:53:23 +01:00

I don't know, if this can help, but i finded deleted code from internal render for update image sequences and movies in (https://developer.blender.org/rB51b796ff1528c52cc8b4079fab1003671652a4d9):

file: source/blender/render/intern/source/render_texture.c
line: 3827

if (tex->ima && BKE_image_is_animated(tex->ima)) {
BKE_image_user_check_frame_calc(&tex->iuser, (int)scene->r.cfra,
0);

I don't know, if this can help, but i finded deleted code from internal render for update image sequences and movies in (https://developer.blender.org/rB51b796ff1528c52cc8b4079fab1003671652a4d9): file: source/blender/render/intern/source/render_texture.c line: 3827 ``` if (tex->ima && BKE_image_is_animated(tex->ima)) { BKE_image_user_check_frame_calc(&tex->iuser, (int)scene->r.cfra, 0); ```

Ian Garrison commented

2018-12-28 11:20:34 +01:00

Added subscriber: @technoendo

Ian Garrison commented

2018-12-28 11:20:34 +01:00

I grabbed Blender 2.80 0661bcba32 from 12/27/2018 and was having some problems with an h264/mov video file used as a texture in Eevee when I was pleased to see a bug was already filed. I tried the frame change handler workaround mentioned by zanqdo, which did update the image viewer + 3d view but ctrl+f12 rendering out animations behaves strangely. Usually the first frame will render out as expected, so rendering out 1 frame (f12) does work, but subsequent frames in an animation will be black in the areas where the movie texture should be.

Next, I used ffmpeg to extract every frame of the h264/mov video as png images. In this case the frame change handler workaround is not needed. I still get similar results: I can scrub through my timeline and see the entire video updating with each frame update as expected (in eevee 3d viewport and in the image viewer), but again... when I render the first frame renders OK but subsequent frames have bright pink where the image sequence should be.

Rendering individual frames (f12) does yield the expected output in the render buffer which can be saved to a file. This is a painful way to render an animation doing this manually in the UI.

This made me wonder if I could do some command line render tricks, run a bash while loop to iterate on every frame, and run blender -b file.blend -f $frame? This did not work and the video frames were always the first frame from the video/image sequence. I also tried "-a" to render out the entire animation instead of specifying it frame by frame and also had the same problem of only the first frame of the video/image sequence being used.

I tried 4 other builds of Blender 2.80 from late November through today and results were all consistent. In reading this thread I think I'm in the same spot as @mhcall. That a bit of python is required to get the 3d viewport updated so its in sync with the image viewer, which fixes f12 renders, but this does not allow ctrl-f12 animations to render.

I grabbed Blender 2.80 0661bcba3210 from 12/27/2018 and was having some problems with an h264/mov video file used as a texture in Eevee when I was pleased to see a bug was already filed. I tried the frame change handler workaround mentioned by zanqdo, which did update the image viewer + 3d view but ctrl+f12 rendering out animations behaves strangely. Usually the first frame will render out as expected, so rendering out 1 frame (f12) does work, but subsequent frames in an animation will be black in the areas where the movie texture should be. Next, I used ffmpeg to extract every frame of the h264/mov video as png images. In this case the frame change handler workaround is not needed. I still get similar results: I can scrub through my timeline and see the entire video updating with each frame update as expected (in eevee 3d viewport and in the image viewer), but again... when I render the first frame renders OK but subsequent frames have bright pink where the image sequence should be. Rendering individual frames (f12) does yield the expected output in the render buffer which can be saved to a file. This is a painful way to render an animation doing this manually in the UI. This made me wonder if I could do some command line render tricks, run a bash while loop to iterate on every frame, and run blender -b file.blend -f $frame? This did not work and the video frames were always the first frame from the video/image sequence. I also tried "-a" to render out the entire animation instead of specifying it frame by frame and also had the same problem of only the first frame of the video/image sequence being used. I tried 4 other builds of Blender 2.80 from late November through today and results were all consistent. In reading this thread I think I'm in the same spot as @mhcall. That a bit of python is required to get the 3d viewport updated so its in sync with the image viewer, which fixes f12 renders, but this does not allow ctrl-f12 animations to render.

Arsen Mikitov commented

2018-12-28 12:27:07 +01:00

but this does not allow ctrl-f12 animations to render.

Yes, I was also happy at first that the texture works, but Ctrl+F12 gives a texture with blinking black images.

> but this does not allow ctrl-f12 animations to render. Yes, I was also happy at first that the texture works, but Ctrl+F12 gives a texture with blinking black images.

Martin Harth commented

2018-12-28 12:42:44 +01:00

@Ian-117 Garrison's and @Arsen Mikitiov's expereinces are correct.
Unfortunately the Ctrl+F12 coommand results in wierd animations with partly pink Frames and "Blackout" all over.

My personal workaround since is this:
I take all respective objects incl. the camera + paths into Cycles 2.7.94 (in my opinion the best and fastest Cycles build ever, #bae880d as from 2018-05-25). Then I apply a HOLDOUT material to all objects that might hide or partly cover the movie clip texture plane. The rendered sequence I put as an additional layer on top of the original sequence (into After Effects for example)…. and this works smoothly.

The time loss with this workaround is half way acceptable. However it would be so great if the 2.8x beta would be "healed"....

@Ian-117 Garrison's and @Arsen Mikitiov's expereinces are correct. Unfortunately the Ctrl+F12 coommand results in wierd animations with partly pink Frames and "Blackout" all over. My personal workaround since is this: I take all respective objects incl. the camera + paths into Cycles 2.7.94 (in my opinion the best and fastest Cycles build ever, #bae880d as from 2018-05-25). Then I apply a HOLDOUT material to all objects that might hide or partly cover the movie clip texture plane. The rendered sequence I put as an additional layer on top of the original sequence (into After Effects for example)…. and this works smoothly. The time loss with this workaround is half way acceptable. However it would be so great if the 2.8x beta would be "healed"....

Daniel Salazar commented

2018-12-28 21:21:29 +01:00

Guys what I had to do is rendering with the Render OGL way from the viewport, it lacks quality controls but it works with movies with my workaround. Hope that helps!

Sebastian Parborg commented

2019-01-01 12:58:51 +01:00

Added subscriber: @Gie

Sebastian Parborg commented

2019-01-01 15:14:18 +01:00

Added subscriber: @antoine.clenet

Vladimir commented

2019-01-06 02:13:19 +01:00

@fclem , if you give a hint, then I can help with finding a problem. In my opinion, this is due to BKE_image_user_check_frame_calc, since I found a similar problem:
https://lists.blender.org/pipermail/bf-blender-cvs/2013-May/056122.html

- / * update animated image textures for gpu, etc,
- * call before BKE_scene_update_for_newframe so modifiers with textures don't lag 1 frame * /
- ED_image_update_frame (bmain, scene-> r.cfra);
-
  ED_clip_update_frame (bmain, scene-> r.cfra);

@fclem , if you give a hint, then I can help with finding a problem. In my opinion, this is due to **BKE_image_user_check_frame_calc**, since I found a similar problem: https://lists.blender.org/pipermail/bf-blender-cvs/2013-May/056122.html ``` - / * update animated image textures for gpu, etc, - * call before BKE_scene_update_for_newframe so modifiers with textures don't lag 1 frame * / - ED_image_update_frame (bmain, scene-> r.cfra); - ED_clip_update_frame (bmain, scene-> r.cfra); ```

Brecht Van Lommel commented

2019-01-07 10:27:28 +01:00

Added subscriber: @KyleAustin

Brecht Van Lommel commented

2019-01-07 10:27:59 +01:00

Added subscribers: @gigi-4, @Serra1973, @Kavukamari

Mike Futcher commented

2019-01-07 21:05:40 +01:00

Added subscriber: @MikeFutcher

Mike Futcher commented

2019-01-07 21:05:40 +01:00

Thanks for that excellent little script quick-fixing this bug, Daniel Salazar (zanqdo). You'll be pleased to know it works for videos in environment textures as well. Do you mind if I include it in a tutorial I have planned? How would you like to be credited?

Mike Futcher commented

2019-01-07 21:09:20 +01:00

Ahh.. but it doesn't work for looping videos.

Mike Futcher commented

2019-01-07 21:53:12 +01:00

And for some even more bazaar reason - it won't go past frame 97. I guess it's a memory problem? Tried the same scene with a few different videos in the same scene so far... but I might make this reporting bugs on a script rather than Blender if I'm not careful. I guess I'll be putting my greenscreen nodegroup for material nodes on hold.

Daniel Salazar commented

2019-01-07 22:28:37 +01:00

@MikeFutcher let's just hope this get's fixed properly :)

boucles-d-art.com commented

2019-01-07 23:36:41 +01:00

Surely video textures and image sequences will be debugged if the Spring movie team requires their use! ;-)
Very nice work in progress to see on the cloud of blender :-)

Surely video textures and image sequences will be debugged if the Spring movie team requires their use! ;-) Very nice work in progress to see on the cloud of blender :-)

Philipp Oeser commented

2019-01-08 09:35:19 +01:00

Added subscriber: @istoltoto

Philipp Oeser changed title from ~~Video texture not refreshing under eevee~~ to Video texture / Image Sequence not refreshing under eevee

2019-01-08 09:35:48 +01:00

pistol ioan commented

2019-01-08 12:24:32 +01:00

Thanks for the script Daniel
However, it seems that it doesn't work when you change the Start Frame to something higher.
But a very good workaround till the bug is solved.

Thanks for the script Daniel However, it seems that it doesn't work when you change the Start Frame to something higher. But a very good workaround till the bug is solved.

Philipp Oeser commented

2019-01-09 15:34:17 +01:00

Added subscribers: @Sergey, @brecht

Philipp Oeser commented

2019-01-09 15:34:17 +01:00

In #57457#549721, @fclem wrote:
Well I hoped something like that would work:

diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c
index e9d874bd1ee..2cf3494802d 100644
--- a/source/blender/draw/intern/draw_manager_data.c
+++ b/source/blender/draw/intern/draw_manager_data.c
@@ -40,6 +40,8 @@
 #include "BLI_link_utils.h"
 #include "BLI_mempool.h"
 
+#include "DEG_depsgraph_query.h"
+
 #include "intern/gpu_codegen.h"
 
 struct GPUVertFormat *g_pos_format = NULL;
@@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct
 			GPUTexture *tex = NULL;
 
 			if (input->ima) {
-				double time = 0.0; /* TODO make time variable */
+				double time = DEG_get_ctime(DST.draw_ctx.depsgraph);
 				tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time);
 			}
 			else {

But GPU_texture_from_blender does not do anything with time...

Also had a quick look and as a starting point it seems GPUInput input->iuser Image User was always NULL. [without the image user you dont have access to framnumber etc...]
I tried to fix this and building upon what @fclem tried I get something that updates movies [sequences also -- but only if the image node has a keyframe, that's another issue to solve...] with flickering. [eh, another issue to solve]

Thought I should drop this here so it is not lost: P888: #57457 snippet



diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c
index 6584b6953d5..615adeb61f1 100644
--- a/source/blender/draw/intern/draw_manager_data.c
+++ b/source/blender/draw/intern/draw_manager_data.c
@@ -40,6 +40,8 @@
 #include "BLI_link_utils.h"
 #include "BLI_mempool.h"
 
+#include "DEG_depsgraph_query.h"
+
 #include "intern/gpu_codegen.h"
 
 struct GPUVertFormat *g_pos_format = NULL;
@@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct
 			GPUTexture *tex = NULL;
 
 			if (input->ima) {
-				double time = 0.0; /* TODO make time variable */
+				double time = DEG_get_ctime(DST.draw_ctx.depsgraph);
 				tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time);
 			}
 			else {
diff --git a/source/blender/gpu/intern/gpu_draw.c b/source/blender/gpu/intern/gpu_draw.c
index 6f939261729..a6fd71585e6 100644
--- a/source/blender/gpu/intern/gpu_draw.c
+++ b/source/blender/gpu/intern/gpu_draw.c
@@ -285,7 +285,7 @@ GPUTexture *GPU_texture_from_blender(
         ImageUser *iuser,
         int textarget,
         bool is_data,
-        double UNUSED(time))
+        double time)
 {
 	if (ima == NULL) {
 		return NULL;
@@ -293,9 +293,11 @@ GPUTexture *GPU_texture_from_blender(
 
 	/* Test if we already have a texture. */
 	GPUTexture **tex = gpu_get_image_gputexture(ima, textarget);
+	/*
 	if (*tex) {
 		return *tex;
 	}
+	*/
 
 	/* Check if we have a valid image. If not, we return a dummy
 	 * texture with zero bindcode so we don't keep trying. */
@@ -312,6 +314,7 @@ GPUTexture *GPU_texture_from_blender(
 	}
 
 	/* check if we have a valid image buffer */
+	BKE_image_user_frame_calc(iuser, (int)time);
 	ImBuf *ibuf = BKE_image_acquire_ibuf(ima, iuser, NULL);
 	if (ibuf == NULL) {
 		*tex = GPU_texture_from_bindcode(textarget, bindcode);
diff --git a/source/blender/nodes/shader/nodes/node_shader_tex_image.c b/source/blender/nodes/shader/nodes/node_shader_tex_image.c
index 524f7a5c8e2..c13a1064794 100644
--- a/source/blender/nodes/shader/nodes/node_shader_tex_image.c
+++ b/source/blender/nodes/shader/nodes/node_shader_tex_image.c
@@ -75,8 +75,8 @@ static int node_shader_gpu_tex_image(GPUMaterial *mat, bNode *node, bNodeExecDat
 	};
 
 	Image *ima = (Image *)node->id;
-	ImageUser *iuser = NULL;
 	NodeTexImage *tex = node->storage;
+	ImageUser *iuser = &tex->iuser;
 	const char *gpu_node_name = (tex->projection == SHD_PROJ_BOX)
 	                             ? names_box[tex->interpolation]
 	                             : names[tex->interpolation];

maybe we should get @brecht and @Sergey on board?

> In #57457#549721, @fclem wrote: > Well I hoped something like that would work: > > ``` > diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c > index e9d874bd1ee..2cf3494802d 100644 > --- a/source/blender/draw/intern/draw_manager_data.c > +++ b/source/blender/draw/intern/draw_manager_data.c > @@ -40,6 +40,8 @@ > #include "BLI_link_utils.h" > #include "BLI_mempool.h" > > +#include "DEG_depsgraph_query.h" > + > #include "intern/gpu_codegen.h" > > struct GPUVertFormat *g_pos_format = NULL; > @@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct > GPUTexture *tex = NULL; > > if (input->ima) { > - double time = 0.0; /* TODO make time variable */ > + double time = DEG_get_ctime(DST.draw_ctx.depsgraph); > tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time); > } > else { > > ``` > > But GPU_texture_from_blender does not do anything with `time`... Also had a quick look and as a starting point it seems GPUInput `input->iuser` Image User was always NULL. [without the image user you dont have access to framnumber etc...] I tried to fix this and building upon what @fclem tried I get something that updates movies [sequences also -- but only if the image node has a keyframe, that's another issue to solve...] with flickering. [eh, another issue to solve] Thought I should drop this here so it is not lost: [P888: #57457 snippet](https://archive.blender.org/developer/P888.txt) ``` diff --git a/source/blender/draw/intern/draw_manager_data.c b/source/blender/draw/intern/draw_manager_data.c index 6584b6953d5..615adeb61f1 100644 --- a/source/blender/draw/intern/draw_manager_data.c +++ b/source/blender/draw/intern/draw_manager_data.c @@ -40,6 +40,8 @@ #include "BLI_link_utils.h" #include "BLI_mempool.h" +#include "DEG_depsgraph_query.h" + #include "intern/gpu_codegen.h" struct GPUVertFormat *g_pos_format = NULL; @@ -802,7 +804,7 @@ static DRWShadingGroup *drw_shgroup_material_inputs(DRWShadingGroup *grp, struct GPUTexture *tex = NULL; if (input->ima) { - double time = 0.0; /* TODO make time variable */ + double time = DEG_get_ctime(DST.draw_ctx.depsgraph); tex = GPU_texture_from_blender(input->ima, input->iuser, GL_TEXTURE_2D, input->image_isdata, time); } else { diff --git a/source/blender/gpu/intern/gpu_draw.c b/source/blender/gpu/intern/gpu_draw.c index 6f939261729..a6fd71585e6 100644 --- a/source/blender/gpu/intern/gpu_draw.c +++ b/source/blender/gpu/intern/gpu_draw.c @@ -285,7 +285,7 @@ GPUTexture *GPU_texture_from_blender( ImageUser *iuser, int textarget, bool is_data, - double UNUSED(time)) + double time) { if (ima == NULL) { return NULL; @@ -293,9 +293,11 @@ GPUTexture *GPU_texture_from_blender( /* Test if we already have a texture. */ GPUTexture **tex = gpu_get_image_gputexture(ima, textarget); + /* if (*tex) { return *tex; } + */ /* Check if we have a valid image. If not, we return a dummy * texture with zero bindcode so we don't keep trying. */ @@ -312,6 +314,7 @@ GPUTexture *GPU_texture_from_blender( } /* check if we have a valid image buffer */ + BKE_image_user_frame_calc(iuser, (int)time); ImBuf *ibuf = BKE_image_acquire_ibuf(ima, iuser, NULL); if (ibuf == NULL) { *tex = GPU_texture_from_bindcode(textarget, bindcode); diff --git a/source/blender/nodes/shader/nodes/node_shader_tex_image.c b/source/blender/nodes/shader/nodes/node_shader_tex_image.c index 524f7a5c8e2..c13a1064794 100644 --- a/source/blender/nodes/shader/nodes/node_shader_tex_image.c +++ b/source/blender/nodes/shader/nodes/node_shader_tex_image.c @@ -75,8 +75,8 @@ static int node_shader_gpu_tex_image(GPUMaterial *mat, bNode *node, bNodeExecDat }; Image *ima = (Image *)node->id; - ImageUser *iuser = NULL; NodeTexImage *tex = node->storage; + ImageUser *iuser = &tex->iuser; const char *gpu_node_name = (tex->projection == SHD_PROJ_BOX) ? names_box[tex->interpolation] : names[tex->interpolation]; ``` maybe we should get @brecht and @Sergey on board?

Philipp Oeser commented

2019-01-11 09:56:43 +01:00

Added subscriber: @Ekiwnox

Philipp Oeser commented

2019-01-11 10:07:00 +01:00

@brecht, @Sergey: not sure whom to assign this to? (I could spend more time investigating, but maybe it is obvious to one of you?)

btw. we have this working (refreshing sequences and movies) in camera background images, see view3d_draw_bgpic, but implementation is different/separate from GPU_texture_from_blender in that it does the whole drawing [not just the texture refresh...]

@brecht, @Sergey: not sure whom to assign this to? (I could spend more time investigating, but maybe it is obvious to one of you?) btw. we have this working (refreshing sequences and movies) in camera background images, see `view3d_draw_bgpic`, but implementation is different/separate from `GPU_texture_from_blender` in that it does the whole drawing [not just the texture refresh...]

Brecht Van Lommel self-assigned this 2019-01-11 11:14:40 +01:00

Brecht Van Lommel commented

2019-01-14 03:59:53 +01:00

Added subscribers: @AJ-200, @ideasman42, @mont29

Brecht Van Lommel commented

2019-01-14 04:33:08 +01:00

Marking as high priority since this gets reported often.

This is a rather complicated issue caused mainly by copy-on-write changes. Previously on each frame change Blender would loop over (most) image users, recalculate the frame number and free the GPU texture if needed.

It did not do this for Cycles/Eevee image texture nodes in materials, only BI materials. That is easily solved, though for best playback performance it could be done in a smarter way than before.

The main issue however is copy-on-write. Both the original and COW datablocks need to be updated. This could be done as part of the depsgraph now for image users that are in the depsgraph, marking such materials or objects as depending on time.

Refreshing the GPU texture is problematic as well. Currently each image datablock stores and owns a single GPU texture at a single frame. However it is now possible to have multiple depsgraphs each at their own time. A proper solution to this likely means moving ownership of the GPU texture from the image to the image user or depsgraph, or having some kind of caching system.

Marking as high priority since this gets reported often. This is a rather complicated issue caused mainly by copy-on-write changes. Previously on each frame change Blender would loop over (most) image users, recalculate the frame number and free the GPU texture if needed. It did not do this for Cycles/Eevee image texture nodes in materials, only BI materials. That is easily solved, though for best playback performance it could be done in a smarter way than before. The main issue however is copy-on-write. Both the original and COW datablocks need to be updated. This could be done as part of the depsgraph now for image users that are in the depsgraph, marking such materials or objects as depending on time. Refreshing the GPU texture is problematic as well. Currently each image datablock stores and owns a single GPU texture at a single frame. However it is now possible to have multiple depsgraphs each at their own time. A proper solution to this likely means moving ownership of the GPU texture from the image to the image user or depsgraph, or having some kind of caching system.

Brecht Van Lommel commented

2019-01-19 11:04:27 +01:00

Added subscriber: @Pastel

Per Hansen commented

2019-01-20 12:51:45 +01:00

Added subscriber: @PerKofodHansen

Philipp Oeser commented

2019-01-21 20:28:52 +01:00

Added subscriber: @CyberLuden

Philipp Oeser commented

2019-01-22 11:03:08 +01:00

Added subscribers: @ChristopherCarroll, @WilliamReynish

pistol ioan commented

2019-01-22 21:09:06 +01:00

Hey,

Some news about this?

Hey, Some news about this?

(Deleted) commented

2019-01-24 13:10:59 +01:00

(Migrated from localhost:3001)

Added subscriber: @(Deleted)

Daniel Craven commented

2019-01-24 21:44:26 +01:00

Added subscriber: @OcularSorcerer

Daniel Craven commented

2019-01-24 21:44:26 +01:00

In #57457#595671, @MikeFutcher wrote:
And for some even more bazaar reason - it won't go past frame 97. I guess it's a memory problem? Tried the same scene with a few different videos in the same scene so far... but I might make this reporting bugs on a script rather than Blender if I'm not careful. I guess I'll be putting my greenscreen nodegroup for material nodes on hold.

I just discovered that if you toggle the sidebar (N) in the image editor, it gives you options to change the amount of frames to use in a movie/image sequence. This seems to be unaffected by the settings on the image texture node.

Still trying to figure out how to use more than one image sequence texture....any solutions?

> In #57457#595671, @MikeFutcher wrote: > And for some even more bazaar reason - it won't go past frame 97. I guess it's a memory problem? Tried the same scene with a few different videos in the same scene so far... but I might make this reporting bugs on a script rather than Blender if I'm not careful. I guess I'll be putting my greenscreen nodegroup for material nodes on hold. I just discovered that if you toggle the sidebar (N) in the image editor, it gives you options to change the amount of frames to use in a movie/image sequence. This seems to be unaffected by the settings on the image texture node. Still trying to figure out how to use more than one image sequence texture....any solutions?

Vladimir commented

2019-01-24 22:11:44 +01:00

@OcularSorcerer , Yep.
The working variant for several objects with video textures is to open several working windows with image editors and in each of them open different textures:

@OcularSorcerer , Yep. The working variant for several objects with video textures is to open several working windows with image editors and in each of them open different textures: ![Bag_2.8_Video.jpg](https://archive.blender.org/developer/F6393088/Bag_2.8_Video.jpg)

Brecht Van Lommel commented

2019-01-25 22:14:49 +01:00

Added subscriber: @iSpeedy

Dylan Neill commented

2019-01-26 03:48:09 +01:00

Added subscriber: @semimetallic-1

Mike Futcher commented

2019-01-26 08:35:46 +01:00

Daniel Craven (Craven) - thankyou! I will be putting a tutorial together on this in the next week.

pistol ioan commented

2019-01-28 17:06:34 +01:00

Removed subscriber: @istoltoto

Fran Alburquerque commented

2019-01-29 13:56:45 +01:00

Added subscriber: @FranAlburquerque

Fran Alburquerque commented

2019-01-29 13:56:45 +01:00

Same problem here in two scenarios:

Image sequence textures under Eevee
Image Empties using a video with autorefresh (the usual way) in viewport, no matter which render engine is set

Same problem here in two scenarios: - Image sequence textures under Eevee - Image Empties using a video with autorefresh (the usual way) in viewport, no matter which render engine is set

Albert commented

2019-02-01 10:46:40 +01:00

When will the bug get fixed?

Vladimir commented

2019-02-01 13:37:42 +01:00

@lichtwerk , i try to compile blender (da1da3053d) with your solution, but your variant don't give needed result (black material with video texture and pink - with sequences).
Working variant with this code in node_shader_tex_image.c :

	Image *ima = (Image *)node->id;
	ImageUser *iuser = NULL;
	NodeTexImage *tex = node->storage;
	//ImageUser *iuser = &tex->iuser;

That give expected result (video and sequences update in viewport but render - sequences is flickering), but only when object is selected and active.

@lichtwerk , i try to compile blender (da1da3053d75) with your solution, but your variant don't give needed result (black material with video texture and pink - with sequences). Working variant with this code in **node_shader_tex_image.c** : ``` Image *ima = (Image *)node->id; ImageUser *iuser = NULL; NodeTexImage *tex = node->storage; //ImageUser *iuser = &tex->iuser; ``` That give expected result (video and sequences update in viewport but render - sequences is flickering), but only when object is selected and active.

riidom commented

2019-02-04 20:20:39 +01:00

Added subscriber: @DominikR

Vladimir commented

2019-02-05 13:26:32 +01:00

Someone can help with it? I don't understand some strings:
in all BKE_image update/check frame/etc uses cfra as integer.

But in GPU_texture_from_blender used time in double.

Ofcourse, in sequences/video textures logically to use integer (as frames). So, why using double?

Someone can help with it? I don't understand some strings: in all **BKE_image update/check frame**/etc uses **cfra** as ***integer***. But in **GPU_texture_from_blender** used **time** in ***double***. Ofcourse, in sequences/video textures logically to use *integer* (as frames). So, why using *double*?

Vincent Sautter commented

2019-02-06 22:24:56 +01:00

Added subscriber: @darylsautter

David Gladstein commented

2019-02-07 00:35:05 +01:00

Added subscriber: @DavidGladstein

Bent Hillerkus commented

2019-02-07 15:14:29 +01:00

Added subscriber: @bent

pistol ioan commented

2019-02-07 21:19:44 +01:00

This comment was removed by @istoltoto

*This comment was removed by @istoltoto*

ML commented

2019-02-07 22:09:00 +01:00

I would like to send some resources for this problem particularly to speed the process, is it possible?

Vladimir commented

2019-02-07 22:15:27 +01:00

In #57457#615643, @MarcelLegindi wrote:
I would like to send some resources for this problem particularly to speed the process, is it possible?

I support. Ready to transfer money for a speedy solution to the problem. Where to transfer?

> In #57457#615643, @MarcelLegindi wrote: > I would like to send some resources for this problem particularly to speed the process, is it possible? I support. Ready to transfer money for a speedy solution to the problem. Where to transfer?

Brecht Van Lommel commented

2019-02-07 22:21:27 +01:00

It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8.

Daniel Salazar commented

2019-02-07 22:24:28 +01:00

In #57457#615645, @brecht wrote:
It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8.

Thanks for the heads up @brecht

> In #57457#615645, @brecht wrote: > It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8. Thanks for the heads up @brecht

M Hoffmann commented

2019-02-08 22:20:12 +01:00

Added subscriber: @mhoff

Gigi Botta commented

2019-02-09 18:21:07 +01:00

In #57457#615645, @brecht wrote:
It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8.

Thank you @brecht I'm broadcast tv director. We are designing a tv show with a real time dynamic CGenerated scenography. Because of Eevee Blender can be ideal for that. But the real time movie clip elements insertion\playback is obviously crucial. We need a lot of video contribution in scenography. Have you an idea of how much time will take the fix? Thank you so much.

> In #57457#615645, @brecht wrote: > It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8. Thank you @brecht I'm broadcast tv director. We are designing a tv show with a real time dynamic CGenerated scenography. Because of Eevee Blender can be ideal for that. But the real time movie clip elements insertion\playback is obviously crucial. We need a lot of video contribution in scenography. Have you an idea of how much time will take the fix? Thank you so much.

Mark D Allen commented

2019-02-13 17:55:53 +01:00

Added subscriber: @Allucinari

Yanis commented

2019-02-15 22:05:26 +01:00

Added subscriber: @Yanis

blender-admin commented

2019-02-18 13:23:49 +01:00

This issue was referenced by 0e3a2acbfa

This issue was referenced by 0e3a2acbfa6998b3a1ec967f3c25f7e12e0cf8fb

Phil Manzano commented

2019-02-18 13:32:44 +01:00

Added subscriber: @pm

Thomas Volkmann commented

2019-02-18 13:53:22 +01:00

Added subscriber: @knekke

Thomas Volkmann commented

2019-02-18 13:53:22 +01:00

Also very interested in this!!

As another workaround:

import bpy

def my_handler(scene):
    print("Frame Change", scene.frame_current)
    bpy.data.images['YOUR_IMAGESEQENCE.0001.png'].reload()

bpy.app.handlers.frame_change_pre.append(my_handler)

Now you can scrub the timeline and see the changes.

Also very interested in this!! As another workaround: ``` import bpy def my_handler(scene): print("Frame Change", scene.frame_current) bpy.data.images['YOUR_IMAGESEQENCE.0001.png'].reload() bpy.app.handlers.frame_change_pre.append(my_handler) ``` Now you can scrub the timeline and see the changes.

Thomas Volkmann commented

2019-02-18 14:40:32 +01:00

ah, well...nevermind... workaround has been posted before

Thomas Volkmann commented

2019-02-18 15:05:42 +01:00

In #57457#615644, @VladimirKunyansky wrote:

In #57457#615643, @MarcelLegindi wrote:
I would like to send some resources for this problem particularly to speed the process, is it possible?

I support. Ready to transfer money for a speedy solution to the problem. Where to transfer?

+1

> In #57457#615644, @VladimirKunyansky wrote: >> In #57457#615643, @MarcelLegindi wrote: >> I would like to send some resources for this problem particularly to speed the process, is it possible? > > I support. Ready to transfer money for a speedy solution to the problem. Where to transfer? +1

pistol ioan commented

2019-02-18 15:35:42 +01:00

I can donate $ 40.

ML commented

2019-02-18 15:44:24 +01:00

In #57457#615645, @brecht wrote:
It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8.

... so, for this problem I think 1000$ is not enough.

> In #57457#615645, @brecht wrote: > It's being worked on, just requires some deep changes to the dependency graph and GPU image loading code to work properly in 2.8. ... so, for this problem I think 1000$ is not enough.

Sebastian Parborg commented

2019-02-18 16:14:43 +01:00

Added subscriber: @StickMeister125

Brecht Van Lommel commented

2019-02-18 16:53:25 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-02-18 16:53:25 +01:00

pistol ioan commented

2019-02-18 17:00:34 +01:00

Thank goodness!
Thank you Brecht Van Lommel ???

You were always my hero, right after you created Cycles!
I knew you could do it!

Thank goodness! Thank you Brecht Van Lommel ??? You were always my hero, right after you created Cycles! I knew you could do it!

Vladimir commented

2019-02-18 18:29:42 +01:00

@brecht , I do not refuse my words, please tell me where to transfer money?

Thank you so much!

@brecht , I do not refuse my words, please tell me where to transfer money? Thank you so much!

Brecht Van Lommel commented

2019-02-18 18:39:18 +01:00

@VladimirKunyansky: anyone is welcome to contribute to the development fund, this bugfix was funded by it.
https://fund.blender.org/

@VladimirKunyansky: anyone is welcome to contribute to the development fund, this bugfix was funded by it. https://fund.blender.org/

Vladimir commented

2019-02-18 19:36:07 +01:00

@brecht , I wanted to thank You personally, but the support of the whole team is also important. Thank you very much for the work!

Daniel Salazar commented

2019-02-18 20:53:17 +01:00

If you're not already subscribed to https://fund.blender.org/ go do it now! You can start as low as $6 a month :)

Thanks @brecht !

If you're not already subscribed to https://fund.blender.org/ go do it now! You can start as low as $6 a month :) Thanks @brecht !

Per Hansen commented

2019-02-18 21:30:14 +01:00

Thanks so much Blender team - you are the most awesome people ! - I am so gratefull for the work you do! This fix was really important to me as well :)

Deen commented

2019-02-19 03:23:34 +01:00

Removed subscriber: @De3n

ML commented

2019-02-24 21:52:30 +01:00

Is it functional in 2.8 - 6bab905c9d ? If so, it is only working with open node editor and active texture node - with properties. Is that right?

Is it functional in 2.8 - 6bab905c9d40 ? If so, it is only working with open node editor and active texture node - with properties. Is that right?

Daniel Salazar commented

2019-02-25 05:51:10 +01:00

@MarcelLegindi Download latest build from https://builder.blender.org/download/ it should work out of trthe box. Remember to set the frame range correctly in the node

ML commented

2019-02-25 10:29:57 +01:00

Added subscriber: @daniel-34

ML commented

2019-02-25 10:29:57 +01:00

@daniel-34 Salazar (zanqdo) Downloaded last build as before, but now is the 893fa59831. But not working - blend file inside. And technique what I using is there: https://blender.stackexchange.com/questions/124813/image-texture-node-image-sequence-control-by-slider

It is working only with open node editor and active texture node. Without it is not functional. I used this technique for automate rigging puppet phases - hands, eyes, mouth etc.

image_sequence_02.blend

@daniel-34 Salazar (zanqdo) Downloaded last build as before, but now is the 893fa598319e. But not working - blend file inside. And technique what I using is there: https://blender.stackexchange.com/questions/124813/image-texture-node-image-sequence-control-by-slider It is working only with open node editor and active texture node. Without it is not functional. I used this technique for automate rigging puppet phases - hands, eyes, mouth etc. [image_sequence_02.blend](https://archive.blender.org/developer/F6710692/image_sequence_02.blend)

Thomas Volkmann commented

2019-02-25 11:40:08 +01:00

I also have some troubles when doing opengl previews. I have a batchscript that starts Blender, replaces the background sequence, renders a opengl preview (because 10x faster than regular evee rendering) from different cameras and quit.
The backgroundsequences can either be png-seqences or mp4 files and the script does the switching and setting offsets. But the rendering is very unreliable and often I end up with only 3 animated frames and then a freeze, or the background is not moving at all. When I open up the scene everything looks fine in the viewport and scrubbing the timeline works. I couldn't detect a pattern yet.

I also have some troubles when doing opengl previews. I have a batchscript that starts Blender, replaces the background sequence, renders a opengl preview (because 10x faster than regular evee rendering) from different cameras and quit. The backgroundsequences can either be png-seqences or mp4 files and the script does the switching and setting offsets. But the rendering is very unreliable and often I end up with only 3 animated frames and then a freeze, or the background is not moving at all. When I open up the scene everything looks fine in the viewport and scrubbing the timeline works. I couldn't detect a pattern yet.

Brecht Van Lommel commented

2019-02-25 13:00:18 +01:00

If there are further specific issues with image sequences, please create new bug reports.

ML commented

2019-02-25 13:25:32 +01:00

But it is same problem as before ... If we created new report we will wait for enough people with same problem then it will be in progress, so it may be long time story.

(Deleted) commented

2019-02-25 13:44:13 +01:00

(Migrated from localhost:3001)

This comment was removed by @(Deleted)

*This comment was removed by @(Deleted)*

Brecht Van Lommel commented

2019-02-25 13:56:58 +01:00

Please do create new bug report, this is working for many cases so if there is a bug it's related to some specific setup. And for that it is best to have an own report with .blend and clear steps to redo. It also means we don't send mails to 50+ people subscribed to this task for a bug that is not relevant to them.

Daniel Salazar commented

2019-02-26 01:48:47 +01:00

In #57457#626977, @MarcelLegindi wrote:
@daniel-34 Salazar (zanqdo) Downloaded last build as before, but now is the 893fa59831. But not working - blend file inside. And technique what I using is there: https://blender.stackexchange.com/questions/124813/image-texture-node-image-sequence-control-by-slider

It is working only with open node editor and active texture node. Without it is not functional. I used this technique for automate rigging puppet phases - hands, eyes, mouth etc.

image_sequence_02.blend

You need to enable the Autorefresh option in the node

> In #57457#626977, @MarcelLegindi wrote: > @daniel-34 Salazar (zanqdo) Downloaded last build as before, but now is the 893fa598319e. But not working - blend file inside. And technique what I using is there: https://blender.stackexchange.com/questions/124813/image-texture-node-image-sequence-control-by-slider > > It is working only with open node editor and active texture node. Without it is not functional. I used this technique for automate rigging puppet phases - hands, eyes, mouth etc. > > [image_sequence_02.blend](https://archive.blender.org/developer/F6710692/image_sequence_02.blend) You need to enable the Autorefresh option in the node

ML commented

2019-02-26 10:37:42 +01:00

No no, it’s not working with enable autorefresh neither withou it.

Per Hansen commented

2019-02-26 10:38:56 +01:00

Removed subscriber: @PerKofodHansen

Gigi Botta commented

2019-02-26 11:41:16 +01:00

Its work but there is still a little bug on autorefresh command. (on my system) Justreassign material you are working on to object in the shader editor when you finish your node assigning video texture etc (remember to set total frame number, activate cyclic and auto refresh) hit play and movie or image sequence work perfectly. If not video remain stopped to first frame. I noted with pleasure same video shader/material is shareable over undefined object number.

Its work but there is still a little bug on autorefresh command. (on my system) Just**reassign** material you are working on to object in the shader editor when you finish your node assigning video texture etc (remember to set total frame number, activate cyclic and auto refresh) hit play and movie or image sequence work perfectly. If not video remain stopped to first frame. I noted with pleasure same video shader/material is shareable over undefined object number.

Daniel Salazar commented

2019-02-26 18:47:29 +01:00

In #57457#627850, @MarcelLegindi wrote:
No no, it’s not working with enable autorefresh neither withou it.

Your scene is set to cycles, this is supposed to be a feature for eevee :s

> In #57457#627850, @MarcelLegindi wrote: > No no, it’s not working with enable autorefresh neither withou it. Your scene is set to cycles, this is supposed to be a feature for eevee :s

ML commented

2019-02-26 18:59:18 +01:00

@daniel-34 Salazar (zanqdo) and did you try it in eevee ?

I am sorry guys, but this my example is not functional on win 7, win 10, cycles or eevee its some kind of system problem, I don't know where exactly it is. I was looking forward to working with puppets, you know ... I am only sad nothing else. From my perspective its one big problem, very difficult problem, but the solution is on half way and I don't know how can I help, because I would like to help of course.

@daniel-34 Salazar (zanqdo) and did you try it in eevee ? I am sorry guys, but this my example is not functional on win 7, win 10, cycles or eevee its some kind of system problem, I don't know where exactly it is. I was looking forward to working with puppets, you know ... I am only sad nothing else. From my perspective its one big problem, very difficult problem, but the solution is on half way and I don't know how can I help, because I would like to help of course.

Daniel Salazar commented

2019-02-26 19:16:53 +01:00

In #57457#628282, @MarcelLegindi wrote:
@daniel-34 Salazar (zanqdo) and did you try it in eevee ?

I am sorry guys, but this my example is not functional on win 7, win 10, cycles or eevee its some kind of system problem, I don't know where exactly it is. I was looking forward to working with puppets, you know ... I am only sad nothing else. From my perspective its one big problem, very difficult problem, but the solution is on half way and I don't know how can I help, because I would like to help of course.

Why do you have that driver setup in the offset?

> In #57457#628282, @MarcelLegindi wrote: > @daniel-34 Salazar (zanqdo) and did you try it in eevee ? > > I am sorry guys, but this my example is not functional on win 7, win 10, cycles or eevee its some kind of system problem, I don't know where exactly it is. I was looking forward to working with puppets, you know ... I am only sad nothing else. From my perspective its one big problem, very difficult problem, but the solution is on half way and I don't know how can I help, because I would like to help of course. Why do you have that driver setup in the offset?

Brecht Van Lommel commented

2019-02-26 19:40:29 +01:00

There's already a separate bug report for @MarcelLegindi's case: #61937 (Image sequence offset driver has no effect without node editor)

It's been confirmed and will be worked on, no need to discuss it here.

There's already a separate bug report for @MarcelLegindi's case: #61937 (Image sequence offset driver has no effect without node editor) It's been confirmed and will be worked on, no need to discuss it here.

Sign in to join this conversation.