Camera Recording Schedule Setup in Richmond, TX 77406

What a recording schedule is actually deciding

Most systems leave the factory recording every channel around the clock at whatever bitrate the manufacturer chose. That is a default, not a decision — and it is why so many households discover, on the one morning it matters, that the oldest footage on the box is nine days old.

The schedule is the single control surface for four things people normally treat as separate:

• Coverage window. Which hours each individual channel writes anything at all.
• Trigger. Whether it writes continuously inside that window, or only when something crosses a defined area.
• Retention. How many days survive before the oldest hour is overwritten by the newest.
• Searchability. Whether an incident is tagged as an event you can jump to, or buried in an unbroken ribbon of empty driveway.

Move one and the other three move with it. Setting every camera to continuous 24/7 feels cautious; in practice it drops your history to a week and leaves you dragging a playback bar with your thumb at six in the morning.

The arithmetic behind “thirty days”

Storage is not mysterious, and the calculation is worth doing before anyone argues about settings. It is one multiplication:

Worked through with stated assumptions: a 4 MP camera at 4 Mbps puts down about half a megabyte every second, roughly 1.8 GB an hour, close to 43 GB over a full day. Eight of those recording continuously land near 350 GB per day, so a thirty-day target wants something on the order of 10 TB of usable space before any headroom. A single 4 TB drive — the size a great many systems shipped with — gets you eleven or twelve days of that, not thirty.

Now change one variable. Four of those eight watch areas where nothing moves for most of the day: a side yard, a back fence, a garage interior. Put those on event recording and their write time collapses to a fraction of the day while the four facing the street and the doors stay continuous. The same hardware reaches the target without a drive purchase. Decide the number of days first, then spend storage where a continuous record genuinely beats an event clip.

Continuous, event-driven, or a schedule that switches between them

Every recorder we work on supports at least three behaviours, and good configurations use all of them on different channels at different hours.

The mix is the one people skip and usually the one that solves the problem. A driveway channel running continuously from late afternoon to sunrise and dropping to event recording during the workday holds a far longer history than the same camera pinned to 24/7, with no loss of the footage anybody actually asks for.

Codec, bitrate mode, frame rate: three settings that quietly rewrite your timeline

Before buying a disk, check what the encoder is doing, because the same scene can be written at very different cost.

H.265 against H.264. H.265 typically produces a similar-looking picture at roughly half the bitrate, though the real saving depends on scene complexity — a still garage compresses beautifully, a tree line in a gusty north wind does not. Some older recorders and third-party viewers will not decode it, so it is a check rather than an assumption.

Smart or “plus” variants. These hold a static background across a long stretch of frames and spend bitrate only where pixels change. The saving is real; the trade is a much longer gap between full reference frames, which can make exports awkward for outside software and smear a fast subject at the moment you most want it sharp.

Bitrate mode and frame rate. Constant bitrate makes planning trivial because every hour costs the same, while variable is efficient but spiky enough that a thunderstorm can hold a channel at its cap for hours. Fifteen frames per second suits a general area view; below about twelve, moving subjects skip in a way that hurts exactly the frames you would want to freeze.

Overwrite, drive health, and the failure nobody notices

A schedule is only as real as the disk underneath it, and this is where we find the most damage on systems set up once and never revisited.

• Overwrite left off. Set to stop rather than loop, the recorder quits writing the day the disk fills. Live view looks perfect. Months of nothing.
• A desktop drive in a surveillance bay. Ordinary computer drives are built for bursts, not many streams written every second forever, and their error-recovery behaviour drops frames rather than returning a read error. Surveillance-rated drives carry a stated annual workload figure for this duty.
• A channel never added to the schedule. Camera online, image perfect, not one second on disk — common where a camera was added after the original install.
• Disk alerts configured nowhere. Most recorders can warn you about a failing drive, but only if somebody set it up.

We read the disk’s health and accumulated write hours before recommending any purchase. Quite often the schedule, not the hardware, is the entire problem.

Why a 77406 driveway fills a disk faster than you would guess

West Richmond is largely newer master-planned ground: long straight collector streets, two-storey brick and stone elevations set well back from the kerb, deep driveways, generous spacing between lots. That geometry has direct consequences for a motion schedule.

• The street sits inside your frame. A camera at the garage looking down a deep driveway sees traffic beyond the kerb line. On a collector street near school release that is a vehicle every few seconds — motion recording quietly becomes continuous recording and nobody chose it. The fix is an activity zone ending at the kerb plus vehicle and person classification, not a lower sensitivity.
• Build-out is still moving through. Parts of 77406 still see trade trucks and deliveries all day on streets that will be quiet in three years, so a schedule set now deserves a review once that passes.
• Large open back yards. Sprinkler heads at dawn, pool service, and unshaded ground producing heat shimmer through a long afternoon all register as motion on a rear camera aimed across open lawn.
• Acreage toward the west and the river bottoms. Longer driveways, a gate camera a considerable distance from the recorder, and real night wildlife traffic — these nearly always want a different mode on the gate channel than on the house.
• Storm-season interruptions. A brief outage restarts the recorder; the schedule survives, but a system with no battery protection loses the minutes around the event, which are sometimes the interesting ones.

What EVOTECH does on a recording schedule call

1. Ask the question that governs everything else: how far back do you need to go, and why that number.
2. Read the recorder — model, firmware, channel count, installed disk, health and accumulated write hours.
3. Pull the current schedule for every channel and show you what it is really doing, which is often not what the previous setup believed.
4. Watch each live scene for repeating motion sources, then set activity zones and detection classes so triggers fire on people and vehicles rather than shadows and traffic.
5. Assign a mode per channel and per time block, including any gate or door contact that can start a recording directly.
6. Set bitrate, codec and frame rate to hit the retention target, then recalculate rather than guess.
7. Enable overwrite, switch on disk and video-loss notifications, and point them somewhere a human will see them.
8. Return to the timeline once it has run and confirm the day count landed where we said.
9. Walk you through exporting a clip yourself — the skill you will need under pressure.

Every visit starts with a free on-site estimate and an itemised written quote before work begins.

What moves the scope of the job

We do not quote a figure over the phone for this, because the variables differ house to house. What changes the scope:

• Channel count — eight cameras is a different afternoon from thirty-two.
• Whether the existing disk meets the target, needs a companion, or is failing.
• Whether the equipment supports person and vehicle classification or only raw pixel motion, which decides how much zone work is needed.
• Mixed-brand systems, where one recorder carries cameras from several manufacturers with different capability sets.
• Firmware far enough behind to be missing scheduling features, and whether updating is safe on that model.
• Whether a camera must be re-aimed before a workable zone is possible at all.
• Remote viewing, notification routing and multi-user access, if you want those set up while we are there.
• Site access — gated entry, a recorder in an awkward closet, an attic run to reach it.

The numbers come in writing, itemised, after we have seen it.

The configuration mistakes that bring us back out

• Sensitivity cranked to maximum. It does not find more real events, it finds more grass. Sensitivity is the crude lever; zones and object classification are the precise ones.
• One schedule copied to every channel. A garage camera and a camera facing a public street have nothing in common.
• Zero pre-record buffer. Recording that begins at the trigger instant gives you a subject already at the door with no approach.
• Main stream only. With no sub-stream, phone playback over a mobile connection stutters and people conclude the system is broken.
• A retention target nobody rechecks. Foliage changes, the encoder spends more, and thirty days becomes eighteen without a single alert.
• An untested export. The first attempt to hand a clip to an officer should not be the first attempt anyone has made.

Related services

Frequently asked questions