Skip to content

Conversation

@lucas-romanenko
Copy link

Summary

This PR enhances upstream key functionality by fixing next transition buttons functionality and adding support for FTB (Fade to Black) disabled state detection and set commands.

Changes Made

  • **Fixed upstream key next transition **: Resolved issues with next transition state management
  • Added FTB disabled state detection: Library now properly handles setting and reading state of FTB Disable button

Testing

  • Tested with 1 M/E Constellation
  • Verified upstream key transitions work correctly
  • Confirmed FTB disabled state is properly detected and reported

Background

These changes address limitations in the current upstream key handling that could cause timing issues during transitions and lack of visibility into FTB disabled states.

Compatibility

  • Maintains backward compatibility with existing code
  • No breaking changes to the existing API

…oolean functionality.

Next Transition Upstream Key buttons now work. 

FTB Disabled checkbox (appears in settings menu in Software Control) functionality added).
…Boolean functionality.

Next Transition Upstream Key buttons now work.

FTB Disabled checkbox (appears in settings menu in Software Control) functionality added).
…oolean functionality.

Next Transition Upstream Key buttons now work.

FTB Disabled checkbox (appears in settings menu in Software Control) functionality added).
The rate box does not actually represent the StingRate state command. That is in Transition settings > Sting. 

The number that shows in the rate box when sting is the selected Transition Style is actually Pre Roll + Clip Duration. I edited Transition.py to add these 2 values together to return totalRate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant