Product Roadmap: What's Coming Next
How ColorX Technology Turn Night into Day
Reolink App v4.41 Released
Attached.There really isn't an issue with my unit; it's just a general observation on all of your zoom cameras. They don't store focus points, and I was trying to figure out why. Because they can't store focus, they rely on autofocus or manual focus, and manual focus has proven itself to be very difficult to use over high latency links, and I was trying to figure out why.RLC-423_SystemInfo.png
Ugh. Still having this problem. See here:https://www.youtube.com/channel/UC7FH1CCSdg1-W9mlJ52cceQ/liveAs the bees run along the walls, they should run smoothly. But they appear to j**k, as though the camera is repeating frames.
At long last I think I have figured this out. The culprit is the "3D Noise Reduction" feature in the camera. 3D noise reduction tries to average non-moving portions of adjacent frames in an attempt to reduce temporal noise. The non-RTSP stream received by the Reolink client does this properly, and outputs frames in order. The RTSP stream does _not_ do this properly, so it repeats some frames, which results in the stuttering effect that you see here. If you turn off the 3D Noise Reduction, then the RTSP stream works properly, although the bit rate goes way up. Other manufacturers implement 3D Noise Reduction properly in their RTSP streams.
Would love to take credit, BUT.... This question came up several weeks ago and ”Double Click” was the answer.There are days that I move the mouse around the screen clicking to see if anything happens.
LOL! I manage a software development team at work, and madly clicking around or banging on the keyboard is how I test for bugs.
double click in the Playback window, which causes it to split into four smaller windows.”intuitive”? no.
Thanks! That works, and is completely non-intuitive. How did you figure it out?For Reolink, please consider having a standard "n-Up" selector in the Playback window, just as you do for Live View.
I recently upgraded from the old "Reolink Client" v188.8.131.52 to the new "Reolink" app v8.1.20 on both my Mac and on my PC. While most of the new features are great, such as 4x playback, and the performance improvement is good, I can't figure out how to get more than 1 camera to play back simultaneously. In the old v184.108.40.206 it worked, and I could see simultaneous playback from multiple cameras with overlapping views, which is very important for many security applications:but I can't find a way to add more than 1 channel in the new version, even though it clearly shows that it should support 4 channels of playback:The Knowledge Base contains this article with conflicting information. One part reads:
Note: You can only playback one device at a time on Reolink App and Web browser.
How to Playback Recordings of Multiple Cameras at the Same Time on Reolink Client (Mac)
Mitku, of course that would be the preferred solution, but all the evidence in the way the Reolink cameras operate suggests that they lack the hardware necessary to move by a specific physical step. If the cameras had physical steps that could be incremented or addressed, then the cameras would be able to store focus points instead of invoking auto-focus every time they go to a preset.The fact that they _don't_ do this leads me to conclude that the motors in the cameras lack the hardware required to provide positional feedback to the controller.That's why my proposal uses time instead of position, because that's the only way I can it working.
Is there any way to get a 4-up view on an iPad? I have an ancient iPad that I'd like to repurpose as a persistent monitor for the 4 most important cameras around my house.
Haha thanks! I like your stream by the way.
Thanks! It'll be a lot more reliable once I figure out how to stop/restart the service cleanly.
It seems it differs by model. Some cameras (my C2 and alex's RLC 410 and 420) appear to have an ”auto cleanup” of streams after a wait of about 30 seconds (after stream termination from the computer end), whereas for others (the cameras Steven Kan and bigger_law have), it appears there isn't such a function (thus requiring a camera reboot).
Ah, things are making more and more sense right now! I have a RLC-410S with Hardware No. IPC_3816M, and it barfs whenever the ffmpeg service stops or restarts.I have an RLC-410 with Hardware No. IPC_51316M it doesn't seem to mind when my ffmpeg service stops/restarts. I couldn't figure out why two such similar cameras behaved so differently.My RLC-423 and my RLC-411 are both Hardware No. IPC_3816M, and both behave like my RLC-410S, e.g. they barf on ffmpeg stop/restart.
Ah, ok. Thanks! I'll ask over on arstechnica, where they know Unix. You still get a cookie for finding the solution!
Ah, I see. Right now I'm calling ffmpeg through a bash script:
#!/bin/bashcd /usr/local/bin/while truedo./ffmpeg -re -thread_queue_size 512 -rtsp_transport tcp -i \"rtsp://anonymous:firstname.lastname@example.org:554" -i WilliamTellOverture.mp3 \-vcodec copy -acodec copy -t 00:11:51 -f flv \"rtmp://a.rtmp.youtube.com/live2/my-youtube-streaming-key"sleep 10sdone
Hi there! Join the Commnunity to get all the latest news, tips and more!