jesperstarkar
commented
4 years ago We have added https://github.com/CasparCG/server/issues/1307 to the agenda, and here is a primer on why this is not a simple "fix it" task.
There's two types of Route-producers: layer and channel. Layer is allowing multiple channels to use the same producers/sources for layers, by referencing them. The Channel producer in <2.2 would render the source-channel to a reusable texture that would act as a new source in other channels.
Some change in 2.2 seems to drop the strategy of rendering the source-channel, and instead tries to replicate the channels final composition on a new channel by re-producing all sources and their transforms/effects.
The problem is: this will not work consistently/predictably with all compositions when opacity (and/or blend modes) are added to the mix. The change in 2.2 is basically a breaking change to how the channel route producer works.
I see three approaches forward:
- Make the 2.3 channel route producer work as <2.2 by rendering.
- Pull through on the breaking change from 2.2, and change how the channel route producer will work with no backwards compatibility (you can read from my tone that I'm against this).
- Do both: Have a normal mode in the channel producer that acts like <2.2 and also allowing for the new suggested >2.2 behaviour through a new API - and patch it to do the correct math for transforms as #1307 suggests.
dotarmin
When
Thu, 18 June 2020 at 11:00 UTC
Where
Google Meet, a link will be sent to attendes prior to the meeting.
Agenda
The agenda will be formed prior to the meeting and will consist of issues and pull requests from the CasparCG organization with the tsc-agenda label. Comments posted on this issue will also be a part of the agenda.
CasparCG/Server
General
Issues/Pull requests
CasparCG/Client
General
Invited
Guests
In the future we will be able to invite guests and observers, but we have to form the processes around the technical steering committee first before we can invite others to participate.
Notes
The agenda is formed by issues and pull requests labelled with tsc-agenda across all of the repositories in the CasparCG organization. Please label any additional issues or pull requests that we need to bring up for discussion before the meeting starts.