• Device Details
• Prerequisite
• Playing Test streams with Rialto
• Running YouTube with Rialto
• Pipeline Diagram
• Known Issues / limitations

Device Details

Prerequisite

• Build the latest Raspberry Pi4/Pi3 Image using below links
  RPI 4B model reference platform for RDKV - RDK - RDK Central Wiki
  RDK-V rdk-next Yocto 3.1 dunfell build for Raspberrypi - RDK - RDK Central Wiki
  
  

Playing Test streams with Rialto

• Stop wpeframework 

  systemctl stop wpeframework

• For Rpi4 platform - Run the below command in all terminals where you need to run the rialto commands.

  export WESTEROS_DRM_CARD=/dev/dri/card0

  Note:  In case of Rpi3 platform, no need to run the above command. Since, Rpi3 uses only one master card.

  
  

• For below steps, Refer Running YouTube with Rialto - Preferred Program - RDK Central Wiki page.
  - Run westeros
  - Start server manager simulator
  - Run Rialto Server for YouTube
  
  

• Command used to run test streams:

  GST_REGISTRY=/tmp/rialto-registry.bin RIALTO_DEBUG=5 RIALTO_CONSOLE_LOG=1 RIALTO_SOCKET_PATH=/tmp/rialto-0 XDG_RUNTIME_DIR=/tmp WAYLAND_DISPLAY=westeros-cobalt LD_LIBRARY_PATH="$PWD/usr/lib" COBALT_CONTENT_DIR="$PWD/usr/share/content/data" RIALTO_CLIENT_BACKEND_LIB="/usr/lib/libRialtoClient.so" gst-launch-1.0 playbin uri=file:///tmp/sample-video-file-for-testing.mp4

           Note: 

• • Make sure rialto-registry.bin is cleared
    rm /tmp/rialto-registry.bin
    
  • PFA sample-video-file-for-testing_mp4.zip for reference.

Playing HLS with Rialto

• Stop wpeframework 

  systemctl stop wpeframework

• For Rpi4 platform - Run the below command in all terminals where you need to run the rialto commands.

  export WESTEROS_DRM_CARD=/dev/dri/card0

  Note:  In case of Rpi3 platform, no need to run the above command. Since, Rpi3 uses only one master card.

  
  

• Run westeros

  XDG_RUNTIME_DIR=/tmp LD_PRELOAD=/usr/lib/libwesteros_gl.so.0 westeros --renderer /usr/lib/libwesteros_render_embedded.so.0.0.0 --embedded --display "westeros-cobalt" --window-size 1920x1080

• Start server manager simulator:

  RIALTO_DEBUG=5 RIALTO_SESSION_SERVER_STARTUP_TIMEOUT_MS=15000 SESSION_SERVER_ENV_VARS='XDG_RUNTIME_DIR=/tmp;RIALTO_SINKS_RANK=0;GST_REGISTRY=/tmp/rialto-server-gstreamer-cache.bin;WAYLAND_DISPLAY=westeros-cobalt;FORCE_SAP=TRUE;FORCE_SVP=TRUE' /usr/bin/RialtoServerManagerSim

  Note:

   If you are not able to play HLS using rialto-mse sinks, then try to increase value of RIALTO_SESSION_SERVER_STARTUP_TIMEOUT_MS (>2000) or remove the TIMEOUT. So, there will be no startup limit.

• Run Rialto Server for YouTube:

  curl -X POST -d "" localhost:9008/SetState/YouTube/Active

  
  

• Command used to run test streams:

  GST_REGISTRY=/tmp/rialto-registry.bin RIALTO_DEBUG=5 RIALTO_CONSOLE_LOG=1 RIALTO_SOCKET_PATH=/tmp/rialto-0 XDG_RUNTIME_DIR=/tmp WAYLAND_DISPLAY=westeros-cobalt LD_LIBRARY_PATH="$PWD/usr/lib" COBALT_CONTENT_DIR="$PWD/usr/share/content/data" RIALTO_CLIENT_BACKEND_LIB="/usr/lib/libRialtoClient.so" gst-launch-1.0 playbin uri=https://bitmovin-a.akamaihd.net/content/MI201109210084_1/mpds/f08e80da-bf1d-4e3d-8899-f0f6155f6efa.mpd

           Note: 

• • Make sure rialto-registry.bin is cleared
    rm /tmp/rialto-registry.bin

Running YouTube with Rialto

• Stop wpeframework 

  systemctl stop wpeframework

• For Rpi4 platform - Run the below command in all terminals where you need to run the rialto commands.

  export WESTEROS_DRM_CARD=/dev/dri/card0

  Note:  In case of Rpi3 platform, no need to run the above command. Since, Rpi3 uses only one master card.

  
  

• For below steps, Refer Running YouTube with Rialto - Preferred Program - RDK Central Wiki page.
  - Run westeros
  - Start server manager simulator
  - Run Rialto Server for YouTube
  
  

• Command used to launch YouTube Homepage.

  GST_REGISTRY=/tmp/rialto-registry.bin RIALTO_DEBUG=5 RIALTO_SOCKET_PATH=/tmp/rialto-0 XDG_RUNTIME_DIR=/tmp WAYLAND_DISPLAY=westeros-cobalt LD_LIBRARY_PATH="$PWD/usr/lib" COBALT_CONTENT_DIR="/usr/share/content/data" RIALTO_CLIENT_BACKEND_LIB="/usr/lib/libRialtoClient.so" /usr/bin/cobalt_bin

           Note: 

• • There is a small correction in the below "Run YouTube" Command mentioned in rdk wiki page

  • remove "$PWD" in COBALT_CONTENT_DIR

  • Make sure rialto-registry.bin is cleared
    rm /tmp/rialto-registry.bin
    
    

Pipeline Diagram

Application Session Management - Overview

RDK Shell + Rialto Architecture (Proposed)

App'n Launch Life cycle

App'n Suspend Life cycle

App'n Destroy Life cycle

Design Approach

• Initial approach was to run RialtoServer using systemd during the boot up sequence. 

This approach had flaws as considering the fact that RialtoServer shouldn't be started by service file directly.

libRialtoServerManager.so should be responsible for creating an insatnce of RialtoServer which should spawn the socket for running rialto.

• Later it was decided to link RialtoServerManager.so with RDKShell, no need to run the system service. 

As mentioned above the latest approach was to integrate libRialtoServerManager.so to RDKShell which would give RDKShell the access to invoke API's.

API's to be invoked via RDKShell.

https://github.com/rdkcentral/rialto/blob/master/serverManager/public/include/IServerManagerService.h

initiateApplication - causes for a new RialtoSessionServer instance to be spawned.

changeSessionServerState - requests an session server to change its state

• Rialto Distro feature was enabled in rdk_next to build Rialto components in RDK builds. 
• RDK shell session management will handle following Rialto state changes 
  • Launch
  • Suspend
  • Destroy

Known issues / Limitations

Encrypted playback is not verified as a part of POC.