Once you have StreamShuttle installed and some cameras added, there are other things you may want to configure or adjust. The overall configuration can be broken down into a few different stages. Initial configuration, Break In Period, and Post Break In Period. Initial configuration takes place when configuring the cameras for the first time. The Break In Period is roughly the first couple weeks after the Initial Configuration, during this time you will may find that some settings may need to be tweaked, such as motion zones or alert settings. During the Post Break In Period, you probably won't need to change much unless the physical space a camera monitors is changed or new devices are added.
Unfortunately, the current trend with most of the off the shelf cameras is that they now require you to setup/configure them using their own proprietary apps. During the initial configuration will probably be only time you will need to use these apps, and after your system is configured and broken in you will most likely not even need them installed.
Although many of the device settings and adjustments we refer to can also be applied within StreamShuttle, it is usually best to set these on the device itself. In a perfect world, you will be able to utilize pass-through recording in StreamShuttle, meaning that we are storing the video directly "as-is" from the camera itself. This is ideal as it means there is less processing to do. If, for instance, we change the resolution, frame rate, or add a timestamp in StreamShuttle; then we have to also decode and re-encode the video which takes a lot more processing power. Simply making the adjustments on the device itself allows for the recordings to remain as pass-through.
The primary "performance" based settings we might consider are resolution, frame rate, and CBR vs VBR.
Another setting better set at the device is the video codec itself (H264 vs H265). Video codec is a specified file format used to compresses the video.
All new systems will have some type of break-in period. After a few days, you will also have a much better idea of the storage usage and general performance profile of the system. You will also start to become aware of potential quirks of your particular system.
For example, maybe there is a bush somewhere that always triggers motion because of the wind.
Maybe you notice one of the wireless cameras tends to have lot of restarts.
Perhaps one device is restarting because of timeouts.
After a few days of working with the new system and working through any quirks, you should be good to go! Now the system will be in more or less maintenance mode, allowing you to worry about what really matters.