Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Video glitch from srt obs #839

Open
JiaG293 opened this issue Oct 23, 2024 · 3 comments
Open

Video glitch from srt obs #839

JiaG293 opened this issue Oct 23, 2024 · 3 comments
Assignees
Labels
bug Program error or software error or software anomaly.

Comments

@JiaG293
Copy link

JiaG293 commented Oct 23, 2024

Describe the bug
For "media source" which taken from SRT OBS, the video source has a glitch problem.
Video source: Occasionally there will be image glitch
Image source: Image will have a glitch in the bottom half

Screenshots
image
image
image

Desktop (please complete the following information):

  • OS: Debian GNU/Linux 12 (bookworm) x86_64
  • Browser: Chrome 126.0.6478.183
  • Version: datarhei-core v16.16.0 (linux/amd64)

Additional context
report.txt

@JiaG293 JiaG293 added the bug Program error or software error or software anomaly. label Oct 23, 2024
@ioppermann
Copy link
Member

This is likely due to some packets drops and the SRT latency must be increased. This you do by adding &latency=... to the SRT URL that you entered into OBS. This parameter expects a value in microseconds. If this parameter is not provided, a default of 120ms is assumed.

Example: Restreamer tells you this URL:

srt://192.168.1.154:6000?mode=caller&transtype=live&streamid=1831091a-8402-421f-b579-348c6892e078.stream,mode:publish,token:xxx

There you add the latency parameter with a higher value, e.g. 500ms, resp. 500000 microseconds:

srt://192.168.1.154:6000?mode=caller&transtype=live&streamid=1831091a-8402-421f-b579-348c6892e078.stream,mode:publish,token:xxx&latency=500000

@ioppermann ioppermann self-assigned this Oct 25, 2024
@backface
Copy link

having similar problem here. It seems to me this issues threads are connected:

#755 (comment)

@UnluckyForSome
Copy link

I have the same issue, I think it’s something to do with Restreamer because I was testing all sorts of settings and restarting the stream to see if it would fix it. On one restart, the issue was gone. Then after the next restart (after changing no settings) it returned. Something wrong with packets and handshakes!

Another nugget I can give you - the SRT to my local Restreamer instance doesn’t have this issue, but an SRT to a public Restreamer instance develops these artefacts. Stumped!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Program error or software error or software anomaly.
Projects
None yet
Development

No branches or pull requests

4 participants