-
Notifications
You must be signed in to change notification settings - Fork 642
Reolink Duo 2 incompatible due to aspect ratio and h265 encoding #1711
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
Comments
Well. In which viewer do you have the wrong aspect ratio? And which one don't you have a problem with? For example ffplay or vlc. Show stream probe from go2rtc WebUI. |
The video aspect ratio playback is fine. I think it is go2rtc that doesnt like it. The camera's aspect ratio is 24:9 (4608x1728). I can view the stream fine in VLC as well as go2rtc up until a point. I guess that is what makes in confusing the go2rtc stream plays fine in the beginning then eventually just stops running , i dont see any apparent errors in the trace to understand why. Ffprobe of go2trc webui:
So that rtps restream (rtsp://192.168.1.50:8554/front) runs fine in VLC. It is the |
So. I don't understand. Aspect ratio fine, but problem that stream stops after some time? |
I don't know why the stream fails after some time but, yes. I am suspecting aspect ratio along with h265 because all other variables about this stream I have ruled out. I have cx820 and cx810 all 4k streams and load just fine. The aspect ratio makes this unique and I felt it was impacting go2rtc and h265 is notoriously difficult. There is something missing in the logs to explain why it won't load. Any where else I can pull logs or metrics to better understand what might be happening? |
I am having trouble configuring a Reolink Duo 2 from what seems to be a combination of the aspect ratio and the h265 encoding. This camera main stream and its sub stream have a strange aspect ratio due to the cameras 180 degree FOV achieveable with feeds from two lenses stiched together on device.
For the record I use Frigate's wrapped go2rtc which is at version 1.9.2
I can also tell Frigate is not contributing to the issue because when i access the stream on 1984 (directly to go2rtc) and click "streams" this is where i see the failure to load the stream and perform my testing.
My camera config:

I have also set them to constant bit rate and constant frame rate to reduce variables
ffprobe on Clear stream:
ffprobe on Fluent stream:
go2rtc config (within frigate):
I can tell that MSE mode is being used and that is acceptable for my use case. From what I have read h265 will use MSE. This works for a while but fails an an arbitrary time in the future. Eventually go2rtc seems to reject it as a viable stream probably due to #1634 however wrapping the stream in
ffmpeg
does not help either the stream flickers and generates artifacts.The substream does work with RTC as its probably h264
I have tried using ffmpeg and re-encoding teh stream to h264 but the aspect ratio makes this not possible. So the stream has to stay in h265
Config:
Log:
When the stream eventually breaks i reload the stream hosted on go2rtc (http://192.168.1.50:1984/stream.html?src=front) and this is the trace log:
I cannot tell if the webrtc errors are red herrings, the stream clearly shows it hosting the MSE version and not webrtc so i think these errors just show why webrtc is not hosting the stream. Any ideas on what i might be doing wrong or tips on configuring this camera would be appreciated. Thanks
The text was updated successfully, but these errors were encountered: