Image Texture Node misbehaving #51989

Closed
opened 2017-07-07 13:46:59 +02:00 by Roel Koster · 8 comments
Member

System Information
OSX Latest

Blender Version
Broken: (2.78a and up)
Worked: (partly) 2.77 !!

Short description of error
Image Texture loading (cycles/internal) does not calculate number of frames when loading and sets a strange offset number

Exact steps for others to reproduce the error
Factory Defaults
Set render engine to Cycles
Go to material tab
Select USE NODES
go to node editor
add an Image Texture node
open a movie
observe strange offset calculation and number of frames not getting updated

(Blender Internal texture has the same issues (guess it's the same code)

When observing this behaviour I wondered when things got messed up and tried several older blender versions from 2.76 uptil now.
It seems that in older versions there was a slightly different behaviour (the offset stayed at 0)
But I noticed when adding an Image Texture node in the material tab did not get frame number updated, while adding a Texture node via the node editor it would!
It could very well be that trying to fix that back then, the new bug got introduced.

Hope you can reproduce it too.
Regards,
Roel

**System Information** OSX Latest **Blender Version** Broken: (2.78a and up) Worked: (partly) 2.77 !! **Short description of error** Image Texture loading (cycles/internal) does not calculate number of frames when loading and sets a strange offset number **Exact steps for others to reproduce the error** Factory Defaults Set render engine to Cycles Go to material tab Select USE NODES go to node editor add an Image Texture node open a movie observe strange offset calculation and number of frames not getting updated (Blender Internal texture has the same issues (guess it's the same code) When observing this behaviour I wondered when things got messed up and tried several older blender versions from 2.76 uptil now. It seems that in older versions there was a slightly different behaviour (the offset stayed at 0) But I noticed when adding an Image Texture node in the material tab did not get frame number updated, while adding a Texture node via the node editor it would! It could very well be that trying to fix that back then, the new bug got introduced. Hope you can reproduce it too. Regards, Roel
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @kostex

Added subscriber: @kostex
Author
Member

Silly me..

It seems that the filename is causing the 'offset'. If there are numbers in the filename, this gets treated as offset value..

The determination of number of frames is still an issue. (For now ;-)

Silly me.. It seems that the filename is causing the 'offset'. If there are numbers in the filename, this gets treated as offset value.. The determination of number of frames is still an issue. (For now ;-)
Author
Member

Searched like crazy to pinpoint where it goes wrong.
My findings are that everything is calculated fine from the movie file (anim_movie.c->IMB_anim_get_duration)
and it shows correctly throughout blender interface and even when querying the loaded movie in console:
bpy.data.images- [x].frame_duration returns the correct number
Only the node itself displays "1"
executing bpy.ops.image.match_movie_length() sets the correct value

So I can only conclude that it's not updating the frame_duration field after a file is loaded
Will search further (I'm not an expert but getting close ;-)

image_ops.c: image_match_len_exec needs to be called???
or iuser->frames = IMB_anim_get_duration set??

Searched like crazy to pinpoint where it goes wrong. My findings are that everything is calculated fine from the movie file (anim_movie.c->IMB_anim_get_duration) and it shows correctly throughout blender interface and even when querying the loaded movie in console: bpy.data.images- [x].frame_duration returns the correct number Only the node itself displays "1" executing bpy.ops.image.match_movie_length() sets the correct value So I can only conclude that it's not updating the frame_duration field after a file is loaded Will search further (I'm not an expert but getting close ;-) image_ops.c: image_match_len_exec needs to be called??? or iuser->frames = IMB_anim_get_duration set??

Added subscriber: @Sergey

Added subscriber: @Sergey
Sergey Sharybin self-assigned this 2017-07-08 15:30:32 +02:00

Will have a look when i'm back to office.

Will have a look when i'm back to office.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Fixed the offset being detected based on movie file name, but movie length detection will need to be done via "Match movie length" button. The reason for that is because image open operator does not have access to movie descriptor or anything. It is possible to make it to behave in a similar way to MovieClip, but that's not really a bug. Added a note in our TODO list: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Editors#Image_Editor

So thanks for the report, but closing it now.

Fixed the offset being detected based on movie file name, but movie length detection will need to be done via "Match movie length" button. The reason for that is because image open operator does not have access to movie descriptor or anything. It is possible to make it to behave in a similar way to MovieClip, but that's not really a bug. Added a note in our TODO list: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Editors#Image_Editor So thanks for the report, but closing it now.
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
2 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#51989
No description provided.