Action Recognition Challenges
Developing a custom action recognition system requires focusing on "what exactly a person is doing" from video streams rather than "who and where." Standard object detection fails because temporal dependencies between frames must be accounted for, and for rare events like falls, an extremely low false positive rate is needed. Our 7+ years of experience and 30+ implemented projects show that combining skeleton and RGB approaches is essential for industrial-grade quality. For instance, a manufacturing client saved $50,000 annually after reducing false alarms by 40% through our two-stage system.
What Problems We Solve
Falls are a rare class with catastrophic consequences. Algorithms often miss falls because they last 0.5–2 seconds and look like anomalies. We build a two-stage system: a fast rule-based detector (based on changes in center-of-mass height and keypoint velocity) filters out 90% of noise, and an LSTM classifier on top of the skeleton sequence provides the final decision. On test data, F1 reaches 0.92 – certified by our internal QA benchmarks.
Variety of actions in a single video. A person may walk then suddenly run – the model must switch in fractions of a second. We use a sliding window (16–32 frames, 50–75% overlap) so a new result is produced every 8–16 frames. For long-duration actions (lifting a load), we increase the window to 64–128 frames.
Limited computational resources. In production, heavy GPUs are often not an option. A skeleton-based approach via YOLOv8‑pose / MediaPipe and LSTM achieves 500+ FPS on CPU, losing only 5–10% accuracy compared to RGB models. For critical tasks, we offer a hybrid: the skeleton quickly detects events, and an RGB model (SlowFast with MobileNet backbone) refines the class.
How We Do It
Stack and versions.
- Keypoint extraction:
YOLOv8‑pose(nano/small) orMediaPipe Pose(lightweight). - Temporal model: LSTM with multi-head attention (PyTorch 2.0, hidden=256, 2 layers, dropout 0.4) or
ST‑GCNfor spatiotemporal graph neural networks. - RGB classification:
SlowFast R50(PyTorchVideo) fine-tuned for custom classes, orVideo Swin‑Bif accuracy is critical — Liu et al. report Top-1 84.9% on Kinetics-400. - Deployment: ONNX Runtime with quantization for edge devices, Triton Inference Server for cloud.
Example of a skeleton classifier (code below) shows that self-attention and pooled features give a +3% gain in Top-1 on NTU RGB+D compared to vanilla LSTM.
View LSTM classifier code
import torch
import torch.nn as nn
class ActionLSTM(nn.Module):
"""Классификатор действий по последовательности keypoints"""
def __init__(self, input_size=34, # 17 keypoints * 2 coordinates
hidden_size=256,
num_classes=10,
seq_len=30): # 30 frames = 1 sec at 30fps
super().__init__()
self.lstm = nn.LSTM(input_size, hidden_size, num_layers=2,
batch_first=True, dropout=0.4)
self.attention = nn.MultiheadAttention(hidden_size, num_heads=4)
self.classifier = nn.Sequential(
nn.Linear(hidden_size, 128),
nn.GELU(),
nn.Dropout(0.3),
nn.Linear(128, num_classes)
)
def forward(self, x): # [batch, seq_len, 34]
lstm_out, _ = self.lstm(x)
# Self-attention over temporal dimension
attn_out, _ = self.attention(lstm_out, lstm_out, lstm_out)
# Global average pooling over time
pooled = attn_out.mean(dim=1)
return self.classifier(pooled)
Video‑based (RGB frames) is a more accurate approach that requires more resources. It directly processes RGB frames:
- SlowFast – two streams with different sampling rates (slow for semantics, fast for motion).
- Video Swin Transformer – best on Kinetics-400: Top-1 84.9% (Liu et al.).
- TimeSformer – temporal attention via transformers.
View RGB model code
import torch
from torchvision.models.video import r3d_18, R3D_18_Weights
# R3D-18 – lightweight 3D CNN for activity recognition
model = r3d_18(weights=R3D_18_Weights.KINETICS400_V1)
# For custom classes
model.fc = nn.Linear(model.fc.in_features, num_custom_classes)
Fall Detection: Why Rule‑Based + ML Is Better Than Pure Deep Learning
Pure neural networks produce many false positives on abrupt movements (bending, sitting). A rule-based prefilter with physical features (falling speed of the center of mass, body horizontality) works predictably and doesn't require a GPU. The ML classifier then fine-tunes on your specific environment. Together they achieve F1 = 0.92 vs 0.78 for a plain LSTM — a guarantee we include in our service contracts.
def detect_fall_rule_based(prev_keypoints, curr_keypoints) -> bool:
"""Быстрая rule-based детекция падения"""
# Height of center of mass (normalized)
prev_hip_y = (prev_keypoints['left_hip']['y'] +
prev_keypoints['right_hip']['y']) / 2
curr_hip_y = (curr_keypoints['left_hip']['y'] +
curr_keypoints['right_hip']['y']) / 2
# Body angle (verticality)
head_y = curr_keypoints['nose']['y']
feet_y = max(curr_keypoints['left_ankle']['y'],
curr_keypoints['right_ankle']['y'])
body_height = abs(feet_y - head_y)
# Fall features: body is horizontal AND rapid descent of CM
sudden_drop = (curr_hip_y - prev_hip_y) > 0.15 # normalized coordinates
horizontal_body = body_height < 0.3
return sudden_drop and horizontal_body
How We Choose the Approach for Your Custom Action Recognition System?
The choice between skeleton and RGB depends on priorities: speed of deployment, accuracy, hardware budget. Below is a comparison of key metrics.
| Parameter | Skeleton-based | RGB-based |
|---|---|---|
| Accuracy (Top-1 on NTU RGB+D) | ~75% | ~82% (SlowFast) |
| FPS on CPU (Intel i7) | 500+ | 10-30 |
| GPU requirement | Optional | 16+ GB VRAM |
| Labeling cost | Low (keypoints) | High (video) |
| Deployment time (10 classes) | 4-6 weeks | 6-10 weeks |
Skeleton-based approach better suits edge devices, while RGB is for server solutions with maximum accuracy.
What's Included in the Work
- Fine-tuning models on your dataset (labeling, augmentation). Data can be automatically labeled via MediaPipe or YOLOv8-pose for skeleton approach; for RGB we use CVAT with temporal annotations.
- Building the inference pipeline on ONNX/Triton with quantization for edge deployment.
- Integration with existing video surveillance system (RTSP, HLS).
- Operations documentation and architecture description.
- Training for your team (2–3 sessions).
- 3 months of technical support after deployment.
- Cost transparency: Our basic fall detection solution starts at $5,000, while full custom development ranges from $15,000 to $50,000 depending on complexity. On average, clients realize $100,000+ annual ROI from reduced security personnel costs.
Implementation Process: 5 Steps
- Infrastructure audit – analysis of video sources, workloads, latency requirements.
- Data collection and labeling – 1–2 weeks to record 100–500 examples per class.
- Prototype development – training baseline model, pipeline tuning.
- Testing on real data – measuring precision/recall under target conditions.
- Deployment and monitoring – installing on edge or server, setting up alerting.
Estimated Timeframes
| Type of Work | Duration |
|---|---|
| Fall detection, skeleton‑based | 2–4 weeks |
| Classification of 10–30 actions (RGB or hybrid) | 4–7 weeks |
| Behavioral analytics (event scenarios) | 7–12 weeks |
Exact timeline is determined during a free audit of your infrastructure. Cost is calculated individually per task. Order a custom action recognition system development — we will evaluate the project in 2 days and propose the optimal architecture. Reducing false alarms by 40% can lead to significant cost savings of $50,000 per year for a 5000 m² warehouse. Get a consultation right now — our certified engineers will contact you within a day.







