Wht is the price of room composit recording? Vs recording single track screen share ?

Thanks for reaching out, Mostafa. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

I want to record screenshare only what is the cheapest way?

Thanks — I’m replying about the cheapest way to record screen share only. Short answer: • Use Track Egress to export the screen‑share track. This is the most cost‑effective option and is billed at $0.001 per minute for track egress recordings. Why this is cheapest: • No transcoding/muxing overhead: Track Egress exports a single track directly, avoiding the heavier compute required by room or composite recordings. • Selective export: You record only the screen track (no other participant audio/video), which reduces storage and egress usage. • If you pair screen capture with WHIP ingress, you avoid extra transcoding on ingest as well, further reducing costs. Other options (more expensive): • Track Composite or Room Composite render and/or mix tracks into a single file and require transcoding — billed at higher per‑minute rates (room composite starts at $0.02/min; lower rates available at scale). If you want, tell me: • Whether your screen share is H.264 or VP8 (or how it’s being sent), and • Where you want the file stored (S3, local, etc.), and I’ll give exact Track Egress settings and a simple example command/payload to start the export. Sources: Universal Egress | Universal Egress | Pricing | LiveKit | Understanding and Estimating Pricing for Video Conference and Livestream Us...

Whip egress what is that?

Thanks — you asked “Whip egress what is that?” I’m replying about WHIP and how it relates to recording/egress. Short answer: • WHIP is an ingress protocol only. WHIP is used to send a media stream into LiveKit (e.g., push a browser screen share into a room). • There is no “WHIP egress.” Egress means exporting or recording media out of LiveKit, and that is handled by LiveKit’s egress features (Track Egress, Track Composite, Room Composite), not WHIP. Quick details: • WHIP Ingress: Use when you want an external source (a browser, encoder, or third‑party publisher) to push a live stream into a LiveKit room. It’s how you get the screen‑share into LiveKit from outside the normal WebRTC session. • Egress (recording/export): Use Track Egress to export a single screen‑share track (cheapest option), or Track/Room Composite if you need mixed/composited files or multiple tracks. These are LiveKit’s export/recording mechanisms — WHIP isn’t used for exporting. If you want, I can: • Walk you through a simple flow to send a screen share into LiveKit via WHIP Ingress and then start a Track Egress to record only that track, or • Provide the Track Egress request payload/command you’ll need to record the screen share to S3 or an MP4. Which would you like me to show? Sources: Python SDKs | livekit/livekit_composite | DeepWiki | Universal Egress

For scale plan what is the price for composite and single tracks?

Thanks — you’re asking for Scale plan pricing specifically for composite recording and single‑track recording. Here are the numbers and a couple of quick notes. • Room Composite (composited recording): $0.015 per minute on the Scale/Enterprise tier. • Single track (Track Egress): $0.001 per minute. Notes: • Room Composite uses a browser compositor and is billed as transcoding minutes, which is why it’s more expensive. • Track Egress exports an individual track (e.g., a screen‑share) with minimal processing and is the lowest‑cost option for single‑track recording. • Your plan may include some free/included minutes depending on tier — those included minutes would offset billed minutes. If you’d like, tell me how many minutes per month you expect to record (composite vs. track) and I’ll estimate a monthly cost for each approach.