From a19551540fa18950ed999b23fac1e2469275a588 Mon Sep 17 00:00:00 2001 From: winlin Date: Fri, 4 Jul 2025 08:39:23 -0400 Subject: [PATCH] AI: Update enhanced-rtmp spec for augment code. --- .augment-guidelines | 19 +++++++++++++++++++ .augmentignore | 2 +- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/.augment-guidelines b/.augment-guidelines index e6facd4e9..5e250537c 100644 --- a/.augment-guidelines +++ b/.augment-guidelines @@ -72,6 +72,25 @@ code_patterns: - pattern: "#ifdef SRS_VALGRIND" description: "Valgrind support" + codec_handling: + enhanced_rtmp: + description: | + For HEVC and other new codecs in RTMP/FLV protocols, always use enhanced-RTMP codec fourcc instead of legacy RTMP codec IDs. + Enhanced-RTMP provides better support for modern codecs and is the preferred approach. + NOTE: This guidance applies ONLY to RTMP/FLV protocols, not to other protocols like SRT/WebRTC/WHIP/WHEP/HLS/DASH/GB28181. + + hevc_codec: + - pattern: "fourcc: hvc1" + description: "Use enhanced-RTMP fourcc 'hvc1' for HEVC codec identification in RTMP/FLV" + usage: "Always use fourcc 'hvc1' for HEVC instead of legacy RTMP codecid(12)" + rationale: "Enhanced-RTMP fourcc provides better codec identification and compatibility" + + general_rule: + - "Do NOT use legacy RTMP codecid(12) for HEVC" + - "Always prefer enhanced-RTMP codec fourcc for new codecs" + - "Use fourcc format for codec identification in enhanced-RTMP contexts" + - "This applies ONLY to RTMP/FLV protocols - other protocols use their own codec identification methods" + build_and_development: build: command: "make -j" diff --git a/.augmentignore b/.augmentignore index 5a594ec58..8fffa4b24 100644 --- a/.augmentignore +++ b/.augmentignore @@ -19,7 +19,6 @@ **/*.ts # 3rd party libraries -**/vendor/** **/3rdparty/ffmpeg-4-fit/** **/3rdparty/gperftools-2-fit/** **/3rdparty/gprof/** @@ -32,6 +31,7 @@ **/3rdparty/srt-1-fit/** # Research files. +**/tools/** **/research/** # Other files.