• Format your newly created partition with ext3 file system

• Create a folder for mounting your new partition at /ext_hdd
• Mount your newly created hard disk partition to /ext_hdd

STEP 5: Copy a Single Program Transport stream to your file system to be used for emulator video playback.

• Pre-requisite to the step is assumed that /ext_hdd is already mounted with the external hard disk partition on your emulator VM
• Copy your SPTS video file from your host machine to /ext_hdd folder on the emulator VM 
• Note: The following command is performed from your Host Machine

• Back on your emulator VM, create a link in /opt/www/ to point to the external hard drive at its mount point /ext_hdd

• In the screenshot below, <your_spts_file_name> is assumed to be "received_spts1.ts" as an example.

Usage Instructions

Logging into your VM

As described in the previous section, you can log in to your emulator VM from your Host Machine using the ssh command.

Note: In order to learn the IP address of your VM, use the RDK Browser application “tab” key to navigate to "Device Info" which will provide you the IP address. Press "Enter" key to enter Device Info

Using rmfApp

Introduction

The rmfApp application is supported for all build types. Once you SSH into your emulator VM, you can play a video stream located at a url using a source and a sink.

Where is rmfApp?

rmfApp is located in the folder: /usr/bin on your emulator VM

How to run rmfApp?

Navigate to the folder /usr/bin and run rmf App using command ./rmfApp. After the initial log statements when the rmfApp starts up, press "Enter" key to get the rmfApp prompt - "rmfApp>"

rmfApp Command Line Options

root@qemux86:~# rmfApp [-source SOURCE] [-sink SINK] [other options] url

SOURCE can be: hnsource,dvrsource ,qamsource

SINK can be:   mediaplayersink   dvrsink

Other options include:
•        -recordingId <id>: id of recording to create where <id> is a decimal number
•        -recordingTitle <title>: title of recording

Example Sequence of rmfApp usage

Before using rmfApp, it will be better to terminate rdkbrowser as it may impact the performance of playback. You may use the systemctl command to terminate rdkbrowser as shown below.

rmfApp is located in the directory /usr/bin. Navigate to the directory containing the rmfApp:

Launch RMF App using the command below:

Once the app is launched, press enter again to get the prompt "rmfApp->":

Simulated Live Playback on a Hybrid Emulator

In a simulated live playback, the following rmfApp command maybe used to playback the local SPTS video file:

launch -source qamsource -sink mediaplayersink ocap://0x125d

Where 

• source : qamsource
• sink; mediaplayersink
• url: ocap://0x125d

Simulated DVR Playback on a Hybrid Emulator

launch –source hnsource –sink mediaplayersink http://127.0.0.1:50050/received_spts1.ts

Where

• source : hnsource
• sink : mediaplayersink
• url : http://127.0.0.0:50050/received_spts1.ts 

Simulated Live Playback on a Media Client Emulator

 In a simulated live playback, the following rmfApp command maybe used to playback the local SPTS video file:

 launch –source hnsource –sink mediaplayersink http://<HYBRID IP>:8080/vldms/tuner?ocap_locator=ocap://0x125d

 Where  

• source : hnsource
• sink; mediaplayersink
• url: http://<HYBRID IP>:8080/vldms/tuner?ocap_locator=ocap://0x125d

Scheduling & Playing Back Recordings from the Media Client using Recording ID

RDK recordings on the Hybrid device are created from a cloud-based scheduler using json messages. Once the recordings are created, the rmfApp on the media client device can be used to playback the newly recorded media content. 

This section outlines the use case:

Step 1: Preconditions / Prerequisites: 

• As the hybrid VM has very limited memory and as recordings are by default stored in /opt/data/, you should create a new directory /ext_hdd/data within the external hard drive that we had set up earlier and also create a soft link to /opt/data

Note: The above directory and the soft link needs to be in place each time before scheduling recordings. 

 Your recordings will get created in the following path on the Hybrid VM:

If there is a media file created in the /chunks folder above, then the recordings have been successfully created.

Step 2: Launching rmfStreamer on Hybrid VM

There are multiple scripts in the folder /usr/bin. There are two scripts for launching rmfStreamer:

