"No, only one camera was initially causing trouble. Closed a ticket yesterday after a user discovered the core issue was his modem/router could not handle the traffic from his 810A causing No Signal errors on BI(see below). Here is a great article on one engineer's journey to reverse engineer the B800 to access the streams.Ģ021-Jun-10: With all these very high resolution (8MP) cameras becoming more and more pervasive, there is an increased load on your networking equipment. However, it turns out while the camera claims ONVIF compatibility, in fact the camera is closed and proprietary.
Blue iris setup series#
The B800 series have been replaced by the 810/820 lineup so probably not widely used anymore. One of my cameras arrived broken and I've had the misfortune of dealing with their support already, I'm fairly certain they'd do nothing with the above mentioned information.Į1-pro-onvif_optimized.jpg (77.48 KiB) Viewed 16852 times
Blue iris setup update#
The key thing to all of this is not letting the reolinks update their time and it seems to work better.Īnd LOL at notifying Reolink, if I knew what I know now, I'd never buy any of their terrible products. Also I've adjusted the keyframe interval on the camera itself and it's 1 during the day, but still takes a dump at night with the newer firmware. The bigger pre trigger (or network buffer? I did both at the same time) seems to ensure there's a keyframe. It used to be 12.5, but I would occasionally end up with the weird grey everywhere and only the moving object visible. Also, I made a massive network buffer, and a 15 second pre trigger. The audio is also constantly blipping a bit when using the time codes, but it at least stays in sync. Unlike the RLC-820A, the RLC822A DOES need the RTSP timecodes, or the audio will go out of sync. The RLC820A doesn't need the time codes, and honestly in the below config does everything mostly well. Adjusting my time sync interval to test it, has caused the audio/video to stay in sync, for how long, I don't know. Something happens where it adjusts the video, but not the audio stream when it syncs the time (even if ignoring OR subscribing to the RTSP time codes), causing the audio to end up further and further ahead with each time sync. By default, once a day, they reach out to the NTP server and sync their time. They seem to keep "fast" time and get ahead. I need more time to test to say it's "stable" but it seems to be related to the Reolink keeping time. One thing I can tell you is decoder compatibility mode is no longer required with the later firmware, and just introduces more artifactsĪlso, I've asked around, and the audio drift is very much an issue on the Reolinks, but I think I may have figured out the root cause and it's odd. I've attached my config for the RLC-820A since it seems to keep its sync the longest. With the attached config I've pretty much eliminated video artifacts (minus that annoying everything turns grey in the x265 stream periodically) and this audio issue is the last one I'm hunting down. Unfortunately, PTZ controls do not come across through ONVIF. Reolink support states no more support for this camera and recommends upgrading the camera.Īccording to a user, the RLC 423 Make/Model does not work. There may be a firmware bug that resets the PW, IP address from static to DHCP among other settings when performing a restart. encoding from H.264 High to H.264 Baseline) on the RLC-423 requires a restart. Change "main" to "sub" in sub stream URI as seen above.Īccording to another user, changing settings (e.g. Simply copy/paste mainstream to sub stream.
Baseline RTMP" Model will also populate the mainstream. Please review IP Camera Connection document for details on connecting cameras correctly. If so, you can simply leverage ONVIF to populate the main and sub stream URIs. I believe the RLC 4 & 5 series both provide ONVIF support. Reolink_ip-config_optimized.png (50.14 KiB) Viewed 14440 times When switching to RTMP, the cameras worked perfectly for the mainstream and the sub stream. Many users were complaining about the No Signal message when using RTSP from BI.
From our testing, RTMP seems to perform better. However, Reolink provides RTSP and RTMP support. However, Intel Beta adversely affected his Amcrest cameras even with H.264 Baseline. One user with an i7-7700K GHz stated the Intel Beta selection for GPU worked well with his Reolinks. I'm only mentioning this because it's a 5 min test. Reolink H.264 High profile (default setting) causes no signal. Reolink engineers have identified video freeze issues with dual streams on their 8MP cameras (RLC-810A, RLC-811A and RLC-820A). This post (article) from BI Support is so the BI Support team can provide information quickly to the community based on support findings and troubleshooting.
0 kommentar(er)
