SRT reading via media source uses old / incorrect url or streamid in obs 32.2.2

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

32.2.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/vdkXedUtye0toWWU

OBS Studio Crash Log URL

No response

Expected Behavior

OBS should be able to read from the SRT url stream id that I put into the media source.

Current Behavior

OBS does not try to read from the SRT URL / stream id that I put into the media source. Instead it tries to read from either a completely different old URL or an different stream id. Sometimes even from a long time ago. This makes it fail to read because it isn't reading from the correct location.

Steps to Reproduce

1. Be on obs 32.1.2
2. Create a media source and have it reading from a remote SRT stream id
3. Upgrade to obs 32.2.2
4. It either breaks then or try changing it to a different stream id / url and if you look at the OBS logs it will not be trying to read from the new updated one
5. Downgrade to 32.1.2 and it works again
   ...

Anything else we should know?

1. Confirmed this behavior happens on Windows 11, 10, and macos
2. It works fine in OBS 32.1.2 and directly after upgrading to 32.2.2 it breaks
3. The issue happens on both HEVC and H264 encoders

Start with the supplied OBS log and compare media-source behavior between OBS 32.1.2 and 32.2.2, focusing on the SRT URL and stream ID recorded during connection attempts. Reproduce the upgrade and source-edit steps on the listed Windows and macOS versions, then verify that the logs use the current URL and stream ID and that both HEVC and H264 streams connect.