diff --git a/adengine/how-to/image.md b/adengine/how-to/image.md index 933db43caa72..d35c5264ce9c 100644 --- a/adengine/how-to/image.md +++ b/adengine/how-to/image.md @@ -59,7 +59,7 @@ GET https://api.galaxy.dolbyrasp.com/image?url=https://my_bucket/my_folder/my_fi ### Using Credentials -Typically, cloud content is not publicly accessable. If the provided `url` is an encrypted link, remember to use `encodeURI()` to encode the URL inside the GET call. If you have registered cloud credentials with the Dolby OptiView Engine, you can reference those credentials in the call. +Typically, cloud content is not publicly accessible. If the provided `url` is an encrypted link, remember to use `encodeURI()` to encode the URL inside the GET call. If you have registered cloud credentials with the Dolby OptiView Engine, you can reference those credentials in the call. ``` GET https://api.galaxy.dolbyrasp.com/image?url=s3://my_bucket/my_folder/my_file.mxf&format=png&height=280&credentials_key=my_s3_creds diff --git a/adengine/how-to/quality-control.md b/adengine/how-to/quality-control.md index 919016816595..ae7be0300c02 100644 --- a/adengine/how-to/quality-control.md +++ b/adengine/how-to/quality-control.md @@ -71,7 +71,7 @@ A QC object is added to the ad profile. In this case, we are checking that the s ### Pre and Post QC -The Ad Engine inlcludes both source and output QC. The `pre` object defines the pre-conversion QC parameters, and the `post` object defines the post-conversion. The vast majority of QC will be `pre` encoding, in order to weed out bad input files. +The Ad Engine includes both source and output QC. The `pre` object defines the pre-conversion QC parameters, and the `post` object defines the post-conversion. The vast majority of QC will be `pre` encoding, in order to weed out bad input files. ### QC Conditions diff --git a/contributing/guidelines/how-to-guides.md b/contributing/guidelines/how-to-guides.md index b4529a6f4b44..46312f76a167 100644 --- a/contributing/guidelines/how-to-guides.md +++ b/contributing/guidelines/how-to-guides.md @@ -100,7 +100,7 @@ Note: we use 5 # here, it will have a different style on Gatsby so it pops out ## Sample Applications -The sample application below demonstates how to do X. +The sample application below demonstrates how to do X. - Code: (if applicable) - Demo: (if applicable) diff --git a/contributing/templates/how-to-guides.md b/contributing/templates/how-to-guides.md index 480dd2c87941..4b3e4889b627 100644 --- a/contributing/templates/how-to-guides.md +++ b/contributing/templates/how-to-guides.md @@ -57,7 +57,7 @@ Some information about the piece of code (optional). ## Sample Applications -The sample application below demonstates how to do X. +The sample application below demonstrates how to do X. - Code: (if applicable) - Demo: (if applicable) diff --git a/millicast/analytics/index.md b/millicast/analytics/index.md index ed9d45d764a7..387e9967ec41 100644 --- a/millicast/analytics/index.md +++ b/millicast/analytics/index.md @@ -95,7 +95,7 @@ app.get('/usage', (req, resp, next) => { }) .on('error', (e) => { console.log('ERROR', e); - resp.satus(404).json(e); + resp.status(404).json(e); }); apiReq.end(); }); @@ -128,7 +128,7 @@ app.get('/usage', (req, resp, next) => { }) .on('error', (e) => { console.log('ERROR', e); - resp.satus(404).json(e); + resp.status(404).json(e); }); apiReq.end(); }); @@ -270,7 +270,7 @@ app.get( '/usage', (req, resp, next) => { }) .on('error', e => { console.log('ERROR',e); - resp.satus(404).json(e); + resp.status(404).json(e); }); apiReq.end(); }); @@ -306,7 +306,7 @@ app.get('/streamusage', (req, resp, next) => { }) .on('error', e => { console.log('ERROR',e); - resp.satus(404).json(e); + resp.status(404).json(e); }); apiReq.end(); }); @@ -510,4 +510,4 @@ Calculating the viewers per stream (daily or hourly), which region they viewed f #### Special Characters in Stream Names -When querying usage with the [Analytics](/millicast/api/analytics-streams-series) APIs using `streamNames` it is expected that the streams have not used special characters such as `/`, `*`, or `--` as this will fail to report results. Recommendation is to avoid using special characters in stream names and sticking with alpha-numeric characters and single dashes. +When querying usage with the [Analytics](/millicast/api/analytics-streams-series) APIs using `streamNames` it is expected that the streams have not used special characters such as `/`, `*`, or `--` as this will fail to report results. Recommendation is to avoid using special characters in stream names and sticking with alphanumeric characters and single dashes. diff --git a/millicast/broadcast/index.mdx b/millicast/broadcast/index.mdx index f2771548f078..421bf16bb4fc 100644 --- a/millicast/broadcast/index.mdx +++ b/millicast/broadcast/index.mdx @@ -133,7 +133,7 @@ To learn how to create a stream from OBS using SRT, see the following video: The Dolby.io dashboard is used to configure the publish path and stream id for an incoming RTMP or RTMPs media stream. [How-to use FFmpeg with RTMP](/millicast/broadcast/software-encoders/ffmpeg.mdx)
-**FFmpeg** is a free and open-source software project that is commonly used in legacy media workflows. It is a command-line tool that is capable of outputing streaming content via RTMP, RTMPS, and RTSP. +**FFmpeg** is a free and open-source software project that is commonly used in legacy media workflows. It is a command-line tool that is capable of outputting streaming content via RTMP, RTMPS, and RTSP. [How-to use vMix with RTMP](/millicast/broadcast/software-encoders/vmix.mdx)
**vMix** is a software vision mixer available for Windows. It is useful for certain live video production workflows and supports RTMP output that can be broadcast by Dolby.io. diff --git a/millicast/changelog/changelog-native-sdk.md b/millicast/changelog/changelog-native-sdk.md index 566bd31bb878..1dfb9bbf30ce 100644 --- a/millicast/changelog/changelog-native-sdk.md +++ b/millicast/changelog/changelog-native-sdk.md @@ -220,7 +220,7 @@ using StreamDetails = std::variant; **Android** - Improved Android SDK playback experience following simulcast layer switches. - - Fixed extended freeze of frame during the switch between simulcast layers, especially prevelant during frequent switchines. + - Fixed extended freeze of frame during the switch between simulcast layers, especially prevalent during frequent switches. - Greatly reduced the number of freezes when packet loss experienced. - Improved Android SDK playback in constrained bandwidth scenarios. - Added multiple MCCMSampleBufferVideoRendererDelegate to MCCMSampleBufferVideoRenderer diff --git a/millicast/changelog/changelog-web-platform.md b/millicast/changelog/changelog-web-platform.md index 6445f08fb676..6564be32c91c 100644 --- a/millicast/changelog/changelog-web-platform.md +++ b/millicast/changelog/changelog-web-platform.md @@ -29,7 +29,7 @@ This release includes some minor updates: ๐Ÿ’ฅ **Breaking Changes** -- Removed the `onMetadata` event, which was already deprecated. This has been superceded by `metadata` as of v0.3.0. +- Removed the `onMetadata` event, which was already deprecated. This has been superseded by `metadata` as of v0.3.0. ## 2025-05-29 | Web SDK [0.4.0](https://github.com/millicast/millicast-sdk/releases/tag/v0.4.0) diff --git a/millicast/getting-started/creating-real-time-streaming-web-app.mdx b/millicast/getting-started/creating-real-time-streaming-web-app.mdx index b82b8eaa93a6..eb786a800b27 100644 --- a/millicast/getting-started/creating-real-time-streaming-web-app.mdx +++ b/millicast/getting-started/creating-real-time-streaming-web-app.mdx @@ -263,7 +263,7 @@ document.getElementById('btn-stop').onclick = () => { ## Continue learning -These starter apps were kept simple for the purpose of getting started. You can re-use these samples in your preferred JavaScript framework such as React, VueJS, Angular, etc. as you customize the user experience of joining a stream, handling when a stream hasn't started, maintaining button state, etc. +These starter apps were kept simple for the purpose of getting started. You can reuse these samples in your preferred JavaScript framework such as React, VueJS, Angular, etc. as you customize the user experience of joining a stream, handling when a stream hasn't started, maintaining button state, etc. Continue by exploring the [Streaming Web SDK](/millicast/playback/players-sdks/web/sdk/index.mdx) documentation for a guide on other functions as you continue building your own project. diff --git a/millicast/platform-requirements/update-to-project-and-trackids.md b/millicast/platform-requirements/update-to-project-and-trackids.md index 283c022cbc4f..7f2221c3ee31 100644 --- a/millicast/platform-requirements/update-to-project-and-trackids.md +++ b/millicast/platform-requirements/update-to-project-and-trackids.md @@ -5,7 +5,7 @@ unlisted: true # Note: unlisted pages still show up in dev mode This is part of our [Multi-view](/millicast/playback/multi-view.md) feature and only impacts users who where using the multiview feature and their own player SDK implementation. If you are using the hosted video player, there is no update to apply. -In the [Broadcast Events](/millicast/playback/players-sdks/viewer-events.md), the `active` event now uses truely dynamic `trackId`. Below you can find the details of what these broadcast events look like. Using `trackId` dynamically has been [documented in the SDK](https://github.com/millicast/millicast-sdk/blob/460444aa9e7a37ad2c9c77046a97cdaf6448a76f/packages/millicast-sdk/src/View.js#L163) for years but we had some hard-coded examples in our multi-view sample code. +In the [Broadcast Events](/millicast/playback/players-sdks/viewer-events.md), the `active` event now uses truly dynamic `trackId`. Below you can find the details of what these broadcast events look like. Using `trackId` dynamically has been [documented in the SDK](https://github.com/millicast/millicast-sdk/blob/460444aa9e7a37ad2c9c77046a97cdaf6448a76f/packages/millicast-sdk/src/View.js#L163) for years but we had some hard-coded examples in our multi-view sample code. `trackId` is an optional (future-proofing) parameter when calling the `project()` command and is not required. @@ -89,7 +89,7 @@ await millicastView.project(sourceID, [ }, { // when calling project() trackId is optional and we are removing it from our examples. By specifying a "media" value (eg, "audio") the correct media track will be used - // in the future we will support multi-audio in which case you will need to project the correct trackId to select the correct audio track as recieved from the broadcast event + // in the future we will support multi-audio in which case you will need to project the correct trackId to select the correct audio track as received from the broadcast event mediaId: audioTransceiver.mid, media: 'audio', }, diff --git a/millicast/playback/audio-multiplexing.md b/millicast/playback/audio-multiplexing.md index fddc73093b6d..954e768ab2a1 100644 --- a/millicast/playback/audio-multiplexing.md +++ b/millicast/playback/audio-multiplexing.md @@ -25,14 +25,14 @@ If you've reviewed the [Multi-source Broadcasting](/millicast/broadcast/multi-so To get started using Audio Multiplexing, you first need to create a Publishing token with [Multisource](/millicast/broadcast/multi-source-broadcasting.mdx) and have multiple audio sources ready to test, each assigned a unique `sourceID` at the publisher. -:::info Not familar with our JavaScript SDK? -Audio Multiplexing is a compelx feature made availible through our [Client SDKs](/millicast/playback/players-sdks/index.mdx). +:::info Not familiar with our JavaScript SDK? +Audio Multiplexing is a complex feature made available through our [Client SDKs](/millicast/playback/players-sdks/index.mdx). ::: Once you're streaming multiple audio sources, the next step is to set up the [Viewer](/millicast/playback/players-sdks/web/sdk/index.mdx#viewing-a-stream) so that the incoming audio sources can be correctly multiplexed. When connecting to the Viewer, there are a [number of parameters available in the SDK](https://millicast.github.io/millicast-sdk/View.html#connect) you can adjust depending on your workflow. Some parameters of note for audio multiplexing include: - `multiplexedAudioTracks`: This is required to enable multiplexing. It denotes the number (`int`) of audio tracks to receive as Voice Activity Detection (VAD) multiplexed audio. This value must be greater than or equal to the number of audio tracks on the stream. Additional audio tracks will overwrite existing audio tracks. There isn't a limit to the number of audio tracks that can be rendered in the browser, only the amount of data. The current limit is a bitrate of 12 Mbps. -- `dtx`: Discontinousous transmision or DTX is a `boolean` value that signals to the viewer to only deliver audio when audio is detected such as when a person is talking. Enabling DTX will reduce bandwidth costs for audio transmission but may cause non-voice audio such as instruments to become choppy. +- `dtx`: Discontinuous transmission or DTX is a `boolean` value that signals to the viewer to only deliver audio when audio is detected such as when a person is talking. Enabling DTX will reduce bandwidth costs for audio transmission but may cause non-voice audio such as instruments to become choppy. - `pinnedSourceId`: Pinned Source ID is a `String` that denotes the main source that will be received by the default MediaStream. This value is useful for denoting your default audio stream that will always load regardless of how many other audio channels are present. - `excludedSourceIds`: Exclude Source IDs is an `Array` of `Strings` that denotes audio streams that should not be included in the multiplex. This feature is useful for conference-type applications where a user's **own** audio shouldn't be heard. diff --git a/millicast/playback/frame-metadata.md b/millicast/playback/frame-metadata.md index c7d07598e195..57ffb9c3d7c5 100644 --- a/millicast/playback/frame-metadata.md +++ b/millicast/playback/frame-metadata.md @@ -340,7 +340,7 @@ const transformer = new TransformStream({ const frame_data = new Uint8Array(frame.data); const total_length = frame_data.length; - // Shift to left for endianess to retrieve the metadata size from the last + // Shift to left for endianness to retrieve the metadata size from the last // 4 bytes of the buffer let shift = 3; const size = frame_data.slice(total_length - 4).reduce((acc, v) => acc + (v << shift--), 0); diff --git a/millicast/playback/players-sdks/flutter/index.mdx b/millicast/playback/players-sdks/flutter/index.mdx index 67fc795ee1a8..8850bd749195 100644 --- a/millicast/playback/players-sdks/flutter/index.mdx +++ b/millicast/playback/players-sdks/flutter/index.mdx @@ -59,7 +59,7 @@ flutter pub add millicast_flutter_sdk For windows you may need to allow installing apps from any source: -You should now see the follwing information in pubspec.yaml file: +You should now see the following information in pubspec.yaml file: ```yaml dependencies: @@ -269,7 +269,7 @@ try { view.webRTCPeer.initStats(); return view; } catch (e) { - throw Excpetion(e); + throw Exception(e); } ``` diff --git a/millicast/playback/players-sdks/viewer-events.md b/millicast/playback/players-sdks/viewer-events.md index e79c585ea609..23e532196c5a 100644 --- a/millicast/playback/players-sdks/viewer-events.md +++ b/millicast/playback/players-sdks/viewer-events.md @@ -23,7 +23,7 @@ Currently, there are several events that can be listened to when connected to th ## Using events -:::tip Not familar with our SDKs? +:::tip Not familiar with our SDKs? Learn more about the Dolby.io Millicast streaming SDKs by following the [Getting Started](/millicast/getting-started/creating-real-time-streaming-web-app.mdx) guide or by learning about our [Client SDKs](/millicast/playback/players-sdks/index.mdx). ::: diff --git a/millicast/playback/securing-stream-playback.md b/millicast/playback/securing-stream-playback.md index e13a54e29f8b..3943ccdb15cf 100644 --- a/millicast/playback/securing-stream-playback.md +++ b/millicast/playback/securing-stream-playback.md @@ -60,7 +60,7 @@ import Img3 from '../assets/img/25a57ae-image.png'; :::caution Subscribe token exposed in the URL -For both the Embedded Viewer and the Hosted Viewer the Subscribe token is exposed in the URL. Unless your are using [IP filtering](/millicast/distribution/access-control/allowed-origins.md#ip-filters), users can share the URL and by extention the stream itself. To prevent this, each user should be served a Subscribe token unique to them. To learn about how to acomplish this continue to [Preventing Stream Sharing with Subscribe Tokens](/millicast/playback/securing-stream-playback.md#preventing-stream-sharing-with-subscribe-tokens). +For both the Embedded Viewer and the Hosted Viewer the Subscribe token is exposed in the URL. Unless your are using [IP filtering](/millicast/distribution/access-control/allowed-origins.md#ip-filters), users can share the URL and by extension the stream itself. To prevent this, each user should be served a Subscribe token unique to them. To learn about how to accomplish this continue to [Preventing Stream Sharing with Subscribe Tokens](/millicast/playback/securing-stream-playback.md#preventing-stream-sharing-with-subscribe-tokens). ::: #### Viewing a secured stream with the embedded viewer diff --git a/millicast/streaming-dashboard/managing-your-tokens.mdx b/millicast/streaming-dashboard/managing-your-tokens.mdx index 9163013131b5..e9fdeaa59fc8 100644 --- a/millicast/streaming-dashboard/managing-your-tokens.mdx +++ b/millicast/streaming-dashboard/managing-your-tokens.mdx @@ -89,7 +89,7 @@ Once created, your Publish token can be used to broadcast in a variety of differ ## Managing and editing existing publish tokens -Once a Pubish token is created, it is displayed on the **Live Broadcast** page. From this page, you can [start a broadcast using the Dashboard Broadcaster](/millicast/getting-started/using-the-dashboard.mdx#b-start-broadcast), enable or disable, delete, or edit the settings for each Publish token. +Once a Publish token is created, it is displayed on the **Live Broadcast** page. From this page, you can [start a broadcast using the Dashboard Broadcaster](/millicast/getting-started/using-the-dashboard.mdx#b-start-broadcast), enable or disable, delete, or edit the settings for each Publish token. import Tempsnip from '../assets/img/tempsnip.png'; diff --git a/millicast/streaming-dashboard/subscribe-tokens.mdx b/millicast/streaming-dashboard/subscribe-tokens.mdx index ee3fc36700f9..5c204e411dad 100644 --- a/millicast/streaming-dashboard/subscribe-tokens.mdx +++ b/millicast/streaming-dashboard/subscribe-tokens.mdx @@ -103,8 +103,8 @@ Of note in the manage screen is the **string of the Subscribe token itself**. Th https://viewer.millicast.com?streamId=[Account ID]/[Stream Name]&token=[Subscribe Token] ``` -:::caution Unsecure URL -The above example exposes the subscribe token in the URL. To prevent URL or token sharing, serve each viewer a unique subscribe token with the [BindsIPAddressOnUsage ](#advanced-settings) parameter enabled to bind the token to the user. +:::caution Insecure URL +The above example exposes the subscribe token in the URL. To prevent URL or token sharing, serve each viewer a unique subscribe token with the [BindsIPAddressOnUsage](#advanced-settings) parameter enabled to bind the token to the user. ::: Depending on the scale of your production, it may not be secure or feasible to create tokens via the dashboard. Instead, you can create tokens via the [Token API](/millicast/streaming-dashboard/token-api.mdx), or, for true scalability, [you can self-sign tokens](#self-signing-subscribe-tokens). diff --git a/millicast/streaming-dashboard/token-api.mdx b/millicast/streaming-dashboard/token-api.mdx index 6abcf769a3b0..bc7590d356c0 100644 --- a/millicast/streaming-dashboard/token-api.mdx +++ b/millicast/streaming-dashboard/token-api.mdx @@ -65,7 +65,7 @@ From here, you can start using any of the APIs in the [API reference](/millicast Publish tokens are required to start a stream and can be used to control who, where, and what kind of stream can be started. The easiest way to begin learning about programmatically creating a publish token is by going to the [PublishToken Create Token interface of the API reference](/millicast/api/publish-token-v-1-create-token.api.mdx). -Inside the reference, you'll see a section on the right where you can select your preferred programing language, add your [API Secret key](/millicast/streaming-dashboard/token-api.mdx#acquiring-your-api-secret), and see the sample call based on the parameters you've added so far. In the middle, you'll see where you can add and adjust the required and optional parameters, along with the respective parameter definitions. +Inside the reference, you'll see a section on the right where you can select your preferred programming language, add your [API Secret key](/millicast/streaming-dashboard/token-api.mdx#acquiring-your-api-secret), and see the sample call based on the parameters you've added so far. In the middle, you'll see where you can add and adjust the required and optional parameters, along with the respective parameter definitions. import PubToken from '../assets/img/pubtok.png'; @@ -163,7 +163,7 @@ Unlike the publisher, the viewer, by default, does not need a subscribe token to The easiest way to begin learning about creating a subscribe token is by going to [the _SubscribeToken Create Token_ interface of the API reference](/millicast/api/subscribe-token-v-1-create-token.api.mdx). -Inside the reference, you'll see a section on the right where you can select your preferred programing language, add your [API Secret key](/millicast/streaming-dashboard/token-api.mdx#acquiring-your-api-secret), and see the sample call based on the parameters you've added so far. In the middle, you'll see where you can add and adjust the required and optional parameters, along with the respective parameter definitions. +Inside the reference, you'll see a section on the right where you can select your preferred programming language, add your [API Secret key](/millicast/streaming-dashboard/token-api.mdx#acquiring-your-api-secret), and see the sample call based on the parameters you've added so far. In the middle, you'll see where you can add and adjust the required and optional parameters, along with the respective parameter definitions. import SubToken from '../assets/img/subtok.png'; diff --git a/theolive/callouts/_premium_feature.md b/theolive/callouts/_premium_feature.md index 74d206cdd949..f2e806e1f0fc 100644 --- a/theolive/callouts/_premium_feature.md +++ b/theolive/callouts/_premium_feature.md @@ -1,5 +1,5 @@ :::warning Premium Feature -This feature is a premium option that must be enabled on your acccount. If you would like to use this capability on your project, please [submit a support ticket](https://support.dolby.io/hc/en-au) or reach out to your [sales/solutions](https://optiview.dolby.com/contact/) contact. +This feature is a premium option that must be enabled on your account. If you would like to use this capability on your project, please [submit a support ticket](https://support.dolby.io/hc/en-au) or reach out to your [sales/solutions](https://optiview.dolby.com/contact/) contact. ::: diff --git a/theolive/contribution/software-encoders/obs.md b/theolive/contribution/software-encoders/obs.md index 1b3a312627e1..b219125e26f6 100644 --- a/theolive/contribution/software-encoders/obs.md +++ b/theolive/contribution/software-encoders/obs.md @@ -58,7 +58,7 @@ Hit apply on settings, close the window, and click on _Start Streaming_ in the _ ### 4. Start your THEOlive channel -Your THEOlive channel must be started in order to recieve video ingest from OBS. You can choose to start up your channel before or after you start streaming via OBS. +Your THEOlive channel must be started in order to receive video ingest from OBS. You can choose to start up your channel before or after you start streaming via OBS. Starting a channel can be done either [through the API](/theolive/api/channels/start-channel) or via [the console](https://console.theo.live/). diff --git a/theolive/platform/manage-team.mdx b/theolive/platform/manage-team.mdx index 322a9ed11be8..80bab42947b0 100644 --- a/theolive/platform/manage-team.mdx +++ b/theolive/platform/manage-team.mdx @@ -13,7 +13,7 @@ After signing up for the [THEOlive console](https://console.theo.live/login), yo Click on the โ€œMy accountโ€ button, on the top right-hand corner of the screen and select _My Team_. -![](../assets/img/22fb225-my-team.PNG 'My team in top right-hand corener menu') +![](../assets/img/22fb225-my-team.PNG 'My team in top right-hand corner menu') This section displays all members of your team along with their current status. Each member is assigned a role as either an admin or user. diff --git a/theolive/platform/real-time-update-with-webhooks.mdx b/theolive/platform/real-time-update-with-webhooks.mdx index 96f691cb5a31..847139b146f9 100644 --- a/theolive/platform/real-time-update-with-webhooks.mdx +++ b/theolive/platform/real-time-update-with-webhooks.mdx @@ -50,7 +50,7 @@ app.listen(port, () => { :::warning ๐Ÿšง Newly created webhooks will be disabled by default -When you create a webhook, it won't be active yet. THEOlive does this so you can test things out before we actually start firing events to your endpoint. When you think you are fully ready to receive webhook mesages from THEOlive, you can enable the webhook through the console, or via the [/webhooks/$\{webhook-id\}/enable](/theolive/api/webhooks/enable-webhook) endpoint. +When you create a webhook, it won't be active yet. THEOlive does this so you can test things out before we actually start firing events to your endpoint. When you think you are fully ready to receive webhook messages from THEOlive, you can enable the webhook through the console, or via the [/webhooks/$\{webhook-id\}/enable](/theolive/api/webhooks/enable-webhook) endpoint. ::: When a webhook is created, you can update or delete it through the API or management console. At the details page you can also see the history of all message that have been sent to your endpoint, and if they've failed or not. diff --git a/theolive/platform/security/geo-blocking.md b/theolive/platform/security/geo-blocking.md index 8dc415756c0e..dee5cc9cdc7c 100644 --- a/theolive/platform/security/geo-blocking.md +++ b/theolive/platform/security/geo-blocking.md @@ -10,7 +10,7 @@ Geo-blocking can be configured via the API or the console. You can enable geo-blocking on a channel by [updating](/theolive/api/channels/update-channel) the `geoBlocking` object within `publicationConfig`. The `mode` of geo-blocking can also be configured: -- `whitelist`: Used by default when no `mode` is passed. This will make the content only available in the countries that have been specified in the `countries` property. Countries not listed in the `countries` property will not recieve the stream. +- `whitelist`: Used by default when no `mode` is passed. This will make the content only available in the countries that have been specified in the `countries` property. Countries not listed in the `countries` property will not receive the stream. - `blacklist`: Blocks the content in the countries that have been specified in the `countries` property. All other countries not specified in the `countries` property will be able to view the content. :::tip diff --git a/theolive/platform/security/ip-blocking.md b/theolive/platform/security/ip-blocking.md index 6252cf080fd3..66dac892f4a3 100644 --- a/theolive/platform/security/ip-blocking.md +++ b/theolive/platform/security/ip-blocking.md @@ -10,7 +10,7 @@ IP-blocking can be configured via the API or the console. You can enable IP-blocking on a channel by [updating](/theolive/api/channels/update-channel) the `ipBlocking` object within `publicationConfig`. The `mode` of geo-blocking can also be configured: -- `whitelist`: Used by default when no `mode` is passed. This will make the content only available for the CIDRs that have been specified in the `cidrs` property. CIDRs not listed in the `cidrs` property will not recieve the stream. +- `whitelist`: Used by default when no `mode` is passed. This will make the content only available for the CIDRs that have been specified in the `cidrs` property. CIDRs not listed in the `cidrs` property will not receive the stream. - `blacklist`: Blocks the content for the CIDRs that have been specified in the `cidrs` property. All CIDRs not specified in the `cidrs` property will be able to view the content. For example: If you want to restrict certain CIDRs from viewing your content, you can pass the following request: diff --git a/theolive/platform/viewer-insights.mdx b/theolive/platform/viewer-insights.mdx index 8826d1d14127..92919bf63230 100644 --- a/theolive/platform/viewer-insights.mdx +++ b/theolive/platform/viewer-insights.mdx @@ -29,7 +29,7 @@ The viewer insights page of your channel includes: - Viewer locations - Top browser and operating systems -:::warning[Must use THEOlive in THEOplayer to recieve viewer insights] +:::warning[Must use THEOlive in THEOplayer to receive viewer insights] Viewer insights will only work if you are using THEOlive inside a THEOplayer. Please refer to [this guide](../playback/web/getting-started.mdx) for implementation details. diff --git a/theolive/platform/viewer-tracking.mdx b/theolive/platform/viewer-tracking.mdx index 80adbbe6bba8..8c42c07db624 100644 --- a/theolive/platform/viewer-tracking.mdx +++ b/theolive/platform/viewer-tracking.mdx @@ -22,7 +22,7 @@ The following is an **example workflow** for setting up stream tracking: 1. Enable [_Token Security_](security/token-based-security.mdx) on the channel or alias 1. When you create your self-signed token, add one or both of the following parameters to a `streaming` object in the `payload` of your JWT: - **trackingId**: Groups viewers of the same channel, allows you to get the aggregated bandwidth usage of all viewers. This is useful for billing a single channel or alias if you use multiple distribution partners and want aggregated billing metrics back or viewer reports for groups of viewers. The maximum size is 128 characters - - **customViewerData** : Access the bandwidth consumption of each viewer for analytics purposes and passthrough metadata from your CMS for a viewer and be able to retrieve it in a viewer report. This data is not parsed by our system and can be a series of key-value pairs for you to extract later. The maxium size is 1024 characters + - **customViewerData** : Access the bandwidth consumption of each viewer for analytics purposes and passthrough metadata from your CMS for a viewer and be able to retrieve it in a viewer report. This data is not parsed by our system and can be a series of key-value pairs for you to extract later. The maximum size is 1024 characters 1. Pass the JWT through to the player as described in the [_Token Security_](security/token-based-security.mdx) section 1. To get _Advanced Reports_, including user-reports, please contact your Dolby representative for access. diff --git a/theolive/playback/flutter/01-basic-playback-guide.mdx b/theolive/playback/flutter/01-basic-playback-guide.mdx index d06ef90f9b5e..d3d4c68ef0a8 100644 --- a/theolive/playback/flutter/01-basic-playback-guide.mdx +++ b/theolive/playback/flutter/01-basic-playback-guide.mdx @@ -74,7 +74,7 @@ To make the current stream take up the full screen, pass a presentationMode of ' player.setPresentationMode('FULLSCREEN'); ``` -To confirm that the change has occured, check the `getPresentationMode` property to ensure it now returns `fullscreen` as its value: +To confirm that the change has occurred, check the `getPresentationMode` property to ensure it now returns `fullscreen` as its value: ```dart // should return a value of 'fullscreen' to the console diff --git a/theolive/playback/react-native/token-based-security.mdx b/theolive/playback/react-native/token-based-security.mdx index 3d58d747af9f..fb037eea8fd4 100644 --- a/theolive/playback/react-native/token-based-security.mdx +++ b/theolive/playback/react-native/token-based-security.mdx @@ -136,7 +136,7 @@ function registerServiceWorker() { }); }; -// Initialise the service worker some time early in the processs. +// Initialise the service worker some time early in the process. if (!(window.MediaSource || window.ManagedMediaSource)) { registerServiceWorker(); } diff --git a/theolive/playback/web/token-based-security.mdx b/theolive/playback/web/token-based-security.mdx index 99fbcd353466..210da8f5dcb8 100644 --- a/theolive/playback/web/token-based-security.mdx +++ b/theolive/playback/web/token-based-security.mdx @@ -140,7 +140,7 @@ function registerServiceWorker() { }); }; -// Initialise the service worker some time early in the processs. +// Initialise the service worker some time early in the process. if (!(window.MediaSource || window.ManagedMediaSource)) { registerServiceWorker(); } diff --git a/theoplayer/changelog.md b/theoplayer/changelog.md index 95f605d76dfe..9e9d6c73ae95 100644 --- a/theoplayer/changelog.md +++ b/theoplayer/changelog.md @@ -79,7 +79,7 @@ toc_max_heading_level: 2 - Fixed an issue where a WideVine L1 protected DASH stream would occasionally fail to play on certain Android FireTV models (AFTSS & AFTSSS). - Fixed an issue where an `#EXT-X-KEY` with a base64 `data:` URI was sometimes parsed incorrectly from the HLS playlist. - Fixed an issue where playback of subsequent OptiView Live sources would cause incorrect endpoints to be selected. -- Fixed an isse where MPEG-DASH content steering was sometimes not switching to a different `serviceLocation` when segment downloads failed. +- Fixed an issue where MPEG-DASH content steering was sometimes not switching to a different `serviceLocation` when segment downloads failed. - Fixed an issue where a PS4 WebMAF app could freeze upon requesting a media segment. - Fixed an issue where the timecode text track would not be present on HESP streams that contain SEI timecodes. - Fixed an issue in MPEG-DASH Content Steering where the `Retry-After` header was not respected when the server returned status code `429`. @@ -2768,7 +2768,7 @@ For more info on navigating our breaking changes, take a look at our migration g #### ๐Ÿ› Issues -- Fixed an audio glitch that occured when transitioning to background audio playback. +- Fixed an audio glitch that occurred when transitioning to background audio playback. - Fixed an issue on Android where the player would sometimes crash when setting a new source after play-out of the old source had already started. ## ๐Ÿš€ 8.2.1 (2024/10/14) @@ -2970,7 +2970,7 @@ For more info on navigating our breaking changes, take a look at our migration g #### ๐Ÿ’ฅ Breaking Changes -- Raising the tvOS mimimum supported version of our tvOS SDK to 13.0 for consistency with iOS version. +- Raising the tvOS minimum supported version of our tvOS SDK to 13.0 for consistency with iOS version. #### ๐Ÿ‘Ž Deprecations @@ -3734,7 +3734,7 @@ THEOplayer 7.0 is **backwards compatible for most features but includes some bre #### ๐Ÿ› Issues -- Fixed an issue where VMAPs would not be scheduled in the Google IMA intergration if `player.currentTime` was set before initial playback. +- Fixed an issue where VMAPs would not be scheduled in the Google IMA integration if `player.currentTime` was set before initial playback. - Fixed an issue where the browser tab could hang when removing the player from the DOM without calling `player.destroy()`, while the player is rendering WebVTT subtitles. - Fixed a CSS issue where the control bar could sometimes have a very small vertical overflow, which could lead to unwanted scrollbars when the player is embedded in an `