VSE: Applying Blur to Color strip produces different result than to same color Image strip #118213

Closed
opened 2024-02-13 19:05:40 +01:00 by Aras Pranckevicius · 7 comments

If you have a Color strip that is transformed to not take up whole screen, and apply some effect (e.g. Gaussian Blur) to it, the resulting image displays both the blurred strip, and the original Color strip underneath it.

This is different behavior from e.g. Image strips - if an image strip is an input to a Gaussian Blur effect, the original image is not displayed.

Attached repro .blend file and the image it uses as a .zip. Plus result of color vs image against gaussian blur:
res_color.png
res_image.png

From what I can tell, the logic in code that determines "which strips should be displayed", has special case that effect strips are always displayed. And "color" strip is deemed an effect strip, even though from user's perspective I'd argue that it's more similar to like a "source" strip (just instead of file based source, it generates a solid color)

The behavior was like that at least since Blender 3.0 (did not check earlier). Similar effect happens on Text strips, applying blur to them displays both the blurred version and the original underneath.

If you have a Color strip that is transformed to not take up whole screen, and apply some effect (e.g. Gaussian Blur) to it, the resulting image displays *both* the blurred strip, and the original Color strip underneath it. This is different behavior from e.g. Image strips - if an image strip is an input to a Gaussian Blur effect, the original image is not displayed. Attached repro .blend file and the image it uses as a .zip. Plus result of color vs image against gaussian blur: ![res_color.png](/attachments/a79f1d33-6639-4530-b251-fe75cadc226b) ![res_image.png](/attachments/230eedab-af22-414a-aa34-1d840432c911) From what I can tell, the logic in code that determines "which strips should be displayed", has special case that effect strips are always displayed. And "color" strip is deemed an effect strip, even though from user's perspective I'd argue that it's more similar to like a "source" strip (just instead of file based source, it generates a solid color) The behavior was like that at least since Blender 3.0 (did not check earlier). Similar effect happens on Text strips, applying blur to them displays both the blurred version and the original underneath.
Aras Pranckevicius added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-02-13 19:05:40 +01:00

Can reproduce. If I remember correctly in 2.79 you had to mute strips on which you applied effects. Agree with this being bug now though.

Can reproduce. If I remember correctly in 2.79 you had to mute strips on which you applied effects. Agree with this being bug now though.
Author
Member

I can fairly easily think of how to solve this, and I think (hope) for Color strips that would not cause practical problems. Not sure about Text strips though, e.g. today if you just add a blur to a Text, you get both displayed at once, and I'd assume people might be accidentally relying on that behavior?

I can fairly easily think of how to solve this, and _I think_ (hope) for Color strips that would not cause practical problems. Not sure about Text strips though, e.g. today if you just add a blur to a Text, you get both displayed at once, and I'd assume people might be accidentally relying on that behavior?

I can fairly easily think of how to solve this, and I think (hope) for Color strips that would not cause practical problems.

I think there is condition somewhere. I remember seeing it quite some time ago...

Not sure about Text strips though, e.g. today if you just add a blur to a Text, you get both displayed at once, and I'd assume people might be accidentally relying on that behavior?

Quite possibly. Which is good question if then this should be classified as bug :/ You can always add dummy effects, but forward compatibility...

There was report where user made quite elaborate text glow effect. Can't find the report now, it was like 30 strip tall stack. Would be good test case...

> I can fairly easily think of how to solve this, and _I think_ (hope) for Color strips that would not cause practical problems. I think there is condition somewhere. I remember seeing it quite some time ago... > Not sure about Text strips though, e.g. today if you just add a blur to a Text, you get both displayed at once, and I'd assume people might be accidentally relying on that behavior? Quite possibly. Which is good question if then this should be classified as bug :/ You can always add dummy effects, but forward compatibility... There was report where user made quite elaborate text glow effect. Can't find the report now, it was like 30 strip tall stack. Would be good test case...
Ah [found it](https://projects.blender.org/attachments/f0c8dc53-b61e-4a49-9329-6a6c2da48090)
Author
Member

@iss hmm, that file is produced with Blender 3.6, it seems... and it renders differently between 3.6 and 4.0 already (same in 4.1/4.2 as in 4.0). Not sure if by design, or something "broke" lol.

@iss hmm, that file is produced with Blender 3.6, it seems... and it renders differently between 3.6 and 4.0 already (same in 4.1/4.2 as in 4.0). Not sure if by design, or something "broke" lol.
Author
Member

@iss found what is the cause of different outline in your "complex text effect stack" file between 3.6 and 4.0 -- the effect was seemingly relying on strip color Multiply affecting the alpha channel as well, which after #110984 was not doing that. #113791 introduced an option to use that; with that option on the effect looks the same as in 3.6. Curiously that was not mentioned in 4.0 release notes.

@iss found what is the cause of different outline in your "complex text effect stack" file between 3.6 and 4.0 -- the effect was seemingly relying on strip color Multiply affecting the alpha channel as well, which after #110984 was not doing that. #113791 introduced an option to use that; with that option on the effect looks the same as in 3.6. Curiously that was not mentioned in 4.0 release notes.

That change indeed should have been mentioned in notes. My bad.

That change indeed should have been mentioned in notes. My bad.
Aras Pranckevicius self-assigned this 2024-02-15 11:44:37 +01:00
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-02-16 19:57:47 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
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
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#118213
No description provided.