TRTC vs Agora in TiLive Recording
Live apps can use different real-time media providers. TiLive rooms may expose TRTC-style metadata or Agora-style metadata, and a serious recorder must handle both paths.
Why HTTP links are not always enough
Some lives expose HLS, FLV, or other HTTP-playable URLs. Those are straightforward for FFmpeg.
Other lives expose real-time RTC metadata. In that case the recorder must join the media session with the right parameters instead of guessing a fake CDN URL.
TRTC and Agora need different runtime handling
TRTC and Agora sessions do not look identical. They can have different app IDs, channels, users, signatures, tokens, and stream identities.
TiLive keeps those paths separated so one provider fix does not break the other.
What users should notice
Ideally, nothing. The bot should say that recording started, then deliver the final MP4 after the live ends.
The transport details are operational details for reliability, not steps the Telegram user should have to manage.
Use the same /rec and /watch commands; TiLive chooses the recorder path behind the scenes.
Open @tiliverec_bot