I've painted myself into a corner, and the only way I'm able to get all 30 cameras to not saturate my i7 4770 CPU on windy/rainy days is to move most of them over to D2D.
One observation so far is that even with the "make" time set to 0.0 seconds, on many triggers, at least a full second has transpired before the recording actually starts. For example, a car entering the frame on the left, driving to the right will usually appear with half of the car cut off on the left side. That's plenty acceptable. However, on most of them, the car is more than halfway through the frame before it appears. Like magic. Nothing, then poof, there's a car in the middle of the screen.
I haven't tried using pre-buffering with D2D (don't even know if it'd work). I think what the problem is, is that when there are a lot of mini recording events (shadows in the wind, etc), each time a recording times out, it takes BI a second or so to finish writing that clip. If, during that clip ending period, a new event triggers a recording on that same camera, BI is busy, and won't start the new clip for several frames.
Thus, on a really quiet, motion-free day, each car is shown perfectly, edge-to-edge. But when there are a ton of stop/go recordings, the new clips are decimated by the previous recording session. I've not seen this when using regular xvid encoding.
Any ideas how to get around it with D2D, while not killing my CPU?
One observation so far is that even with the "make" time set to 0.0 seconds, on many triggers, at least a full second has transpired before the recording actually starts. For example, a car entering the frame on the left, driving to the right will usually appear with half of the car cut off on the left side. That's plenty acceptable. However, on most of them, the car is more than halfway through the frame before it appears. Like magic. Nothing, then poof, there's a car in the middle of the screen.
I haven't tried using pre-buffering with D2D (don't even know if it'd work). I think what the problem is, is that when there are a lot of mini recording events (shadows in the wind, etc), each time a recording times out, it takes BI a second or so to finish writing that clip. If, during that clip ending period, a new event triggers a recording on that same camera, BI is busy, and won't start the new clip for several frames.
Thus, on a really quiet, motion-free day, each car is shown perfectly, edge-to-edge. But when there are a ton of stop/go recordings, the new clips are decimated by the previous recording session. I've not seen this when using regular xvid encoding.
Any ideas how to get around it with D2D, while not killing my CPU?
