Best posts made by joseph_1979

@user_828616743243981_828616743243981 I will email their support team to request dev team to evaluate it.

@reolink-daisy Whenever I see members attaching screenshots with UID I immediately inform them to delete or hide the UID. IPs if they are private it's OK.

@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.

@williamjjames65_518880897646817 Viewing H.265 streams is handled by the client. Uninstall all old Reolink clients and re-install. If you get the same issue, try to install Redist DirectX.

@reolink-daisy Kindly go through our comments in thread https://community.reolink.com/topic/14545/trackmix-wifi

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

@williamjjames65_518880897646817 Client uses old DirectX dlls. So now you have client working on both OS. Note that if you use the client from an external network, viewing is always defaulted to fluent and you have to change it to clear. This is due to the P2P Relay server bandwidth offered by 3rd parties (Azure/AWS) and this is not infinite and free.

@big_ted In order to keep customers satisfied, Reolink should ensure synchronicity with the developments of each client.

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

@user_833789011820780_833789011820780 Do you encounter this when you are on the same network as the cameras? I did notice this when I am on 4G but when I am on the same WIFI I don't have the issue. So it seems to be a transport one.

@reolink-daisy Can we have the specs please?

@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.

@phirephoto_633457091563556 yes...in each channel to access individual cams.

@seb_526812765704330 I agree. I told them you need to be in synchronicity amongst all platforms. If you introduce a feature...make it available on all clients at the same time. FULLSTOP.

Yes, fw....we saw it once and then nothing. Not even the email subscription for fw upgrade has ever worked...at least to me. If not working then remove it. My sister has TAPO....if there is fw upgrade on any of the cameras she receives a notification on the client. This is fantastic and easily to implement. The playback is by far better. We are telling them where to improve but they don't listen to us.

@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.

@nzx resend email. Normally I receive a reply within 48 hours.

@big_ted wholly in agreement. This is way far from professionalism.

@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.

@kylimo_837175850053876 what do you mean by pictures? Can you paste a screenshot?

@reolink-oskar Finally we see the DUO floodlight in 4K. This should be more than welcomed by the customers.