Best posts made by joseph_1979

@tomsreolink I already told them. It is of utmost important to keep customers informed with the latest developments, fw upgrades, roadmaps with estimated deliver time, etc. And that any client or fw release should be rigorously tested.

@davidandrewpowell81_526149738635440 I suggest you to roll back to 8.8.5 on the other pc and wait till they fix it. You are not the only one to encounter this issue. I cannot reproduce and so cannot delve through.

I saw some have drag the camera out of the liveview. Others have deleted and added cams.

In my opinion when upgrading to 64 bit client they should have done a clean up of the installed client and its data and then proceed with the fresh installation. The 64 bit client is using the same data of the 32 bit client.

@md I have already requested all of these with support, here and on Reddit.

@strangerjona_704168632094884 Last year I did ask for sound detection but seems not yet on their priority list.

It seems that the priority list is based on customers request to support. So please send your request on support(at)reolink(dot)com Replace (at) by @ and(dot) by . Sometimes the site restricts us from adding ULR.

@big_ted of course. But they need to improve their clients and add more features customers are requesting. We are seeing new cameras but no features.

@jedi2020_32727772450952 IoS I meant MAC.....was in a meeting with my engineers while typing :).

@manc-sooty_859835089170607 We have been saying this for v1 chimes. They should have produced more chimes than doorbell :).

@nomahisssss_477125106348271 Object tagging which triggered detection is not yet implemented on Reolink. Customers are looking for it.

@robert_5420 What is the fw of your NVR? Check out this link https://support.reolink.com/hc/en-us/articles/4410520891033-Which-NVR-Can-Work-with-Reolink-Duo-WiFi-PoE-/?source=search

"Please note that if your Duo 2 WiFi/PoE works with an NVR with Hw_H3MB18 Hw_N3MB01, and Hw_N2MB02 hardware, you need to upgrade your NVR's firmware to the latest version to view the video, and it can only support max. 6MP video resolution.
The decoding width of Hw_H3MB18 Hw_N3MB01, and Hw_N2MB02 hardware is 4096. Therefore, if you set the mainstream resolution as 4608*1728, the image cannot be displayed on full screen successfully. It is recommended to set the mainstream resolution as 4096*1536."

Ensure you have the latest fw on both DUO 2 and NVR. Go to their Reolink Download Center and check them out.

@davidandrewpowell81_526149738635440 Correct and they have introduced a scheduler on the sensitivity but has been restricted to motion. This should have been extended to cover all object types. There are still issues with IOT and clear stream views. I forwarded my feedback to senior support and hope they clear them before this is launched to the public.

@gkl_293453548720263 See if this helps you https://support.reolink.com/hc/en-us/articles/26862588584089-Introduction-to-Antenna-Extension-Cable/

@maineac_706707508990194 Yes, they are fixing bugs and developing some new features . Personally I won't make my application available to the customers unless I am 100% sure that it is functioning correctly. I used to spend a lot of time testing and re-testing before handling it to my customers.

The missing icons in live view and the calendar issues have been solved. However, they still need to solve the clear mode stream and the floodlight configuration.

@martin_762542987481297 We are awaiting the roadmap till end of the year.

@big_ted I did a quick check and observed the following.

1. If you set the stream mode to CLEAR for DUO 2 and log again, you won't have video but just audio. You need to set stream mode to FLUENT before quitting the DUO 2 live stream.
2. 
   
3. One cannot playback DUO 2 clips if set to CLEAR mode.
4. 
   
5. Changing from FLUENT to CLEAR in DUO 2 has no significance. Seems CLEAR is no longer available on DUO 2 from client's perspective.
6. 
   
7. In playback, no bar to move the video backward and forward.
8. 
   
9. Doorbell left in the 1:1 view. It should follow the others and should be stretched once the stretch option has been enabled.
10. 
    
11. Floodlight no longer supported.
12. 
    
13. Mode stream selection is not maintained when accessing camera outside its LAN. Stream mode selection works only when camera and PC are on the same LAN as client connects directly....This I can understand why.
14. 
    
15. Scheduler for the sensitivity has been added for motion only. This should be extended to cover all the object types. During the night the sensitivity has to be higher for pixel changes detection.

I will report them to the senior support. The issue of the CLEAR stream related to the DUO 2 has to do with some old libraries being used in the development (old MS C++ distribution packages, DirectX, etc) and is not in my notebook. In 4 years time this is the first time I encountered the issue of no video. Will troubleshoot it later on.

@micciche-matteo I have never came across any Reolink document on ONVIF implementation. Only the API doc was released to the public. You may submit your request to Reolink support.

@user_649233705312379_649233705312379 Try this https://support.reolink.com/hc/en-us/articles/360012466173-All-Reolink-Client-Versions/

If this is not the one you had then email support.

@reolink-cam_813700743893181 Most network surveillance camera streams are made up of I-frames and P-frames, I-frames are full image captures that record everything the camera is seeing and P-frames are the frames between the I-frames where only the elements of the image that are changing are refreshed.

To explain this with an example, if you had an empty corridor and someone walked down it the I-frame would capture the entire image and then the following P-frames would only capture the elements of the image that are changing, which in this case would be the person walking.

The idea behind this is that it is another way to compress the bitrate of the camera stream because instead of capturing 25 full-resolution images every second you are capturing one full image every 50 frames (e.g. 2 seconds) and then all the frames in between only capture what changes in the image and thus are much smaller files/use less bitrate.

Reducing the I-frame interval (25 frames, 10 frames, etc...) will obviously increase the bitrate/bandwidth used by the camera and is only really recommended if you are installing the camera in a very busy scene where having the full image refresh more regularly can improve image detail. Increasing the I-frame interval (75 frames, 100 frames, etc...) will decrease the bandwidth used and is only really recommended when covering scenes with little to no activity as you will see a drop in image quality and maybe even distortion to any movement that happens between the I-frames.

Now as regards the new fw, ensure you have the latest one cited in the Download center. I have the WIFI trackmix and the first fw released included ONVIF but at the expense of lower resolution at clear mode. In fact the colours appeared washed out. We have requested to restore max bit rate and fps and the definition is merely the say as the old fw. There are some issues on the new fw. Do a search on Trackmix fw and you shall find a thread on this.

@reolink-lorenz But there is no scheduler for the scene mode. I did request this to senior support. Hope that we will eventually see this implemented together with its status.

@jing_734911040270566 This is the norm with most suppliers. I used to patch equipment costing millions of bucks and no details were provided. Those were the days when you receive the details and the code changed (in assembly language). And fixing known bugs is the generic one. It's like the adhoc assignment in your job.

@mamymam2013_465350299701478 I am running 8.11.0 on Windows 10 and 11 and have no issues. However, I did have an issue with the latest version but I sorted it out myself.

Version 8.11.0 runs on Win 64bit architecture. I asked them to compile their new application for both 32 and 64 bit OS.