Blance FPS & resolution with bitrate (IP2M-842E)
Posted: Wed Jul 20, 2016 9:12 pm
Using B.I. as the software package, I am trying to balance the frames per second (FPS) and the resolution while balancing the bandwidth & CPU requirements.
If I max it out, the PC (Dual Dore Win7 6GB RAM) has a hard time to keep up with 2 cameras. My home internal network is all GB, the cameras are PoE (100MB), no Wi-Fi in use for any of this (yes I have Wi-Fi but not for this application).
At 720P resolution and 20 FPS with a 1024 bit rate, it works well but at 40' distance, I zoom into a license plate, I cannot read it.
So I need the 1080P mode to get that resolution detail but at 20-30 FPS, it is crushing to the PC.
So I have dialed it down to 15 FPS & 1024 bit rate VBR Quality level "4" (max 6) "640-6144Kb/S" Reference Bit Rate (unclear what that means). I also set it to just H.264 (not 264B or 264H). I have an Intel CPU, so the hardware decoding is supposed to assist.
So other than throwing it up against the wall to see if it sticks, is there a best practices cheat sheet kicking about?
If I max it out, the PC (Dual Dore Win7 6GB RAM) has a hard time to keep up with 2 cameras. My home internal network is all GB, the cameras are PoE (100MB), no Wi-Fi in use for any of this (yes I have Wi-Fi but not for this application).
At 720P resolution and 20 FPS with a 1024 bit rate, it works well but at 40' distance, I zoom into a license plate, I cannot read it.
So I need the 1080P mode to get that resolution detail but at 20-30 FPS, it is crushing to the PC.
So I have dialed it down to 15 FPS & 1024 bit rate VBR Quality level "4" (max 6) "640-6144Kb/S" Reference Bit Rate (unclear what that means). I also set it to just H.264 (not 264B or 264H). I have an Intel CPU, so the hardware decoding is supposed to assist.
So other than throwing it up against the wall to see if it sticks, is there a best practices cheat sheet kicking about?

