Fix: casparCG template transitions bug #225
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Transitions for templates are not supported by Caspar nor CasparCG state
|
There is an edge case here when your template doesn't have an out transition and you want to do a fade out using the casparcg transitions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug fix.
CasparCG Templates doesn't actually support transitions, but we have code paths that support it (but apparently they are buggy).
What is the current behavior? (You can also link to an open issue here)
When playing a template object, and (accidentally) has set a transition for it, the template isn't played properly.
(when stopped, a PLAY "empty" is sent, not a CG STOP)
What is the new behavior (if this is a feature change)?
CG PLAY and CG STOP are sent, as they should
Other information:
TODO