Auto refresh on movie files does not work on frame change (Cycles) #48399

Closed
opened 2016-05-10 21:07:40 +02:00 by Thomas Beck · 10 comments
Member

System Information
Ubuntu 64, 16GbRam, 2*Gtx560 ti oc 2GB

Blender Version
Broken: Every single version I tried up until the last master a18f4d2
Worked: never

Short description of error
I load a movie onto a plane and activate "Auto Refresh". On frame changes the current movie frame should be updated in Cycles "material" mode but it doesn't.

Exact steps for others to reproduce the error
Download this MovieRefresh.blend file and this Suzanne.avi movie file and place them together in a directory. Then load the blend file and change a frame. This should refresh the image texture but it does not.

Background information
I need that feature mostly for compositing 2D imagery in the 3D space. Formerly we used AE for such things, but we try to omit that completely this time. I read that in the Wiki as a Todo "Image Sequence & Movie texture is not being updated on frame advance (using textured solid and multitexture textured shading modes, in 3d window). GLSL materials do update." but as it is about GLSL materials not updating I strongly believe that this is a bug. In BI (when GLSL is turned on) this is basically working (most of the time)

@Sergey I added you because I hope that it's dependency issue and nothing worse...

Best regards,

Thomas

**System Information** Ubuntu 64, 16GbRam, 2*Gtx560 ti oc 2GB **Blender Version** Broken: Every single version I tried up until the last master a18f4d2 Worked: never **Short description of error** I load a movie onto a plane and activate "Auto Refresh". On frame changes the current movie frame should be updated in Cycles "material" mode but it doesn't. **Exact steps for others to reproduce the error** Download this [MovieRefresh.blend](https://archive.blender.org/developer/F310029/MovieRefresh.blend) file and this [Suzanne.avi](https://archive.blender.org/developer/F310030/Suzanne.avi) movie file and place them together in a directory. Then load the blend file and change a frame. This should refresh the image texture but it does not. **Background information** I need that feature mostly for compositing 2D imagery in the 3D space. Formerly we used AE for such things, but we try to omit that completely this time. I read that in the Wiki as a Todo "Image Sequence & Movie texture is not being updated on frame advance (using textured solid and multitexture textured shading modes, in 3d window). GLSL materials do update." but as it is about GLSL materials not updating I strongly believe that this is a bug. In BI (when GLSL is turned on) this is basically working (most of the time) @Sergey I added you because I hope that it's dependency issue and nothing worse... Best regards, Thomas
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Sergey Sharybin was assigned by Thomas Beck 2016-05-10 21:07:40 +02:00
Author
Member

Added subscribers: @plasmasolutions, @Sergey

Added subscribers: @plasmasolutions, @Sergey

Added subscriber: @cheleb

Added subscriber: @cheleb

Hi Thomas,
sadly, this is a Duplicate of #48355

However, there is a workaround. Cycles image nodes only update in the viewport if you have an open properties panel of that node in an node editor window and property panels are enabled for frame updates the timeline's playback menu.

To make it work:

  • open a node editor window with the material containing the image node
  • make sure the image node is active
  • open the properties panel of the node editor
  • make sure the properties section is unfolded

activate "Property Editors" in the "Playback" manu of the timeline editor

or

just open the modified version of your scene here -> MovieRefresh2.blend

Press play, have fun! :)

Hi Thomas, sadly, this is a Duplicate of #48355 However, there is a workaround. Cycles image nodes only update in the viewport if you have an **open properties panel** of that node **in an node editor window** and **property panels are enabled for frame updates** the timeline's playback menu. **To make it work:** - open a node editor window with the material containing the image node - make sure the image node is active - open the properties panel of the node editor - make sure the properties section is unfolded # activate "Property Editors" in the "Playback" manu of the timeline editor **or** just open the modified version of your scene here -> [MovieRefresh2.blend](https://archive.blender.org/developer/F310033/MovieRefresh2.blend) Press play, have fun! :)
Author
Member

Hi Ralf,

thanks for making me aware of the dup - I even searched for exactly those keywords and didn't found the report :(
Unfortunately the situation does not look brighter with your work around (which is very appreciated though): the problem persists if we got two and more movies in the viewport - and that is exactly what's happening when you're compositing elements in 3d :(

Cheers, maybe @Sergey knows a nice hack how to enable it before 2.8 still...

Hi Ralf, thanks for making me aware of the dup - I even searched for exactly those keywords and didn't found the report :( Unfortunately the situation does not look brighter with your work around (which is very appreciated though): the problem persists if we got two and more movies in the viewport - and that is exactly what's happening when you're compositing elements in 3d :( Cheers, maybe @Sergey knows a nice hack how to enable it before 2.8 still...
Member

Added subscriber: @Blendify

Added subscriber: @Blendify

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

It's not really a dependency problem. The way viewport operates with textures requires having ImageUser (which defines how the image is used, frame of the image and so). It exists for Blender Internal textures, but not for the Image Texture nodes. So viewport can't really know what to display.

Was trying to solve this in the past, but it's a can of worms. Wouldn't hack it in and rather see how we can re-think that system.

It's not really a dependency problem. The way viewport operates with textures requires having ImageUser (which defines how the image is used, frame of the image and so). It exists for Blender Internal textures, but not for the Image Texture nodes. So viewport can't really know what to display. Was trying to solve this in the past, but it's a can of worms. Wouldn't hack it in and rather see how we can re-think that system.

Added subscriber: @Alexandermitchell

Added subscriber: @Alexandermitchell

I have stumbled onto this bug when wanting to use Blender for compositing multiple video textures. As @plasmasolutions mentioned, activating "Property Editors" and keeping the node view open only allows one texture to be viewable at a time.

Is there a timeline (awareness) for this to get fixed in 2.8, or any updates post 2.78a?

UPDATE: The only hack I was able to workout was to use a pinned NodeTree in order to open up multiple Node Editors, (one per object texture with its Properties open). But obviously this would get very messy very fast when using many compositing video / image sequence textures.

I have stumbled onto this bug when wanting to use Blender for compositing multiple video textures. As @plasmasolutions mentioned, activating "Property Editors" and keeping the node view open only allows one texture to be viewable at a time. Is there a timeline (awareness) for this to get fixed in 2.8, or any updates post 2.78a? UPDATE: The only hack I was able to workout was to use a pinned NodeTree in order to open up multiple Node Editors, (one per object texture with its Properties open). But obviously this would get very messy very fast when using many compositing video / image sequence textures.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#48399
No description provided.