BitRate27

When I did this I verified the issue did not exist on Main. However, for the sake of consistency, I went ahead and dug into the differences between starting and...

What is the log from? It looks like a NDI Analysis output. It is not helpful. It would be more helpful to run OBS with --distroav-debug flag and upload the...

Do you have the OBS log file from this run? We need to know why the output creation failed in order to try and duplicate.

You bring up some good areas to investigate further. I see now where the log file came from, it is added by PRISM to the OBS code. It should be...

In addition to using heap memory (which we need to fix), merely checking context.output instead of context.is_running will properly close the audio and video if the output was never created...

This is very helpful! One way to get send_create to fail is to provide an existing NDI name. I think this is enough to duplicate in OBS.

Re-opening issue as the 996 fixed another problem and was merged into master in April 2024. The problem can be duplicated by creating an NDI output with the same name...

While reviewing PR [Keep Last Frame Received](https://github.com/DistroAV/DistroAV/pull/1330) I ran into this issue. The solution to this involves building on top of that PR and adding the following code to ndi_sender_create:...

Looking at the problem of changing the NDI name for existing/saved scenes, if we change the default NDI name (FLT_PROP_NAME) to Dedicated NDI Output (\), then when we create the...

I modified the code above and this gets around the problem of changing existing NDI names: ``` auto parent_source = obs_filter_get_parent(filter->obs_source); if (!parent_source) { // Don't create sender if the...