• rmfstreamer
• rmfStreamer

Note that the name of each file is similar apart from the usage of upper case and lowercase "s" in each file name.

Launch rmfStreamer using the script: rmfstreamer

if you run in into issues accessing rmfstreamer, then change the access permissions of file appropriately:

Once rmfStreamer starts, you will see log print statements on the console.

Step 3: Start playback of recorded content on Hybrid emulator from your Media Client emulator

Now you can playback from the media client using the rmfApp on the media client VM using the following sample commands:

Note: Where the recording id is "6" as set in the schedule.json message from the server. Users may write a small application to simulate the scheduler server json messages.

Westeros and WPE-webkit Support on RDKV Emulator

RDK emulator supports westeros compositor and renderer module as westeros-renderer-gl

Building WPE-image:

# To build the same for different build types, use the below command
  
#Hybrid
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment
bitbake rdk-generic-hybrid-wpe-image

To test WPE image from the VM console

1)Boot the VM in NAT mode and ssh in to the VM to get the console as mentioned above.

ex: ssh -p 2222 root@localhost

2)Then type the following command

To support westeros surface width and height are HD so emulator need to set HD resolution

To enable support for 1280x720 resolution in emulator please follow the steps mentioned in this page.
This will help us in adding custom resolution in Virtual Box.

Applications testing over westeros Compositor

1) ssh login to the Emulator

Westeros compositor will  run automatically in startup of Emulator image

run following commands in terminal for manual starting the compositor on Emulator if needed

$ mkdir -p /run/user/0
$ export XDG_RUNTIME_DIR=/run/user/0/
$ westeros --renderer <renderer module> --display <socket-name> &
$ westeros --renderer /usr/lib/libwesteros_render_gl.so.0.0.0 --display WPE &
$ gdisplay start
$ export WAYLAND_DISPLAY=WPE

westeros compositor will launch

Testing Westeros_compositor

to test westeros compositor with simple egl test apliaction

run westeros_test

# After Launching westeros compositor in emulator
$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE
$ westeros_test
(or)
$ westeros_test --display WPE

Testing Videosink on Westeros Compositor

$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE

#Check the plugin in image
$ gst-inspect-1.0 westerossink

# To play the video and render on westeros compositor
$ gst-launch-1.0 playbin uri=http://localhost:50050/received_spts1.ts videosink=westerossink

Testing WPE-WEBKIT on Westeros compositor

ssh to emulator VM terminal run following commands

$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE
$ WPElancher <http url >

Ex: WPELauncher http://easyhtml5video.com

$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE
$ WPELauncher http://www.youtube.com/tv
 

Note: Video Positioning is not proper with the present video sink so positioning is not setting properly as of now in Emulator. We will update it once it is done**

Closedcaption support in RDK Emulator

1)Boot the VM in NAT mode and ssh in to the VM to get the console.

ex: ssh -p 3022 root@localhost

2)To check the closedcaption in rmfapp start the rmfapp and launch a video as shown below

ex: cd /usr/bin; ./rmfApp

rmfApp->launch -source hnsource -sink mediaplayersink http://127.0.0.1:50050/received_spts1.ts

now you will be able to see ccdata displayed on sccsreen

3)To enable or disable closedcaption rendering in rmfApp user “e” or “enable” to enable closedcaption and “d” or “disable” to disable the closedcaption

ex: rmfApp->d

expexted output: closedcaption rendering should stop on screen.

rmfApp->e

expected output: Closedcaption rendering should start on screen

4)To show and hide the closedcaption after enabling the cc rendering user “s” or “show” tp show the cc window and “h” or “hide” to hide the cc window

example: rmfApp->h

expected output: CC window should not be visible on screen

To show the closedcaption again type the command "s" in rmfapp as shown below.

rmfApp->s

expected output: CC window should be visible on screen.

5)To pause and play the video after launching the video as shown below

ex: rmfApp->launch -source hnsource -sink mediaplayersink http://127.0.0.1:50050/received_spts1.ts

rmfApp->p (To Pause the video)

expected output: Stop the playing video also closedcaption rendering should stop

To resume the video paused type the command "p" again in rmfapp as shown below.

