Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Format your newly created partition with ext3 file system
$ mkfs.ext3 /dev/hdb1

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

$ mkdir /ext_hdd

$ mount /dev/hdb1 /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
$ scp <your_spts_file_name>.ts root@<your_emulator_vm_ip>:/ext_hdd
  • Back on your emulator VM, create a link in /opt/www/ to point to the external hard drive at its mount point /ext_hdd
$ ln -sf /ext_hdd/<your_spts_file_name> <your_spts_file_name>
  • 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.

$ ssh root@x.x.x.x

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,qamsource

SINK can be:   mediaplayersink 

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.

$ systemctl stop rdkbrowser.service

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

$ cd /usr/bin

Launch RMF App using the command below:

$ ./rmfApp

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

$ rmfApp->
NOTE:

Note 1: There is an additional step required prior to using the emulator because it is built without the gsttee module in gst-plugins-rdk:

Before invoking rmfapp, it is necessary to set the environment variable 'USE_GENERIC_GSTREAMER_TEE' to 'TRUE', so that mediaframework uses the generic gsttee that is built from Open Source gstreamer: 

example : 

root@qemux86hyb-morty:/usr/bin# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86hyb-morty:/usr/bin# ./rmfApp 

Note 2: In the streaming scenario it is necessary to kill the rmfStreamer process on the hybrid image, which is started automatically, and invoke it manually as illustrated below : 

Streaming Scenario : 

Hybrid : 

barracuda:~> ssh root@193.120.91.104

root@qemux86hyb-morty:/#

root@qemux86hyb-morty:/# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86hyb-morty:/# cd /usr/bin root@qemux86hyb-morty:/usr/bin# ps -aef  | grep rmf root@qemux86hyb-morty:/usr/bin#kill -9 <pid> root@qemux86hyb-morty:/usr/bin# ./rmfStreamer 

IP Client : 

barracuda:~> ssh root@193.120.91.132

root@qemux86mc-morty:/#

root@qemux86mc-morty:/# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86mc-morty:/# cd /usr/bin root@qemux86mc-morty:/usr/bin# ./rmfApp

rmfApp->launch -source hnsource -sink mediaplayersink

http://193.120.91.104:8080/vldms/tuner?ocap_locator=ocap://0x125d


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
$ rmfApp-> launch –source qamsource –sink mediaplayersink ocap://0x125d

Simulated Playback on a Hybrid Emulator


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

Where

$ rmfApp-> launch –source hnsource –sink mediaplayersink http://127.0.0.1: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
$ launch –source hnsource –sink mediaplayersink 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

mkdir -p /ext_hdd/data

ln -sf /ext_hdd/data /opt/data

NoteThe 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:

/opt/data/OCAP_MSV/0/0/DEFAULT_RECORDING_VOLUME/test

/opt/data/OCAP_MSV/0/0/DEFAULT_RECORDING_VOLUME/test/chunks

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

cd /usr/bin/

sh rmfstreamer

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

chmod 777 rmfstreamer

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:

cd /usr/bin

./rmfApp

rmfApp> launch -source hnsource -sink mediaplayersink http://<hybird_vm_ip>:8080/vldms/test?rec_id=6

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:


Code Block
languagenone
# 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

Code Block
languagenone
$ 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

for Dunfell Emulator
---------------------
$ mkdir -p /run/user/0
$ export XDG_RUNTIME_DIR=/run/user/0/
Add the below line in westeros-init.sh
export LD_PRELOAD=/usr/lib/libwesteros_gl.so.0.0.0
$ westeros --renderer /usr/lib/libwesteros_render_gl.so.0.0.0 --display WPE &

Run the commands
westeros-init.sh
westeors_test


westeros compositor will launch

Testing Westeros_compositor

to test westeros compositor with simple egl test apliaction

run westeros_test


Code Block
languagenone
# 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


Code Block
languagenone
$ 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

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

Ex: WPELauncher http://easyhtml5video.com





Code Block
languagenone
$ 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**


Yocto 2.2 (morty) support in RDK Emulator

...