Conversation
moving into the repo for easier feedback
|
|
please don't merge these changes yet as the features are not complete |
| With [Stream Recordings](/millicast/distribution/stream-recordings/index.mdx) you will want to be able to retrieve and operate on any media assets that are created. You can do this manually using the [Streaming Dashboard](/millicast/streaming-dashboard/index.mdx) or automate workflows using the [Media Assets](/millicast/api/media-assets-list-media-assets.api.mdx) REST endpoints. There are also [Media Webhooks](/millicast/webhooks/media.md) available for building event-driven integrations. | ||
|
|
||
| ## Recordings in the Dashboard | ||
| _Note: At this time, **Stream Recordings** are currently visible in the dashboard, for **live-to-vod** and **media uploads**, you must use the API to retrieve your assets. Creating live-to-vod assets requires consultation with the Dolby team to enable the workflow._ |
There was a problem hiding this comment.
Live-to-vod clips are also visible on the dashboard
Edit: only mp4, not HLS
| Media assets are media recordings that are created one of several ways: | ||
|
|
||
| - **[Stream Recordings](/millicast/distribution/stream-recordings/):** Media captured by enabling _recording_ on a token, the entire stream from first to last frame is stored in the cloud as a single-layer "mezzanine" recording, usually stored in an MP4 container | ||
| - **[Live-to-VOD clips](/millicast/distribution/stream-recordings/live-clipping/):** These assets are "clipped" out of a live streaming workflow as a servable HLS manifest that can be used for distribution and replays of the stream. These are referred to as "live clips" or "live clipping" |
There was a problem hiding this comment.
Are millicast mp4 clips also included in live-to-vod?
There was a problem hiding this comment.
yes, i made an update but it will be confusing for customers only using theo and not being able to generate an mp4. I assume we don't handle that case? Probably something we should pick up for consistency.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…ts.mdx Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
| ### How-to Retrieve a Media Asset | ||
|
|
||
| Recordings will typically be stored on Dolby's servers and made available for retrieval. You'll need to know the `mediaAssetId` of the item you want to download. | ||
| Media Assets are typically be stored on Dolby's servers and made available for retrieval. You'll need to know the `mediaAssetId` of the item you want to download. This includes all media types including stream recordings, live-to-vod clips, and media uploads. |
There was a problem hiding this comment.
🟡 Grammar error: "typically be stored" should be "typically stored"
When rewriting the sentence from "Recordings will typically be stored" to use "Media Assets are", the word "be" was left behind, resulting in the ungrammatical phrase "Media Assets are typically be stored". It should read "Media Assets are typically stored".
| Media Assets are typically be stored on Dolby's servers and made available for retrieval. You'll need to know the `mediaAssetId` of the item you want to download. This includes all media types including stream recordings, live-to-vod clips, and media uploads. | |
| Media Assets are typically stored on Dolby's servers and made available for retrieval. You'll need to know the `mediaAssetId` of the item you want to download. This includes all media types including stream recordings, live-to-vod clips, and media uploads. |
Was this helpful? React with 👍 or 👎 to provide feedback.
|
|
||
| # Live Clipping | ||
|
|
||
| Live clipping allows you to create CDN servable media files from your HLS stream while it is in progress. This requires a Real-time streaming account and [API key](/millicast/api/millicast-api) in addition to your THEOlive channe. For more details on the capabilties of the Media Asset API, refer to our [Media Asset API guide](/millicast/distribution/stream-recordings/how-to-get-media-assets/) and contact your Dolby Account Team to help you get set up. |
There was a problem hiding this comment.
🟡 Typos: "channe" (missing 'l') and "capabilties" (missing 'i')
Line 7 of the new live-clipping page contains two typos: "THEOlive channe." should be "THEOlive channel." and "capabilties" should be "capabilities". These appear in the introductory paragraph that users will read first.
| Live clipping allows you to create CDN servable media files from your HLS stream while it is in progress. This requires a Real-time streaming account and [API key](/millicast/api/millicast-api) in addition to your THEOlive channe. For more details on the capabilties of the Media Asset API, refer to our [Media Asset API guide](/millicast/distribution/stream-recordings/how-to-get-media-assets/) and contact your Dolby Account Team to help you get set up. | |
| Live clipping allows you to create CDN servable media files from your HLS stream while it is in progress. This requires a Real-time streaming account and [API key](/millicast/api/millicast-api) in addition to your THEOlive channel. For more details on the capabilities of the Media Asset API, refer to our [Media Asset API guide](/millicast/distribution/stream-recordings/how-to-get-media-assets/) and contact your Dolby Account Team to help you get set up. |
Was this helpful? React with 👍 or 👎 to provide feedback.
| Media assets are media recordings that are created one of several ways: | ||
|
|
||
| - **[Stream Recordings](/millicast/distribution/stream-recordings/):** Media captured by enabling _recording_ on a token, the entire stream from first to last frame is stored in the cloud as a single-layer "mezzanine" recording, usually stored in an MP4 container | ||
| - **[Live-to-VOD clips](/millicast/distribution/stream-recordings/live-clipping/):** These assets are "clipped" out of a live streaming workflow as a servable HLS manifest that can be used for distribution and replays of the stream. These are referred to as "live clips" or "live clipping". You can also extract a single MP4 mezzanine "clip" appropriate or social sharing or archive |
There was a problem hiding this comment.
🟡 Missing word "for" in bullet point: "appropriate or social sharing"
Line 8 says "a single MP4 mezzanine 'clip' appropriate or social sharing or archive" — the word "for" is missing. It should read "appropriate for social sharing or archive".
| - **[Live-to-VOD clips](/millicast/distribution/stream-recordings/live-clipping/):** These assets are "clipped" out of a live streaming workflow as a servable HLS manifest that can be used for distribution and replays of the stream. These are referred to as "live clips" or "live clipping". You can also extract a single MP4 mezzanine "clip" appropriate or social sharing or archive | |
| - **[Live-to-VOD clips](/millicast/distribution/stream-recordings/live-clipping/):** These assets are "clipped" out of a live streaming workflow as a servable HLS manifest that can be used for distribution and replays of the stream. These are referred to as "live clips" or "live clipping". You can also extract a single MP4 mezzanine "clip" appropriate for social sharing or archive |
Was this helpful? React with 👍 or 👎 to provide feedback.
| Using the response fields _from the previous API call_, upload the media asset files to the specified S3 location. | ||
|
|
||
| ``` | ||
| $ AWS_ACCESS_KEY_ID=<from-above> AWS_SECRET_ACCESS_KEY=<from-above> AWS_SESSION_TOKEN=<from-above> \ aws s3 cp <filepath> s3://<bucketName>/<objectPrefix> |
There was a problem hiding this comment.
🟡 Stray backslash in shell command causes invalid command name
The shell example $ AWS_ACCESS_KEY_ID=<from-above> ... AWS_SESSION_TOKEN=<from-above> \ aws s3 cp ... has a stray \ (backslash-space) before aws. In bash, \ escapes the space making it part of the next word, so the shell would try to execute aws (with a leading space) as the command name, which would fail with "command not found". The \ should be removed so that the environment variables are set inline before the aws command.
| $ AWS_ACCESS_KEY_ID=<from-above> AWS_SECRET_ACCESS_KEY=<from-above> AWS_SESSION_TOKEN=<from-above> \ aws s3 cp <filepath> s3://<bucketName>/<objectPrefix> | |
| $ AWS_ACCESS_KEY_ID=<from-above> AWS_SECRET_ACCESS_KEY=<from-above> AWS_SESSION_TOKEN=<from-above> aws s3 cp <filepath> s3://<bucketName>/<objectPrefix> |
Was this helpful? React with 👍 or 👎 to provide feedback.
2 participants
moving changes from rhfitz into a branch for the feedback process