Closed kyleparrott closed 2 months ago
Latest commit: dda287b3cae4d146d0f529349ba9d5b4372078fd
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Currently if a track processor is applied to a video track while the track's upstream is paused (ie.
pauseUpstream()
has been called on it), the next call to resume upstream will replace the processed track with the plain, unprocessed track. This should correct that logic and prevent this incorrect replacement.My app was performing the following steps when I ran into this behavior:
I am pausing and resuming the track when I am making processor changes to prevent showing any "flashes" of unprocessed frames when changing between virtual background options.