Posts made by Robert Hammond_315369854550200

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

@joseph_1979 The page full screen button in the top right hand corner.

When the Square is shown, the program is running full screen, if two overlapping squares are shown then the program is running in a mode that does not completely fill the screen.

Reporting an observed bug.

My 10 inch laptop has Intel UHD Graphics 600
driver dated 26/02/2022
version 30.01.101.2079
resolution 1920 x 1200



Observation....
If I close the new Beta full screen, when I re-start the program the very right hand side of the screen is missing (see attached jpg from my low down garden cam).

If I close the new Beta not on full screen, then when i re-start the program the screen works correctly when changed to full screen.

@joseph-chircop_497308027822318
RLC-811A
RLC-410-5MP
RLC-410-5MP
RLC-1220A

All with their latest firmware's. Note that the 811A (Camera 1) is a new camera that I only received and setup some days ago, replacing a RLC-511 which I plan to use at another location when the weather improves.

A very strange message because the recordings are clearly shown in the recording timeline and can be played back once the message is cleared.
Today the message no longer displays before playback.

Reporting another issue where I am getting the following message display with all of my cameras. After I clear the message the Playback function works as expected. All of my cameras support playback.

I have decided to revert back to version 882 because I really need the full screen option which is not available with this beta, but unfortunately version 882 will no longer install after uninstalling this beta. Seems that installing 810 beta has changed something somewhere. Hence requesting for some help from Reolink to post up a reply to this message with details of how to revert back to version 882.

On two separate Computers, sometimes when starting v8.10 Beta it will freeze during startup and when left for a short period will display the attached message. Note that the program will load correctly on the second attempt.

Question...
Does the Beta save any debug logs that I could forward after this happens.

Robert

With the Client Version 8.7 Beta

The live camera view defaults to Standard view (which I think is the same as Fluent). And I can change the camera view to Clear by right clicking on the live image. This setting change will remain while the client is running.

My recollection with the previous client version was that after changing the live view to Clear, this setting change would be saved so that when starting the client after shutting down, the client would boot the live view to Clear.

Observation with 8.7 Beta - changing the live view to Clear is not save after a client re-boot.

@robert-hammond_315369854550200

Replying to my own post.

The full screen mode can be quite complex if you display multiple cameras.
So suggest a simple way forward would be to program using a 'Double Tap' to exit full screen mode on touch screen devices

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.

I have some experience.

Some time back I spotted a youtube product comparison that seemed to show the the RLC-1220A had very good night vision so I purchased one to use for my low down Badger Cam project. I have it mounted about 50cm above ground level and have configured with the supplied 850nm IR function turned off.

I supply the 940nm IR lighting using an illuminator that I purchased on line and seems to be reasonably successful.

Currently the streaming video has a dark shadow away from the light source because the illuminator is mounted higher than the camera.
When I get time my plan is to have two illuminators, one each side, each with a variable voltage control to minimise over exposure.

Hello Cynthia

I have also been trying out the 8.0.5 beta on both my PC and also a Windows 10 touch screen tablet.

It is normal practice when debugging beta software for the software developers to use feedback gained from forum postings posted by the wider user community so have posted to this particular message thread. I hope that your software developers monitor the forum.

I would like to report two software problems with this version.

1. The first issue is due to running the software on a windows 10 32 bit touch screen device that does not have a keyboard.
If I expand the video screen using the double arrows in the bottom right corner, I cannot then exit this mode because the exit method involves pressing the Esc key but a touch screen device has no Esc key. Perhaps your software developers could incorporate using a double screen tap or some other method for exiting full screen mode when using touch screen devices.

2. The second issue, I can adjust the motion alarm sensitivity but there is no way to save the setting. The sensitivity setting reverts back when the settings page is closed hence a relatively major issue.

Regards Robert