You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warnings from github.com/AlexxIT/go2rtc/pkg/core/track.go:144 +0x48 and track.go:112 +0x28
(Warning) go2rtc
Possible Cause
go2rtc logs these warnings when it encounters problems parsing or relaying a video/audio track.
Suggested Fixes
Check go2rtc Configuration: Look in your go2rtc.yaml (if you have one) or the add-on’s configuration. Make sure the RTSP/HTTP streams are valid and spelled correctly.
Adjust Settings: If the camera stream is high-bitrate or has an unusual codec, try a lower resolution/substream or a standard H.264 profile.
Update go2rtc: Ensure you have the latest version of the go2rtc integration or add-on.
Error from stream worker: No dts in 7 consecutive packets
(Error) Stream
Possible Cause
“No dts” (decoding timestamp) means the demuxer can’t find timestamps in consecutive packets. This is often a camera firmware or network timing/latency issue.
The text was updated successfully, but these errors were encountered:
Warnings from github.com/AlexxIT/go2rtc/pkg/core/track.go:144 +0x48 and track.go:112 +0x28
(Warning) go2rtc
Possible Cause
go2rtc logs these warnings when it encounters problems parsing or relaying a video/audio track.
Suggested Fixes
Check go2rtc Configuration: Look in your go2rtc.yaml (if you have one) or the add-on’s configuration. Make sure the RTSP/HTTP streams are valid and spelled correctly.
Adjust Settings: If the camera stream is high-bitrate or has an unusual codec, try a lower resolution/substream or a standard H.264 profile.
Update go2rtc: Ensure you have the latest version of the go2rtc integration or add-on.
Error from stream worker: No dts in 7 consecutive packets
(Error) Stream
Possible Cause
“No dts” (decoding timestamp) means the demuxer can’t find timestamps in consecutive packets. This is often a camera firmware or network timing/latency issue.
The text was updated successfully, but these errors were encountered: