Wipe Effect does't work because its struct has only 1 input #47961

Closed
opened 2016-03-27 08:19:52 +02:00 by Paulo José Oliveira Amaro · 11 comments

I don't know since which version, but now the Wipe effect contains only 1 input, instead of 2 that are expected.
I've check the specs for all 2 inputs effects in EffectSequence and the it seems to affect only the WipeSequence class.
https://www.blender.org/api/blender_python_api_current/bpy.types.WipeSequence.html

I don't know since which version, but now the Wipe effect contains only 1 input, instead of 2 that are expected. I've check the specs for all 2 inputs effects in EffectSequence and the it seems to affect only the WipeSequence class. https://www.blender.org/api/blender_python_api_current/bpy.types.WipeSequence.html

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @PauloJoseOliveiraAmaro

Added subscriber: @PauloJoseOliveiraAmaro

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-03-27 16:27:52 +02:00

There is no bug here, Wipe is a single-strip effect, not a transition (though you can of course use it as such).

There is no bug here, Wipe is a single-strip effect, not a transition (though you can of course use it as such).

No, Wipe is not a single strip effect. See the wiki references and Youtube videos using it.
"The wipe effect is a type of transition strip. It can be used to transition from one strip to the next. The wipe will have no effect if created from a single strip instead of two strips. "
https://www.blender.org/manual/editors/sequencer/strips/types/effects/wipe.html
https://www.youtube.com/watch?v=YzhqERJbX_Y

It's a bug with the specs, the Blender behaviour is the expected when you create Wipe effect from 2 strips.

No, Wipe is not a single strip effect. See the wiki references and Youtube videos using it. "The wipe effect is a type of transition strip. It can be used to transition from one strip to the next. The wipe will have no effect if created from a single strip instead of two strips. " https://www.blender.org/manual/editors/sequencer/strips/types/effects/wipe.html https://www.youtube.com/watch?v=YzhqERJbX_Y It's a bug with the specs, the Blender behaviour is the expected when you create Wipe effect from 2 strips.

Please, test this .blend. It has two Wipes effects.
wipe-effect-bug.blend
wipe-effect-bug.png
Wipe in channel 4 (displayed in the main preview) was created from Red strip (bug).
Wipe in channel 3 (displayed in the top small preview) was created from Red and Yellow strips (correct)
Even with alpha over blend mode, the Wipe from channel 4 shows no wipe at all (because Wipe effect doesn't generate alpha channel). So it's useless.

I'm really sorry if I'm misunderstanding something, my intent is just to help Blender. I thank you for your time spent in this issue.

Please, test this .blend. It has two Wipes effects. [wipe-effect-bug.blend](https://archive.blender.org/developer/F298709/wipe-effect-bug.blend) ![wipe-effect-bug.png](https://archive.blender.org/developer/F298710/wipe-effect-bug.png) Wipe in channel 4 (displayed in the main preview) was created from Red strip (bug). Wipe in channel 3 (displayed in the top small preview) was created from Red and Yellow strips (correct) Even with alpha over blend mode, the Wipe from channel 4 shows no wipe at all (because Wipe effect doesn't generate alpha channel). So it's useless. I'm really sorry if I'm misunderstanding something, my intent is just to help Blender. I thank you for your time spent in this issue.

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Yeah… something is not right here indeed. Wipe reports only one input (not only in RNA, but even in core BKE C code), and yet it behaves and is handled as a two-inputs effect…

Yeah… something is not right here indeed. Wipe reports only one input (not only in RNA, but even in core BKE C code), and yet it behaves and is handled as a two-inputs effect…

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This issue was referenced by e5e8d67028

This issue was referenced by e5e8d67028ba6e0804a29a774224633ae5291003
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#47961
No description provided.