When entering full screen mode, currently the only way to exit this mode is by pressing the ESC key.

My Windows 10 touch screen tablet has no keyboard hence if have no way to exit full screen mode.


Hence request that the developers should in a future release to include a method to exit full screen mode when using a touch screen device.

I suggest to add a small touch button in the lower right corner of the screen where there are existing touch buttons for taking screen shots etc, and program the new button with the ESC function. Quite a simple task for the software developer team.

@joseph_1979 I am also going to roll back to the previous version.

There is an intermittent issue when using playback. Sometimes when trying to return to live view, I see a large play arrow on the centre of the screen rather than the live video view. For me the only way to recover is to re-boot the software.

Unsure why, has now happened twice for no apparent reason.

@joseph_1979 There is a more recent Windows Client release, the build date for Reolink.exe is 26th Feb 2025.

The version number has been bumped up to 8.18 series.

This latest build seems to be currently on restricted release. I was offered the update last week when running the existing client on my laptop.

The release seems to be quite robust, the software bug that I reported some months back has been fixed.

@reolink-daisy Reporting an observed software bug with Version 8.17.6

Inspecting the System Status I see the following entries

System Status

{sniped text}

(0)0: current dir C:\Program Files\Reolink\Reolink.exe
(0)89: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)773: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)795: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)595: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)721: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)1344: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)1344: open C:\Program Files\Reolink\MediaDiagnose.log fail Permission denied
(0)1344: Render Success 2560x1920 0xae

{sniped text}

My understanding is that it is better to save log files to a location that is not located in the C:\Program Files\ sub directories because this folder tree is typically read only during program execution to minimise the risk of viruses adding their code if the read access is changed to read/write access.

I think most programs use the location C:\ProgramData to store runtime writable files such as log files.

@user_703835435114728_703835435114728

Question - Which of the two Junction boxes is the camera compatible with.

@reolink-fiona Do you have any details regarding the in focus depth of field for this sensor + Lens + Aperture combination.

I ask because I currently use another Reolink camera mounted quite low down to record nighttime wildlife and the animals can be quite close to the camera.

Hence requesting the nighttime distance from the camera where the subject will be in reasonably good focus.

@user_646203682046022_646203682046022 I have tried to mimic this behaviour with my laptop because it also has Intel UHD GPU 0 and Nvidia Quadro GPU 1.

I have tried running with the four video option combinations of GPU 0, GPU 1 both with and without Hardware Decoding First.
I think your setup is similar to mine with video running through the Nvidia Quadro with Hardware Decoding First, a good choice to allow the better video chip to take the load away from the CPU.

And on my machine there does not appear to be a memory leak. Note that I connect directly to four cameras and not through an NVR.
Also I have the latest Nvidia drivers installed.

@joseph_1979 I just had a thought regarding the local copies of the VC++ library files.

One way to force the client to use the system VC++ library files would be to move the local library files out of the client folder tree. I have just done this and the program still seems to work OK indicating either that

1. the client has always used the system libraries or
2. that moving the local copies has forced the client to use the system libraries.

Note that I needed to have administrator privileges to move the files

Importantly the client still works with the three files moved hence I think is safe for the users who have the pop up issue to try.

1. Shut down the Reolink Client
2. I moved out of the folder C:\Program Files\Reolink\resources\app and into another temporary folder location on my desktop the following files
3. msvcp140.dll
4. vcruntime140.dll
5. vcruntime140_1.dll

Then re-started the client

Unsure if this will fix the pop up issue because I do not see the issue with my machines

@joseph_1979
Checking deeper today, I think the client does use Microsoft Visual C++ libraries because I have found a local copy of them in the clients folder tree which are probably the versions being used by the client.

C:\Program Files\Reolink\resources\app

An interesting observation if these are the actual dll's being used by the client - there is a version mismatch with the three files which could easily cause many of the reported instability issues.

msvcp140.dll Time Stamp 11th Feb 2021 version 14.28.29910.0
vcruntime140.dll Time Stamp 11th Feb 2021 version 14.28.29910.0
vcruntime140_1.dll Time Stamp 5th Oct 2022 version 14.34.31931.0

@joseph_1979 You state that "It must be the C++/dll library."

I have the 8.10.4 client running on three different computers and the playback date/calendar works on all of them.

Now.... one of them does not have the Microsoft Visual C++ libraries installed on it.

Hence your statement is incorrect, the C++ libraries are not used by the Reolink client, the client is using some other libraries which are not based on Microsoft Visual C++.

You can easily prove this by uninstalling the C++ 64bit library and then see if the client still works.

@robert-hammond_315369854550200 Replying to my own post.

I think I have my latest replay the wrong way around.

The page size in the top right hand corner:-

1. When the two overlapping squares are shown, the program is running in full screen mode. And in this mode it seems to function correctly.
2. When the single square is shown the program is supposed to be running in a mode that is smaller than the screen size. But for some strange reason the program runs larger than the complete screen.

Investigating..... and will post again when I have had some time to experiment with screen settings.