Since v3.0.0 beta 22 and also in beta 23, the windows bluecherry v3 client consistently fails to display two cameras from my V3 BC server. All other cameras on this server display fine in the windows client.
All cameras on the server, including these two display perfectly fine in the live view page of the servers web GUI and in the V2 windows client.
This has only started happening since v3.0.0 beta 22.
It should be of no consequence, but both of these cameras are older analogue cameras connected to an AXIS P7304 video encoder whereas all the other cameras monitored by this Bluecherry server are HIKVision or Dahua IP cameras.
I have attached two screen shots, one from the windows client and one from the live view client, both showing the two cameras for “WH 11 Inside Right” and “Warehouse 3 Rear”. I have also attached the log files from the windows beta 23 client.
I think it is the MDK rendering that is causing the issue.
I have two test PCs as follows:
One PC is running Windows 11 24H2 and has BC client 3.0.0.beta 22
The other is running Windows 11 23H2 and has BC client 3.0.0 beta 23.
Each system is configured to view the same BC server which is running BC server version 3.1.9 on a Debian 12 OS. The server is recording 18 cameras, three of which are analogue cameras connected to AXIS P7304 video encoders.
I believe that you changed the default rendering on the windows client from MPV (in beta 22) to MDK (in beta 23) to resolve a previous issue whereby the client would hang on startup or whenever a large number of cameras where first selected for display in the viewport. The change to MDK rendering did indeed resolve the hanging issue, however it has now created two additional problems, as explained below:
When the beta 22 client is running in normal mode without the --mdk flag, it still has the hanging problem, but after killing the BC client program and restarting it it will work OK and all cameras will display correctly. This includes the three analogue cameras on the encoders. The client also correctly generates log files for each camera which I have attached.
When the beta 22 client is started with the --mdk flag, it no longer hangs on startup, but is now exhibiting the same problems that I have with the beta 23 client where all three analogue cameras are not rendered and the client shows them as late or timed out. The other 15 cameras still display normally. A secondary problem is that when the client is started in --mdk mode, it does not generate any log files for the cameras, so unfortunately there is nothing for me to upload.
When the beta 23 client is started in normal mode without the --mdk flag, it also fails to render the video for the three analogue cameras and shows them as late or timed out. The beta 23 also, does not create any log files for the cameras, so again, I cannot upload any logs for you.
When the beta 23 client is started with the --mdk flag, it makes no difference and behaves exactly the same as described in point 3 above. The three analogue cameras fail to display and no log files are produced.
I have attached the log files that I could get, including the logs.txt files for each of the cases above. The only individual camera logs for the analogue cameras that I could get are from the working case on the beta 22 client.
