How this port works
The reference port runs on the T31X, the 128 MB member of Ingenic’s
T31 family. Other T31 variants use the same IMP SDK; their memory
sizes and sensor choices set the starting point for a product
integration.
The T31’s sensor, ISP and encoders are reached through Ingenic’s IMP
media SDK. CameraStack handles platforms like this with a C
producer: a compact native adapter, written in C against the IMP
libraries, that drives the vendor media pipeline from sensor to
hardware encoder and passes encoded video, motion events and object
observations to the portable core. There is no GStreamer dependency on
the device. ONVIF request handling, authentication, profile management,
events and RTSP delivery are the same portable core used on every other
platform. On the T31X, the whole stack runs on the single MIPS core
in the 64 MB of its 128 MB that is left to Linux, with the other
64 MB reserved for the media pipeline.
Video profiles
The T31 has two hardware encoders, a main stream and a substream, and
each can use H.264 Main or H.265 Main independently:
| Encoder | Resolution | Frame rate | Bitrate |
|---|
| Main | 2496x1440, 1920x1080 or 1280x720 | 25 fps | 512 to 4096 kbit/s |
| Substream | 640x360 | 25 fps | 256 to 1024 kbit/s |
Up to four ONVIF profiles share these two encoders, so a client can
create extra profiles without needing more hardware encoding channels.
Profiles attached to the same encoder use the same video settings.
Bitrate changes apply to the running encoder. A codec or resolution
change rebuilds only the selected encoding channel, while the sensor,
ISP and the other stream keep running.
Imaging, snapshots and OSD
The Imaging service operates the running ISP: brightness, contrast,
saturation and sharpness, automatic or manual exposure and gain,
automatic or manual white balance, and backlight compensation.
JPEG snapshots come from the hardware JPEG encoder at the selected
profile’s resolution. The OSD has four slots for text and date/time,
composed into both video streams and the snapshots, so they always
match.
Motion and person analytics
The Analytics service runs up to four ONVIF
MotionRegionDetector
polygons over the ISP’s statistics grid, with named region events and
an aggregate motion alarm. The same statistics, together with the
exposure settings, drive the ONVIF ImageTooDark tampering event.
Person detection
runs on the CPU’s SIMD instructions through Ingenic’s JZDL runtime, at
one or two inferences per second, using images from the existing
substream. Detected people are tracked with stable IDs by the shared
tracker and published as ONVIF scene metadata. The model package is
optional: a product can leave it out and keep video and motion events.
Built on the Ingenic IMP SDK
The producer builds against Ingenic’s IMP media SDK and the matching
sensor driver. The ISP, the two video encoders and the JPEG encoder
are driven directly through IMP, and the producer builds on the same
shared common core as CameraStack’s other custom-SDK platforms.
Bringing up another T31 product starts from its silicon
variant, sensor, SDK version and memory layout.