ESPHome 2026.11.0-dev
Loading...
Searching...
No Matches
esphome::rtsp_server Namespace Reference

Data Structures

struct  JpegInfo
 The fields of a JPEG frame that an RFC 2435 RTP/JPEG payload needs. Pointers refer into the frame. More...
 
class  RTSPServer
 
class  RTSPSession
 A single RTSP client: one TCP connection carrying both the RTSP control channel and, once playing, RTP/JPEG media interleaved on the same socket (RFC 2326 ยง10.12). More...
 

Functions

 ESPHOME_LOG_TAG (TAG, "rtsp_server")
 
bool parse_jpeg_info (const uint8_t *data, size_t len, JpegInfo &out)
 Scans JPEG marker segments (SOF0/1, DQT, SOS) for the dimensions, quantization tables and the start of the entropy-coded scan data.
 

Function Documentation

◆ ESPHOME_LOG_TAG()

esphome::rtsp_server::ESPHOME_LOG_TAG ( TAG ,
"rtsp_server"  )

◆ parse_jpeg_info()

bool esphome::rtsp_server::parse_jpeg_info ( const uint8_t * data,
size_t len,
JpegInfo & out )

Scans JPEG marker segments (SOF0/1, DQT, SOS) for the dimensions, quantization tables and the start of the entropy-coded scan data.

Assumes the standard Huffman tables (true for esp32-camera), so DHT segments are not parsed; receivers rebuild them per RFC 2435. Only three-component 4:2:2 or 4:2:0 frames without restart markers (DRI) can be carried as RFC 2435 types 0 and 1; anything else returns false.

Definition at line 73 of file rtsp_session.cpp.