Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 118
    • Merge requests 118
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #577

Closed
Open
Created Jan 10, 2022 by Robert Mader@rmaderDeveloper

Subsurface blending regression from !596

The change in !596 (9a6a4e70) apparently broke previous behaviour of blending. This is prominently visible with the Gstreamer Waylandsink example demos.

main: Screenshot_from_2022-01-10_17-39-25

previously and other compositors: Screenshot_from_2022-01-10_17-38-43

Note: the "video" here contains alpha/is not opaque. Its surface is on top of a black background surface.

Also: the Gstreamer Waylandsink appears to be mainly used for cases where the surface can be scanned out by the display controller. So this might be an example of display controllers making assumptions about non-linear blending, when done in hardware and not by the shader.

cc @pq, @daniels

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking