VSE: Changes in F-curve noise modifier are not shown #109579

Open
opened 2023-07-01 11:45:05 +02:00 by Frank · 4 comments

System Information
Operating system: Windows-10-10.0.18363-SP0 64 Bits
Graphics card: AMD Radeon HD 6800 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: (newest version of Blender that worked as expected)

Short description of error
When you animate the Y-position of a strip in the VSE and put a noise modifier on the F-curve, any later changes to the settings are not shown in the VSE preview window (preview cache not emptied??).

Exact steps for others to reproduce the error

  1. Open the attached blend file.
  2. Play the animation. You see the cube shake heavily.
  3. Change the strength of the F-curve noise modifier from 1000 to 1.
  4. Play the animation. The heavy shaking is still there, while it should be gone.
  5. Save the updated blend file and reload it.
  6. Play the animation. The shaking is gone now. So you need to save and reload the file to see the effect of the changes that were made in the F-curve noise modifier. This is very inconvenient.

NOTE: When you play only the first 100 frames of the animation, set the noise strength to 1 and play the animation again, frame 101-250 play correctly (without the shaking), but frame 1-100 still show the shaking.
It looks like the preview cache is not being emptied when a change it made in the noise modifier.

**System Information** Operating system: Windows-10-10.0.18363-SP0 64 Bits Graphics card: AMD Radeon HD 6800 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: (newest version of Blender that worked as expected) **Short description of error** When you animate the Y-position of a strip in the VSE and put a noise modifier on the F-curve, any later changes to the settings are not shown in the VSE preview window (preview cache not emptied??). **Exact steps for others to reproduce the error** 1. Open the attached blend file. 2. Play the animation. You see the cube shake heavily. 3. Change the strength of the F-curve noise modifier from 1000 to 1. 4. Play the animation. The heavy shaking is still there, while it should be gone. 5. Save the updated blend file and reload it. 6. Play the animation. The shaking is gone now. So you need to save and reload the file to see the effect of the changes that were made in the F-curve noise modifier. This is very inconvenient. NOTE: When you play only the first 100 frames of the animation, set the noise strength to 1 and play the animation again, frame 101-250 play correctly (without the shaking), but frame 1-100 still show the shaking. It looks like the preview cache is not being emptied when a change it made in the noise modifier.
Frank added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-07-01 11:45:06 +02:00
Iliya Katushenock added the
Interest
Video Sequencer
label 2023-07-01 12:30:50 +02:00
Member

Thanks for the report. I can confirm.
cc @iss

Thanks for the report. I can confirm. cc @iss

Will classify as known issue, since there are more instances of curve data not updating sequencer cache.

Will classify as known issue, since there are more instances of curve data not updating sequencer cache.
Richard Antalik added
Type
Known Issue
and removed
Type
Report
labels 2023-07-04 04:26:09 +02:00
Author

Does the status "known issue" mean that the fix for this issue is already in the roadmap?
This is all new to me, I don"t have a clue how long it takes on average before an issue is solved.

Does the status "known issue" mean that the fix for this issue is already in the roadmap? This is all new to me, I don"t have a clue how long it takes on average before an issue is solved.
Member

Does the status "known issue" mean that the fix for this issue is already in the roadmap?
This is all new to me, I don"t have a clue how long it takes on average before an issue is solved.

Unfortunately ,quite the opposite. If an issue is classified as Bug, a fix will be more likely to happen faster, a Known Issue might mean a fix will not see the light of day within the next 6 months.

A bit of it is described here https://wiki.blender.org/wiki/Process/A_Bugs_Life

> Does the status "known issue" mean that the fix for this issue is already in the roadmap? > This is all new to me, I don"t have a clue how long it takes on average before an issue is solved. Unfortunately ,quite the opposite. If an issue is classified as `Bug`, a fix will be more likely to happen faster, a `Known Issue` might mean a fix will not see the light of day within the next 6 months. A bit of it is described here https://wiki.blender.org/wiki/Process/A_Bugs_Life
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
4 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#109579
No description provided.