Is there an existing issue for this?

• I have searched the existing issues and did not find a similar issue

This bug exists on the latest available release of DistroAV and supported environment?

• I have checked this bug still exists on the latest available version of DistroAV.
• I have checked that my OS / OBS / NDI versions are supported & up-to-date.

OBS Log [URL] - Important!

No response

Issue reported - Current Behavior

When a source is deleted which has a Dedicated NDI Output filter on it, the NDI sender is not destroyed and can be selected in Studio Monitor. The sender is finally destroyed when OBS closes.

I have a fix for this issue.

Expected Behavior

The sender should be destroyed when the source is deleted. Same as when the filter is deleted.

Steps To Reproduce

In OBS
Select a source in a scene
Select Filters
Select + to add a DistroAV NDI Output filter to a source
Select OK
Select Done
In Studio Monitor
Select the menu icon in upper left (note DistroAV NDI Output exists)
In OBS
Select the trash can at the bottom of the Source list to delete the currently selected source (which you just added the filter to)
In Studio Monitor
Select the menu icon in upper left (note DistroAV NDI Output still exists)

Environment

- OS: Windows 11
- OBS: 32.0.1
- DistroAV: 6.1.1
- NDI: 6.3.0.3

Pre-Check for Bug Report

• I am able to reproduce the bug following the steps provided above
• I have confirmed this bug exist on more than one device/computer
• I have tested using a new scene collection to reproduce the issue
• I have tested on a 'clean' OBS installation (aka with no other scripts or plugin installed)
• I am filing this bug report as a Human and have reviewed its content to the best of my ability to ensure it's accurate.