rmfApp->p (To play the video)

expected output: Video playing should resume and closedcaption rendering aswell.

6)To test for the video playing with tsb do as shown below.

Ex: rmfApp-> launch -source hnsource -sink mediaplayersink -tsb http://127.0.0.1:8080/vldms/tuner?ocap_locator=ocap://0x125d&tsb=60

rmfApp->p (to pause the video)

expected output: The video playing should stop and cc rendering aswell.

rmfApp->l (to switch to live)

expected output: Video should switch back to live and cc rendering should resume

7)Checking closedcaptioning in recorded content. 

After recording the video using the method provided in the above link using rmfApp try to play the recorded content.

Ex: To view the recording list

rmfApp-> l

expected output : To show the list.

total Space: 1886208000 bytes

free Space: 358744064 bytes

number of recordings= 1

-------------------------------------

recording 0 id 30 title "Recording_tile"

-------------------------------------

Now play the recorded content as shown below.

RmfApp->launch -source dvrsource -sink mediaplayersink dvr://local/30

expected output: Recording content should play along with closedcaption rendering.

Note: To play the recorded content use dvr://local/id where id is the recordingid.

8) To exit from the rmfApp first kill the running proccess and then press q to quit

Ex: rmfApp->kill 1

rmfApp->q

Yocto 2.2 (morty) support in RDK Emulator

Downloading Source Code & Building (morty version of RDK-Emulator)

The following commands fetches the source code of emulator using repo tool

#Yocto-2.2 Build (morty builds)
 
$ mkdir emulator-morty && cd emulator-morty
 
 # Download code in yocto integration mode

$ repo init -u https://code.rdkcentral.com/r/manifests -b morty -m emulator.xml

$ repo sync
 
# To build the same for different build types, use the below command
  
# Mediaclient
MACHINE=qemux86mc-morty source meta-cmf/setup-environment
bitbake rdk-generic-mediaclient-wpe-image
  
#Hybrid
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment
bitbake rdk-generic-hybrid-wpe-image
 
# Note
VMWare Player 6.X or less only supported to get wpe-webkit browser support
Host OS ubuntu 12.04 32-Bit

#Yocto-2.2 Build (RDK-DEV-1901 builds)

$ mkdir emulator-rdk-dev && cd emulator-rdk-dev

# Download code in yocto integration mode

for Non-ASP:

$ repo init -u https://code.rdkcentral.com/r/manifests -b rdk-dev-1901 -m rdkv-extsrc.xml

for ASP:

$ repo init -u https://code.rdkcentral.com/r/manifests -b rdk-dev-1901 -m rdkv-asp-extsrc.xml

$  repo sync

# To build the same for different build types, use the below command

# Mediaclient
MACHINE=qemux86mc-morty source meta-cmf/setup-environment
bitbake rdk-generic-mediaclient-wpe-image
  
#Hybrid
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment
bitbake rdk-generic-hybrid-wpe-image

#To build TDK-images

# Mediaclient
MACHINE=qemux86mc-morty source meta-cmf/setup-environment
bitbake rdk-generic-mediaclient-wpe-tdk-image
  
#Hybrid
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment
bitbake rdk-generic-hybrid-wpe-tdk-image

# Note
VMWare Player 6.X or less only supported to get wpe-webkit browser support
Host OS ubuntu 12.04 32-Bit

Bringing up the Emulator on VMWare Player

Install VMplayer in Host Machine

Use the below Link download to install VMware Player on host

https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/5_0|PLAYER-504|product_downloads

After downloading

sudo ./VMware-Player-<Version>.bundle (LInux OS)

Run  VMware-Player-<Version>.exe  (Windows OS)

Reason for VMplayer: in Mesa Higher versions EGL-PLATFORM fbdev is not available as it is deprecated so we tried using DRM (Direct Rendering Manager driver for graphics)

for DRM driver is available only in vmware only (vmwgfx so we have gone for VMware Player)
 

Steps to bring up RDK Emulator on VMware Player

1        Once VMware Player is installed, open the VMWare Player  using the command

2       Click File --> Create a New Virtual Machine --> Select  'i will install my operating system later' --> click Next

