🐛[BUG] TwitCasting: Recording does not stop and restart when stream goes offline and comes back live

[DealsBeam]

⚠️ Confirm if similar issues exist

• I have searched the issues and found no similar problems

🔧 How did you run the program?

Running with source code

🐍 If running with source code, please select your Python environment version

Other (please specify in the issue)

💻 Please select your system environment

Other (please specify in the issue)

⚠️ Confirm if you have retried multiple times

• I have tried multiple times and still encounter the problem

🕹 Reproduction steps

1. The live room address I tried to record is: any channel on https://twitcasting.tv/
2. The recording format I used is: M4A (Audio only)
3. Add the TwitCasting stream URL to StreamCap with loop monitoring enabled
4. Wait for the stream to go live - recording starts correctly
5. Streamer ends their broadcast or it ends by its self
6. Streamer starts a new broadcast shortly after
7. StreamCap does not detect the new broadcast and does not start a new recording

😯 Problem description

• OS: Linux (CachyOS)
• StreamCap version: 1.0.3
• Running via Docker
• Platform being recorded: TwitCasting

When recording a TwitCasting stream and the streamer ends their broadcast and
starts a new one, StreamCap does not stop the current recording and start a
new one for the new broadcast. Instead it appears to either continue the old
recording or gets stuck without detecting the new stream.

Expected behavior: When a monitored stream goes offline and comes back live
as a new broadcast, StreamCap should automatically stop the current recording,
save the file, and start a new recording for the new broadcast session.

Current behavior: StreamCap does not detect the stream restart and does not
begin a new recording for the new broadcast.

(Settings)

📜 Error information

No response