Maniphest T97210

Wipe Strip in VSE does not produce wipe effect
Closed, Archived
Actions

Assigned To
None
Authored By
stephen paschke (paskperfect)
Apr 10 2022, 5:08 AM
Tags
  • BF Blender
Subscribers
Philipp Oeser (lichtwerk)
Pratik Borhade (PratikPB2123)
Richard Antalik (ISS)
stephen paschke (paskperfect)

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Radeon(TM) RX 550 ATI Technologies Inc. 4.5.13587 Core Profile Context 19.40.38.02 26.20.14038.2009

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: rBcc66d1020c3b
Worked: 3.0.0

Short description of error
Standard Wipe-strip (Although being generated) does not perform as expected. Effect is not being displayed in the Sequencer (VSE) Preveiw editor window.

Exact steps for others to reproduce the error

  1. Generate Two Color strips on same channel in sequencer, separated by un-used (empty) time.
  2. Select the two color strips and generate a wipe strip by Sequencer>Add>Transition>Wipe.
  3. Place the Time-line Position Line mid-way across the just-generated wipe strip,
  4. and observe that the wipe effect is not present in the Sequencer-Preview view.

This Bug was mentioned by @BlenderFrenzy , in the #VSE room of blender.chat , and described on video posted on Youtube.com - https://www.youtube.com/watch?v=xiHcmqG_KWw

Bug_Report_Wipe-Out.blend576 KBDownload

Related Objects

Event Timeline

stephen paschke (paskperfect) created this task.Apr 10 2022, 5:08 AM
stephen paschke (paskperfect) added a comment.Apr 10 2022, 8:23 AM

Most recent daily build has this bug corrected.

(3.2.0 Alpha)

Pratik Borhade (PratikPB2123) changed the task status from Needs Triage to Needs Information from Developers.Apr 10 2022, 2:43 PM
Pratik Borhade (PratikPB2123) added subscribers: Richard Antalik (ISS), Philipp Oeser (lichtwerk), Pratik Borhade (PratikPB2123).

Hi, thanks for the report.

Most recent daily build has this bug corrected.

Yes the bug is fixed in current master. See the original report: T96582.
I don't think 3.1 branch will receive more bug fixes (assuming 3.1.2 is the last corrective release).
@Philipp Oeser (lichtwerk) @Richard Antalik (ISS) hi, fix was listed in T96241 but wasn't backported for corrective release. Any reasons?

Philipp Oeser (lichtwerk) closed this task as Archived.Apr 11 2022, 6:22 AM

Seems like @Richard Antalik (ISS) added the commit to the wrong bock (in "3.1.1" instead of "To be backported") and I did not notice this. I appologize, but there is not much we can do here now...

Will close.

Richard Antalik (ISS) added a comment.Apr 12 2022, 5:01 PM

I must not noticed "To be backported" table, I apologize for that too. I remember checking that table had commits pending backporting still, will double check this next time.