diff --git a/docs/DEVELOPER/core-concepts/playing-videos.md b/docs/DEVELOPER/core-concepts/playing-videos.md index f750a7cf..e45c3e2a 100644 --- a/docs/DEVELOPER/core-concepts/playing-videos.md +++ b/docs/DEVELOPER/core-concepts/playing-videos.md @@ -18,11 +18,11 @@ Roku Player: * the video files must have been encoded in one of the formats supported by a Roku Player (see [Streaming - specifications](doc:streaming-specifications)) + specifications](doc:media#supported-video-codecs)) * if you want to use an adaptive bitrate switching scheme, the video files must be configured to use the supported adaptive bitrate scheme you want (see [Streaming - specifications](doc:streaming-specifications)) + specifications](doc:media#adaptive-streaming-protocols)) * you must also include any supporting files for special playback options you want, such as _trick play_ (see [Trick mode](doc:trick-mode)) @@ -133,7 +133,7 @@ video playback is interrupted by an unexpected slowdown in the video stream transfer rate. (Video playback interruptions are more likely to occur if you do not take advantage of some type of adaptive bitrate configuration of the video playback, such as using a segmented adaptive -video playback scheme such as HLS, as described in [Streaming specifications](doc:streaming-specifications).) +video playback scheme such as HLS, as described in [Streaming specifications](doc:media#hls-streams).) To indicate to the user that the video stream is buffering, the Video node class includes two instances of an diff --git a/docs/DEVELOPER/performance-guide/optimization-techniques.md b/docs/DEVELOPER/performance-guide/optimization-techniques.md index f2a2dab6..62357dc1 100644 --- a/docs/DEVELOPER/performance-guide/optimization-techniques.md +++ b/docs/DEVELOPER/performance-guide/optimization-techniques.md @@ -106,6 +106,6 @@ Circular references can be detected by calling [RunGarbageCollector](doc:compone * The Developer settings page is necessary for enabling developer mode on your box. * All file paths are prefixed by the device name and a colon: `pkg:/filename.txt`. See [File System](doc:file-system) for more information. * Display a facade screen when launching your application so that it appears to the user that your app launches immediately. When your scene is first rendered, display a channel level splash image while initial setup logic is happening. Hide it once you are ready to display content to the user. -* There are a limited number of video content and streaming formats supported on the Roku Streaming Player. See [Audio and Video Support](doc:streaming-specifications) for complete information on the supported formats. +* There are a limited number of video content and streaming formats supported on the Roku Streaming Player. See [Audio and Video Support](doc:media) for complete information on the supported formats. * Be sure to use a unique key for each application you publish and reuse this key each time you update your application using the "rekey" option. This ensures that all versions of your application will have access to the same registry data and avoid causing users to re-link after an update. * We require that your web servers support range requests. If they do not, you may run into content that is not playable, or large images that do not display. The data will appear as a corrupted file format to our components, as the first block may be resent by the web server when we expect data at a particular range or offset. diff --git a/docs/DEVELOPER/release-notes/index.md b/docs/DEVELOPER/release-notes/index.md index 769c0edf..95b9e27d 100644 --- a/docs/DEVELOPER/release-notes/index.md +++ b/docs/DEVELOPER/release-notes/index.md @@ -708,7 +708,7 @@ Below is a list of key developer-facing Roku OS 9.4 updates: * **[Widevine v16](/docs/specs/media/content-protection.md#widevine)** — Roku OS now supports Widevine v16 DRM, including on older supported platforms. -* **[WebP image format](/docs/specs/media/streaming-specifications.md#supported-image-formats)** — The Roku platform now supports the WebP image format, which provides smaller compressed image files and faster decoding and rendering. +* **[WebP image format](/docs/specs/media/index.md#supported-image-formats)** — The Roku platform now supports the WebP image format, which provides smaller compressed image files and faster decoding and rendering. * **[DRM security level reporting](/docs/references/brightscript/interfaces/ifdeviceinfo.md#getdrminfoex-as-object)** — The **ifDeviceInfo.GetDrmInfoEx()** method now returns the security levels of Widevine and PlayReady DRMs. diff --git a/docs/REFERENCES/brightscript/components/robitmap.md b/docs/REFERENCES/brightscript/components/robitmap.md index ad159c26..465945c9 100644 --- a/docs/REFERENCES/brightscript/components/robitmap.md +++ b/docs/REFERENCES/brightscript/components/robitmap.md @@ -64,7 +64,7 @@ Screen1.Finish() ## Supported image formats -See the [Roku streaming specification](doc:streaming-specifications) for the image formats supported by this component. +See the [Roku streaming specification](doc:media#supported-image-formats) for the image formats supported by this component. ## Supported interfaces diff --git a/docs/REFERENCES/brightscript/interfaces/ifhdmistatus.md b/docs/REFERENCES/brightscript/interfaces/ifhdmistatus.md index 6571bce6..df41a684 100644 --- a/docs/REFERENCES/brightscript/interfaces/ifhdmistatus.md +++ b/docs/REFERENCES/brightscript/interfaces/ifhdmistatus.md @@ -42,7 +42,7 @@ The version number of the HDCP link: 1.4 or 2.2. If an empty string is returned, HDCP is disabled. In this case, videos that require HDCP encryption cannot be played. Videos not requiring encryption should still be playable. -> For code demonstrating how to check whether a Roku device (STB or TV) can play 4K content, see the [streaming specification](doc:streaming-specifications). +> For code demonstrating how to check whether a Roku device (STB or TV) can play 4K content, see the [streaming specification](doc:media#detecting-4k-uhd-compatibility). ### IsHdcpActive(version as String) as Boolean diff --git a/docs/REFERENCES/scenegraph/renderable-nodes/poster.md b/docs/REFERENCES/scenegraph/renderable-nodes/poster.md index 6d26d93b..32866289 100644 --- a/docs/REFERENCES/scenegraph/renderable-nodes/poster.md +++ b/docs/REFERENCES/scenegraph/renderable-nodes/poster.md @@ -14,7 +14,7 @@ Extends [**Group**](doc:group) The Poster node class draws an image with the top/left corner located at the origin of the node local coordinate system. Because the Poster node class extends the Group node class, a Poster node can have child nodes. For example, a Poster node might have a Label node as a child that draws an annotation on top of the poster. -The Poster node class supports JPEG, PNG and (since [Roku OS 9.4](doc:release-notes#roku-os-94)) [WebP](https://developers.google.com/speed/webp/) image files. Please observe [Special WebP considerations](doc:streaming-specifications) when using the latter. +The Poster node class supports JPEG, PNG and (since [Roku OS 9.4](doc:release-notes#roku-os-94)) [WebP](https://developers.google.com/speed/webp/) image files. Please observe [Special WebP considerations](doc:media#special-webp-considerations) when using the latter. The Poster node class includes the capability to automatically scale graphical images to different sizes as they are loaded, by setting the loadWidth and loadHeight field values. After the graphical images are loaded, the images can be scaled to fit within the target screen element area specified by the width and height field values. To use this capability, select the scaling option you want as the value of the loadDisplayMode field. diff --git a/docs/VIDEOS/courses/rsg/video-player.md b/docs/VIDEOS/courses/rsg/video-player.md index 534317be..9dd631d5 100644 --- a/docs/VIDEOS/courses/rsg/video-player.md +++ b/docs/VIDEOS/courses/rsg/video-player.md @@ -16,7 +16,7 @@ next: ## About this lesson -This lesson explains how to add the [SceneGraph Video node](doc:video) to your app and link it to the content in other components. It describes how to open the video screen when content is selected, and close it when playback finishes or the back button is pressed on the Roku remote control. This lesson also includes the [requirements for streaming videos](doc:streaming-specifications) on the Roku platform. +This lesson explains how to add the [SceneGraph Video node](doc:video) to your app and link it to the content in other components. It describes how to open the video screen when content is selected, and close it when playback finishes or the back button is pressed on the Roku remote control. This lesson also includes the [requirements for streaming videos](doc:media) on the Roku platform. ## Resources @@ -25,7 +25,7 @@ This lesson explains how to add the [SceneGraph Video node](doc:video) to your a | [Video Player sample app](https://github.com/rokudev/scenegraph-master-sample/tree/master/VideoPlayer) | Download and review the code used in this lesson to implement a Video node in a Roku app . | | [Sideloading Roku apps](doc:developer-setup) | Sideload and test the Video Player app created in this lesson. | | [Video hosting](doc:how-channels-work) | View the list content delivery networks (CDNs) and online video platforms (OVPs) that have worked with publishers to host content for their Roku apps. | -| [Streaming spec](doc:streaming-specifications) | Understand the required file formats and encoding methods for streaming video content on Roku devices. | +| [Streaming spec](doc:media) | Understand the required file formats and encoding methods for streaming video content on Roku devices. | | [SceneGraph Video node](doc:video) | Read how to configure the different attributes of the SceneGraph Video node, including its playback, UI, trick play, and captioning parameters. | ## Related