place.stream.media.track
A track for a video stream, either part of the source or a custom additional track. One of: video, audio, subtitles.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | media.stream.place |
| Indexed |
Record
record · key tidProperties
metadata
unionparentTrack
refIf this is a derived track like a transcode or a transcript, what was the parent track?
video
string · at-uriIf this is a derived track like a transcode or a transcript, what was the source place.stream.video?
#commonMetadata
objectMetadata common to all media types. Contains subobjects for other media types.
Properties
audio
refdurationMs
integerduration of this track in milliseconds
language
stringIETF BCP 47 language tag corresponding to the content of this track
video
ref#trackView
objectProperties
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
place.stream.media.defs
not from the namespace authorityA track backed by a MUXL container
-
place.stream.video
recordSome audiovisual content.
-
Media file representing a segment of a livestream
-
Bluvy Tube-specific metadata for a published video, written to the creator's own repo alongside the app.bsky.feed.post record that actually carries the video (via app.bsky.embed.video). Not required or validated by the PDS or any other AT Protocol app — Bluvy Tube reads this back itself to render an owner-editable title/description/language overlay on top of the plain post text. Written by App\Service\VideoPublicationProcessor (native uploads) and rewritten by App\Service\PdsMetadataSyncService
-
A streamplace node's report of view counts for one place.stream.video over a closed time window. Published in the reporting node's server repo (not the streamer's), so a video served by multiple nodes accumulates multiple records — consumers are expected to sum across trusted reporters. The rkey is conventionally `<windowStart-as-tid>-<video-rkey>` so re-running the aggregator over the same window is idempotent. Counts represent the reporting node's best effort given the data it has; the `tracks