The short answer
These three settings affect different parts of image detail, motion and load. Change one at a time and measure the moving scene rather than treating a bigger number as universally better.
Work through the checks
Write down the exact outcome you need: live observation, a saved event, camera movement or long-term retention. Check each outcome separately instead of treating a visible stream as proof of all functions.
Lower one camera parameter at a time: frame rate, resolution or bitrate. Re-test motion and readable detail; a lower idle bitrate alone does not prove a usable moving image.
Observe CPU, GPU, memory and network use in Windows Task Manager with one view, then add views gradually. Record the point where playback begins to lag.
Estimate decimal GB per day as total Mbps × 10.8, then multiply by days and recording duty cycle. Add practical headroom and measure real files because variable bitrate changes with motion.
What to verify
Show a visible changing clock or a supervised movement in the camera scene, then compare it with the live image. Use the same source and layout for each latency comparison.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.