For our users, the time it takes to launch the Windows app and load/buffer the initial camera(s) can vary wildly, but sometimes exceed 20 seconds. This doesn’t seem like long, but between the inconsistency and length, we sometimes wonder if it’s going to work. What is the source of the loading times, and is there anything we can do to speed it up?
Hello! Can you try to download the client from our bleeding edge release?
This issue should be fixed there. If that doesn’t fix the issue, please attach the log files. You can find the log file under Settings > Advanced Options > Open Log File.
See BC Client 3.0.0-beta21 hangs on startup - Client discussion - Bluecherry
Installed the bleeding edge client and launched the app. It took 17 seconds to launch and display the live feeds from 4 cameras. The log only has two rows from today:
[2025-03-25T12:53:30.832838] App working directory: C:\Users\[redacted]\AppData\Roaming\com.bluecherry\Bluecherry Client
[2025-03-25T12:53:31.364848] Opening app with []eoPlayerMediaKitInterface video playback
The app launched quickly. I think the majority of the 17 seconds was buffering/loading the 4 live feeds.
Hello, any further thoughts on how to reduce time to viewing cameras? Or, is @ 20 seconds the norm?
Can you try this:
Try opening the client with the --mdk flag?
Hello. I tried the --mdk option. The bottom right Loading badge appeared for a much shorter amount of time for all 4 cameras. However, 2/4 cameras showed Live but with only a black screen for several seconds. The other 2 cameras showed Timed Out for several seconds before showing a live feed. In all, the time to showing 4 live feeds was actually about 7 seconds more after doing a couple rounds of testing.