3       Select 'Linux' --> Version  'Other Linux 3.x kernel' --> Click Next --> Give name --> Click Next

4       Maximum Disk Size : 8 Gb --> Select 'Store Virtual Disk as a Single File' --> Click Next --> Memory for this Virtual Machine '512 Mb' --> Click 'Close'  --> Click  'Finish'

5       Click 'Edit virtual machine settings' --> select Hard Disk (IDE) --> Click 'Remove'   -->Click  'Add'  --> Select Hard Disk  --> Select  'Use existing Virtual Hard disk'

6       File browse and set the path to the *.vmdk  file --> Click Finish --> Click 'Keep Existing Format'

7       Network Adapter select Bridge Adapter  --> Click Save

8       Click Play Virtual Machine

         Cannot connect the virtual device ide1:0 because no corresponding device is available on the host.
         Do you want to try to connect this virtual device every time you power on the virtual machine? [YES] [NO]

          You select [NO]

9       This will bring the emulator up with the initial splash screen followed by RDK-Browser as startup application.

*** Note :  No support for Shared Folder.

step 1:

Step 2:

Step3:

Step 4:

Step 5:

Click 'Save'  --> Click  'Finish'

Click 'Edit virtual machine settings' --> select Hard Disk (IDE) --> Click 'Remove'   -->Click  'Add'  --> Select Hard Disk  --> Select  'Use existing Virtual Hard disk'

Step 6:

Step 7:

Step 8:

Step 9:

Step 10:

Step 11:

step 12:

Applications testing over westeros Compositor

WPELauncher  (wpewebkit default browing Application)

1) ssh login to the Emulator

   systemctl stop wpe-launcher ( this will stop the wpe-webkit browser

to launch any url through wpe launcher use this script sh startWPE.sh

ex:

sh startWPE.sh http://www.easyhtml5video.com

sh startWPE.sh http://www.google.com

Using rmfApp

for using rmfApp in morty builds need to follow the below steps

in ssh terminal of emulator type the following commands

1. systemctl stop westeros-startup ( to stop westeros-compositor)
2. rmmod vmwgfx
   
   

now you can see tty terminal console of emulator

from ssh terminal follow the normal rmfApp playback usage steps mentioned in this guide

Known Issues:

1. westeros Mouse click does not work.
2. DRM drivers does not work properly with virtualbox (virtualbox is unsupported for browser applications and graphics drivers)
3. VMware player supported Till 6.0.x version and lower versions only for RDK Emulator.

PXSCENE Support Test Procedure in Emulator

for using morty emulator WPE image we can validate pxscene examples in emulator

Pxscene works over the wayland compositor (westeros compositor)

Before launching pxscene examples need to export these parameters and run pxscene examples

$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE
Example 1 :
$ ./pxscene ( will launch default browser.js)
Example 2 :
$ ./pxscene http://www.pxscene.org/examples/px-reference/gallery/fancy.js
Example 3 :
$ ./pxscene http://www.pxscene.org/examples/px-reference/gallery/gallery.js
Example 4 : 
$ ./pxscene http://www.pxscene.org/examples/px-reference/gallery/picturepile.js

Please find screen shots attached

1. Browser.js

2.Fancy.js

Gallery.js

Picturepile.js

RDKBROWSER2 Support Test Procedure in Emulator

for using morty emulator WPE image we can validate rdkbrowser2 examples in emulator

works over the wayland compositor (westeros compositor)

For testing rdkbrowser2

$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE

 Example 1 :
$ ./rdkbrowser2 ( will launch http://www.example.com)
Example 2 :
$ ./rdkbrowser2 --url http://www.google.com
Example 3 :
$ ./rdkbrowser2 --url http://www.youtube.com/tv
Example 4 : 
$ ./rdkbrowser2 --url http://www.easyhtml5video.com

Note: Video performance is gittery in emulator with westerosink ( software of emulator
WEBBGL related urls not suported as graphics GPU available in the VMplayer is having limitation
with 3d graphics renderering

 

Cursor will work with rdkbrowser2

Ex: Picture-1 google.com

Ex 2: Youtube.com playback with westeros-sink

Ex 3 easyhtml5video.com