Installing STB Tester

[Yougant....@relianceada.com]

Hi David & William,

For past few days i have been looking into options for automated STB testing and came across STB TESTER Tool.

I have gone through the article available on the internet but need further clarification regarding implementation of the tool.

I would like to know to exact step by step process on installing the tool and also apart from  Hauppauge HD PVR can we use any other frame grabber device.

Look forward for your reply.

Thanks.


Regards
Yougant Somvanshi

Reliance Communications Limited.
2nd Floor, RTIC Building
DAKC,New Mumbai - 400710

Mobile no: 9699651949
Desk Phone: +912230372458

Enjoy the widest reach of 3G services across India only On Reliance
www.rcom.co.in/3G



The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

[David Röthlisberger]

On 17 Apr 2013, at 06:28, Yougant....@relianceada.com wrote:
> I would like to know to exact step by step process on installing the
> tool

You will need a Linux system. If you use Fedora we have pre-built RPMs
available. Otherwise you will need to build stb-tester from source.

Then you will need to create a lirc configuration file to describe the
infrared protocol used by your remote control.

Full step-by-step instructions are here:
http://stb-tester.com/getting-started.html

> apart from Hauppauge HD PVR can we use any other frame
> grabber device.

You can use any video-capture hardware with video-for-linux drivers
(like the Hauppauge HDPVR); or other hardware if it has a custom
GStreamer source element, like the BlackMagic Intensity Pro
( http://www.blackmagicdesign.com/products/intensity/ ).

> The information contained in this electronic message (email) and any
> attachments to this email are intended for the exclusive use of the
> addressee(s) and access to this email by any one else is unauthorised.

> [...]

Please be aware that this is a public mailing list with
publically-viewable archives. :-)

[David Röthlisberger]

On 10 Jun 2013, at 10:19, Yougant Somvanshi wrote:
> Hi David,
>
> I have managed to install Stb Tester but on executing the command
>
> gst-launch videotestsrc \
> ! stbt-templatematch template=stb-tester/tests/videotestsrc-bw.png \
> ! ffmpegcolorspace ! ximagesink
>
> i am not able to get the red border.

Hmmm. If you use the same pipeline but with "gst-launch --messages", do
you see messages from the "stbt-templatematch" element saying whether or
not it matched?


> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/loader.py",
> line 413, in loadTestsFromName
> addr.filename, addr.module)
> File "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/importer.py",
> line 47, in importFromPath
> return self.importFromDir(dir_path, fqname)
> File "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/importer.py",
> line 94, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
> File "/home/yougant/Stb-Tester/stb-tester/stbt.py", line 63, in <module>
> import pygst # gstreamer
> ImportError: No module named pygst
>
> [...]
>
> when i try to do sudo apt-get install python-gst0.10
>
> Reading state information... Done
> python-gst0.10 is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


Presumably you're using Debian or Ubuntu. I don't have such a system in
front of me right at the moment, but this is how I'd investigate:

* Can I import this package from python?
python -c 'import pygst'

If the above fails,

* What files are installed by the "python-gst0.10" package?
dpkg -L python-gst0.10

(You're looking for a "pygst.py")

* Where is my "python" installed?
which python

* Where does my python search for packages?
http://docs.python.org/2/tutorial/modules.html#the-module-search-path


Hope this helps,

Dave.

[David Röthlisberger]

On 12 Jun 2013, at 13:36, you...@gmail.com wrote:
> Thanks for the help i manged to resolve the error but now on executing

That's good news. What was the problem? If you post how you resolved
it to this mailing list, it will help people who run into the same
problem in the future.

> gst-launch videotestsrc \
> ! stbt-templatematch template=stb-tester/tests/videotestsrc-bw.png \
> ! ffmpegcolorspace ! ximagesink
>

> gives me error WARNING: erroneous pipeline: no element "stbt-templatematch"


Are you following these instructions:
http://stb-tester.com/getting-started.html#install-stb-tester-from-source

After following those instructions, is the GStreamer plugin installed to
the location that those instructions say it should be installed to?

[you...@gmail.com]

Hi David i simply downloaded fedora and used the links given on stb-tester.com

Installation seems to be working fine, but now i would like to integrate a stb and test the same if you can please guide me how to proceed further also

How do i play any video file that is present on my desktop using gstreamer.

Sorry have been bothering you off late but i am trying to implement this tool.

Thanks alot for all your support

[you...@gmail.com]

Hi David,

I am using a EasyCap DC60 device for AV capture i have been trying to install its drivers and i am getting an error while installing

i have been refering the readme file to install the drivers, where it has been mentioned on run the command sudo ./install.sh after executing the command i get the o/p :

ERROR: step failed: make
/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c: In function ‘easycap_mmap’:
/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c:2675:19: error: ‘VM_RESERVED’ undeclared (first use in this function)
/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c:2675:19: note: each undeclared identifier is reported only once for each function it appears in
/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c: In function ‘easycap_usb_probe’:
/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c:4416:3: error: implicit declaration of function ‘err’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[3]: *** [/home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.o] Error 1
make[2]: *** [_module_/home/yougant/EASYCAP/easycap_dc60.0.9/src] Error 2
make[1]: *** [all] Error 2
make: *** [build] Error 2

can you please help me out

[David Röthlisberger]

On 21 Jun 2013, at 10:33, you...@gmail.com wrote:
> I am using a EasyCap DC60 device for AV capture i have been trying to install its drivers and i am getting an error while installing
>

> /home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c: In function ‘easycap_mmap’:
> /home/yougant/EASYCAP/easycap_dc60.0.9/src/easycap_main.c:2675:19: error: ‘VM_RESERVED’ undeclared (first use in this function)
>

> can you please help me out

It seems that the driver you are trying to build is incompatible with
your Linux kernel. I googled for "VM_RESERVED" and it seems it was
removed from the Linux kernel in version 3.7.

Note also that the driver for your device seems to be already present in
Linux kernels from 3.7, so you don't need to build it yourself. The
driver is called "stk1160". See
http://easycap.blogspot.co.uk/2012/10/stk1160-news.html

[you...@gmail.com]

Hi David,

I have Kernel version 3.8.13-100.fc17.i686.PAE running do i need to install kernel 3.7?? if yes please let me know once after installing kernel 3.7 & its header files how do i switch from kernel 3.8.13-100.fc17.i686.PAE
to kernel 3.7

[David Röthlisberger]

On 21 Jun 2013, at 11:03, you...@gmail.com wrote:
> On Friday, June 21, 2013 3:20:49 PM UTC+5:30, David Röthlisberger wrote:
>> Note also that the driver for your device seems to be already present in
>> Linux kernels from 3.7, so you don't need to build it yourself. The
>> driver is called "stk1160". See
>> http://easycap.blogspot.co.uk/2012/10/stk1160-news.html
>

> I have Kernel version 3.8.13-100.fc17.i686.PAE running do i need to install kernel 3.7??

No, you don't. The stk1160 driver is present in kernels from 3.7
onwards. That includes 3.8.

[you...@gmail.com]

Hi
Now that the drivers are installed and i have also installed mplayer when i connect the Easycap device to the computer and STB is connected to the easycap device and i try to execute the command mplayer tv:// it just shows me a blank green screen am i going wrong anywhere??

[David Röthlisberger]

On 21 Jun 2013, at 11:26, you...@gmail.com wrote:
> Now that the drivers are installed and i have also installed mplayer when i connect the Easycap device to the computer and STB is connected to the easycap device and i try to execute the command mplayer tv:// it just shows me a blank green screen am i going wrong anywhere??

Have you tried googling for help? Does the Easycap device have its own
support forums?

[you...@gmail.com]

Have been looking up for the same will let you know if i find anything meanwhile thanks alot for the support really appreciate all your help

[you...@gmail.com]

Hi David,
I managed to play the video by installing gstreamer missing element ffmpeg after which i was able to capture the video using gst-launch, but only problem is the video is black & white and there is no audio

[you...@gmail.com]

> I managed to play the video by installing gstreamer missing element ffmpeg after which i was able to capture the video using gst-launch, but only problem is the video is black & white and there is no audio.





Hi David,

I have been trying to record a test script but have been unsuccessful. I referred to a video on stb-tester.com wherein it has been mentioned that in order to create a test script execute command
stbt record but it launches window which shows test pattern and not the set top box video which is connected , do i need to make any changes in

stbt.conf

[global]
source_pipeline=videotestsrc is-live=true

DO I NEED TO CHANGE videotestsrc to v4l2src

or any other changes required

[David Röthlisberger]

On 22 Jun 2013, at 12:26, you...@gmail.com wrote:
> I have been trying to record a test script but have been unsuccessful. I referred to a video on stb-tester.com wherein it has been mentioned that in order to create a test script execute command
> stbt record but it launches window which shows test pattern and not the set top box video which is connected , do i need to make any changes in stbt.conf

stbt record --help

and

http://stb-tester.com/getting-started.html

[you...@gmail.com]

On Saturday, June 22, 2013 5:07:14 PM UTC+5:30, David Röthlisberger wrote:
> On 22 Jun 2013, at 12:26, you...@gmail.com wrote:
>
> > I have been trying to record a test script but have been unsuccessful. I referred to a video on stb-tester.com wherein it has been mentioned that in order to create a test script execute command
>
> > stbt record but it launches window which shows test pattern and not the set top box video which is connected , do i need to make any changes in stbt.conf
>
>

> Hi David,

I finally have all things setup only thing remaining is integrating the RedRat3, now i have been trying to create a config file for my remote but unfortunately when i try irrecord command
it asks for me to enter button name, but when i enter any name (like HOME) it says it is not a under namespace and to disable namespace use --disable-namespace
after which i executed the command irrecord --list-namespace which lists all button names
so when i select any of these name for eg. KEY_SCROLLDOWN and then system asks me to press the button when i press same button on my remote control it give me an output:
something went wrong, please try again.

I have found a config file which seems to be a match for my remote but not sure about it because when i run irsend command no action is executed neither does it give me any error

[David Röthlisberger]

On 29 Jun 2013, at 09:41, you...@gmail.com wrote:
> I finally have all things setup only thing remaining is integrating the RedRat3, now i have been trying to create a config file for my remote but unfortunately when i try irrecord command
> it asks for me to enter button name, but when i enter any name (like HOME) it says it is not a under namespace and to disable namespace use --disable-namespace
> after which i executed the command irrecord --list-namespace which lists all button names
> so when i select any of these name for eg. KEY_SCROLLDOWN and then system asks me to press the button when i press same button on my remote control it give me an output:
> something went wrong, please try again.
>
> I have found a config file which seems to be a match for my remote but not sure about it because when i run irsend command no action is executed neither does it give me any error

Some devices' protocols are easier to record than others. You'll have
the best results if you tell "irrecord" what protocol your remote
control uses: Ask the manufacturer of your remote control if you don't
know, then find a config file for that protocol[1] and give that to
"irrecord". (See the "irrecord" man page[2]). If you don't know what the
protocol is, you can try using "irrecord" in "raw" mode. Finally, there
was a previous post on this forum[3] with some additional suggestions.
Good luck!

[1] http://lirc.sourceforge.net/remotes/
[2] http://linux.die.net/man/1/irrecord
[3] https://groups.google.com/d/msg/stb-tester/fh2Tm1QyaVQ/bmzvzXn2-LQJ

[you...@gmail.com]

Hi David,

I have manged to create the config file for my remote using irrecord -f

Now when i execute:

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=file:///dev/stdin --control=lirc::lirc0 (where lirc0 is name of my remote in the lirc.conf file)

i get the stbt-record screen with the video playing and message
Waiting for keypresses from standard input...

but when i press any remote control button keeping redrat in front it does not take any input

Also when i execute the same command the second time the stbt record screen does not pop up- with message
libv4l2: error setting pixformat: Device or resource busy
Waiting for keypresses from standard input...

how can i free the resource ??

Also i need to execute quite a lot of test cases i wanted to know how do i create testscript with names for individual test cases.

[you...@gmail.com]

Also i just wanted to confirm the test-up
From STB AV cable goes to EasyCap DC60 frame graber, the frame grabber is connected to PC & redrat is directly connected to PC

[David Röthlisberger]

On 1 Jul 2013, at 12:59, you...@gmail.com wrote:
> stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=file:///dev/stdin --control=lirc::lirc0 (where lirc0 is name of my remote in the lirc.conf file)
>
> i get the stbt-record screen with the video playing and message
> Waiting for keypresses from standard input...
>
> but when i press any remote control button keeping redrat in front it does not take any input

Read the documentation for "--control-recorder" in the stbt manual.

> Also i need to execute quite a lot of test cases i wanted to know how do i create testscript with names for individual test cases.

"stbt record" creates a file called "test.py". Rename the file to a
different name, or put it in a different directory.

[David Röthlisberger]

On 1 Jul 2013, at 13:25, you...@gmail.com wrote:
> Also i just wanted to confirm the test-up
> From STB AV cable goes to EasyCap DC60 frame graber, the frame grabber is connected to PC & redrat is directly connected to PC

See the diagram here: http://stb-tester.com/jenkins.html
(ignore the "Jenkins master PC" in the diagram).

[you...@gmail.com]

Hi David,

I dont understand when i execute command

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=file:///dev/stdin --control=lirc::lirc0

should i be making changes to control recorder or control.

I could not understand from the stbt manual documentation if you can please explain it in a easier manner

[David Röthlisberger]

On 2 Jul 2013, at 10:15, you...@gmail.com wrote:
> I dont understand when i execute command
> stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=file:///dev/stdin --control=lirc::lirc0
>
> should i be making changes to control recorder or control.
>
> I could not understand from the stbt manual documentation if you can please explain it in a easier manner

Have you read the explanation of "control" and "control-recorder"
at http://stb-tester.com/getting-started.html#stbt-record ?

If it's still not clear, please let me know.

[you...@gmail.com]

Yes i have gone through what i dont understand that in order for redrat to work we put the control=lirc:/var/run/lirc/lircd:lirc0

for control-recorder=file:///dev/stdin i am not able to relate between control & control-recorder i think this is where i am stuck

[you...@gmail.com]

OK while performing stbt record control recorder will record the input so what should control-recorder=???? and control=??? and while
we run a particular script what should control=???

[you...@gmail.com]

also should i be making these changes to stbt.conf or writing a command in terminal??

[David Röthlisberger]

On 2 Jul 2013, at 11:19, you...@gmail.com wrote:
> Yes i have gone through what i dont understand that in order for redrat
> to work we put the control=lirc:/var/run/lirc/lircd:lirc0
>
> for control-recorder=file:///dev/stdin i am not able to relate between
> control & control-recorder i think this is where i am stuck

http://stb-tester.com/getting-started.html#stbt-record says:

stbt record will listen for remote-control keypresses on
the *control-recorder* and will forward those keypresses to the system
under test using the *control*.

I have just added a wiring diagram that will hopefully make this
clearer: http://stb-tester.com/getting-started.html#wiring-diagram
-- thanks for the feedback.

> OK while performing "stbt record", "control recorder" will record the

> input so what should control-recorder=????

That depends on how you want to *record* button presses during "stbt
record". You have several choices; they are documented at
http://stb-tester.com/stbt.html#additional-options-to-stbt-record

> and control=???

That depends on how you want to *send* button presses to the
system-under-test during "stbt record".

> and while we run a particular script what should control=???

That depends on how you want to *send* button presses during "stbt run".

> should i be making these changes to stbt.conf or writing a command in
> terminal??

Whichever you prefer.

[you...@gmail.com]

OK i understand
Now that i refer the stbt manual

--control-recorder=lirc:([<lircd_socket>]|[<hostname>:]<port>):<remote_control_name>
since i am using A hardware infrared receiver controlled by the lirc which in my case will be

--control-recorder=lirc:/var/run/lirc/lircd:lirc0 and same for

control

but i am not able to record anything

[you...@gmail.com]

Hi David,

finally with the command

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=lirc:/var/run/lirc/lircd:lirc0 --control=lirc::lirc0

i am able to execute actions and i can even see screen shots being generated when i press keys,

what i would like to know is:

1. If i hold the remote in front of RedRat3 and give the commands the screen being captured is only for live tv playing
As i have referred the earlier wired diagram you have sent while recording does stbt need to have receiver as well as emitter (2 redrat devices connected at same time) so that receiver can capture the commands and emitter can send the command to stb so that as the test script is getting generated it captures the screen
AND
2. how do i end a test script : i have performed whatever required actions were required i had to and now i need to stop recording so how do i do it

because if i simply close the stbt-record screen and when i execute the command:

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=lirc:/var/run/lirc/lircd:lirc0 --control=lirc::lirc0
second time i get the error

[you...@gmail.com]

Also the test.py file generated is blank i cannot see any script generated

[David Röthlisberger]

On 3 Jul 2013, at 07:38, you...@gmail.com wrote:
> does stbt need to have receiver as well as emitter (2 redrat devices
> connected at same time)

Yes. When stb-tester receives a keypress from the "control-recorder", it
takes a screenshot *before* sending the keypress on to the system under
test via the "control". So you have to make sure that the system under
test isn't receiving the IR directly from your remote control.

OR, instead of using "--control-recorder=lirc:..." you can use
"--control-recorder=file:///dev/stdin" and type each key name (the same
as the key names in your lirc config file) on your keyboard, followed
by RETURN.

> how do i end a test script

Press Control-C. Please read http://stb-tester.com/getting-started.html
-- this is documented there in the "stbt record" section.

[you...@gmail.com]

Ok got it.

So i need a receiver and emitter connected when i am performing stbt record??

because if i see the video on introduction page you pressed remote buttons by keeping redrat in front (wherein you only had redrat receiver and the actions were getting executed that does not happen in my case)

and if i use --control-recorder=file:///dev/stdin i am able to write a test script but the actions are not executed on stb.

if i write a script for eg.
press('KEY_HOME') it should launch HOME screen, that does not happen instead only the live video which is being played is captured

[you...@gmail.com]

if you can please share your stbt.conf file script or else can you please share the details of stbt record as in what are you using in command stbt record

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=lirc:/var/run/lirc/lircd:lirc0 (what are you using here)
--control=lirc::lirc0 (what are you using here)

[Lewis Haley]

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=lirc:/var/run/lirc/lircd:lirc0 (what are you using here)
--control=lirc::lirc0 (what are you using here)

The device you have set for --control-recorder and --control are the same - they must be different.

Remember that the --control-recorder device is how YOU send commands, and the --control device is how you PC tells you STB what to do.
As for why your recorded test script would be blank: it would only be completely blank (but existing) if the stbt setup processes, i.e. starting
the GStreamer Pipeline, does not happen successfully. If the pipeline is started successfully, then the test script will contain "import stbt" on
line 1, and then any --control-recorder commands given.

Also, I'm not convinced that just "v4l2src" as your source pipeline will work.
What pipeline did you give to gst-launch to get to be able to see video from your set top box?

[you...@gmail.com]

i have been using v4l2src and it has been working fine

stbt record --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control-recorder=lirc:/var/run/lirc/lircd:lirc0

> --control=lirc::lirc0

as a matter of fact when i use this command i have been able to view live tv.

well i have also tried to replace control-recorder=file:///dev/stdin so what i can enter the test script using my keyboard and keeping the control=lirc::lirc0

so now when i write a command in test scrip and press enter the screenshot for live tv is captured but the command is not executed

I have also tried connecting one more redrat device while executing stbt record
control-recorder=lirc:/var/run/lirc/lircd:lirc0
> --control=lirc::lirc1

but this also did not help i am not able to understand where am i going wrong.

[David Röthlisberger]

On 4 Jul 2013, at 13:47, you...@gmail.com wrote:
> now when i write a command in test scrip and press enter the screenshot
> for live tv is captured but the command is not executed

Your infrared emitter isn't working. You need to figure out why.
Please read the following for debugging hints:
http://stb-tester.com/getting-started.html#using-a-real-control
https://groups.google.com/forum/#!msg/stb-tester/fh2Tm1QyaVQ/H2rxVzUsIdYJ

> I have also tried connecting one more redrat device while executing
> stbt record

> --control-recorder=lirc:/var/run/lirc/lircd:lirc0

> --control=lirc::lirc1
> but this also did not help

If you want to use multiple lirc infrared devices, see
http://stb-tester.com/multi-lirc.html

[Lewis Haley]

Can you send commands with irsend? Like:

% irsend SEND_ONCE lirc0 KEY_HOME?

Also I would recommend not calling your control config lirc0 as this is the name of the device i.e. /dev/lirc0.
We name our controls after the brand of the boxes they control.

Some other things to check:
Is lirc service running?

% sudo systemctl list-units | grep lirc

should report
"lirc.service              loaded active running       LSB: Linux Infrared Remote Control daemon"

Is the IR-blaster listed under /dev
% ls /dev/lirc*

I have also tried connecting one more redrat device

We have had troubles getting more than one RedRat to work per PC. It is not as trivial as plugging 2 in
and referring to them solely by the /dev names.

[you...@gmail.com]

On Thursday, July 4, 2013 6:35:37 PM UTC+5:30, Lewis Haley wrote:
> Can you send commands with irsend? Like:
>
> % irsend SEND_ONCE lirc0 KEY_HOME?
>
> Also I would recommend not calling your control config lirc0 as this is the name of the device i.e. /dev/lirc0.
> We name our controls after the brand of the boxes they control.
>
> Some other things to check:
> Is lirc service running?
>
> % sudo systemctl list-units | grep lirc
>
> should report
> "lirc.service              loaded active running       LSB: Linux Infrared Remote Control daemon"
>
> Is the IR-blaster listed under /dev

> % ls /devting one more redrat device

>
>
> We have had troubles getting more than one RedRat to work per PC. It is not as trivial as plugging 2 in
> and referring to them solely by the /dev na

The LIRC service is running i have checked irsend command and it works. It works even when both redrat devices are connected and both of them respond to irsend command,
but maybe there is some more further configuration required in order for both the redrat devices to perform simultaneously any ideas??

[Lewis Haley]

For performing or recording a single test, you only need 1 RedRat. As you say, if you have 2 plugged in, then any command
sent with `irsend` goes to both Blasters, which is not what is needed.

> % ls /devting one more redrat device

Sorry, this has become garbled and I don't know what you were trying to say.

Basically, if this isn't working:

% stbt record --source-pipeline=v4lsrc --sink-pipeline='ximagesink sync=false' --control=lirc::lirc0 --control-recorder=file:///dev/stdin
i.e. You input commands but they are not sent to the set top box.
Then the problem is with this bit "--control=lirc::lirc0".

Can you post/link to your recorded lircd.conf file, ie.
% cat /etc/lirc/lircd.conf

[you...@gmail.com]

Hi Lewis,

Yes even i suspect the same, some problem with "--control=lirc::lirc0" i have recorded raw input commands using irrecord -f , i have tried and the commands do get executed using irsend command.

Below is the remote control config file

begin remote

name lirc0
flags RAW_CODES
eps 30
aeps 100

gap 123749

begin raw_codes

name KEY_POWER
296 807 282 1532 277 1532
249 2806 249 1277 249 1277
249 1000 249 2113 249 13027
249 863 249 1835 249 726
249 1558 249 726 249 863
249 726 230 746 262

name BTN_0
295 807 281 1528 278 1531
251 2805 251 1277 251 1277
251 1001 251 2114 251 13026
251 861 251 2114 251 723
251 1559 248 726 262 2796
288 686 320 655 349

name BTN_1
295 807 281 1532 276 1532
250 2804 250 1278 250 1278
250 1002 250 2113 250 13027
250 861 250 1558 250 725
250 1558 250 725 229 1163
246 728 276 699 291

name BTN_2
290 807 282 1532 276 1532
249 2806 249 1278 249 1278
249 1002 249 2113 248 13027
248 862 249 1697 249 724
249 1558 249 724 242 1010
276 700 290 683 306

name BTN_3
297 806 283 1527 279 1529
249 2804 249 1278 249 1278
249 999 249 2111 249 13026
249 861 249 1418 249 724
249 1558 249 724 242 1289
275 699 306 669 335

name BTN_4
297 806 283 1527 279 1529
250 2805 250 1275 250 1275
250 1000 250 2113 249 13027
250 861 254 1277 254 721
262 1547 288 686 320 1349
347 628 378 597 407

name KEY_INFO
296 807 281 1532 277 1532
252 2806 252 1278 252 1278
252 1002 252 2113 252 13027
252 861 252 1140 252 723
252 1558 242 732 262 1548
289 684 320 655 349

name KEY_VOLUMEUP
295 807 282 1528 278 1531
254 2805 254 1279 254 1279
254 999 254 2113 252 13027
252 862 254 862 252 724
249 1559 260 714 291 1797
317 656 349 625 378

name KEY_VOLUMEDOWN
400 706 328 1480 280 1529
310 2748 306 1224 302 1229
254 998 254 2111 236 13039
259 854 290 2768 316 659
348 1460 375 877 405 1681
432 543 464 510 493

name KEY_CHANNELUP
295 807 282 1530 278 1530
254 2806 254 1278 254 1278
251 1000 254 2112 254 13027
250 862 254 723 254 723
251 1557 250 723 251 1976
260 714 291 682 320

name KEY_CHANNELDOWN
296 807 282 1527 279 1529
253 2804 253 1278 253 1278
253 999 253 2113 250 13027
253 861 253 1694 253 723
250 1558 260 993 290 683
320 655 349 625 378

name KEY_OK
451 656 374 1435 280 1528
257 2802 257 1274 359 1172
252 999 252 2111 252 13023
252 859 255 1970 274 700
305 1504 332 643 363 610
392 584 421 553 451

name KEY_SCROLLUP
296 807 282 1528 278 1531
251 2805 251 1279 251 1279
251 1003 251 2113 250 13027
250 861 251 1003 251 723
251 1559 250 723 242 1707
274 699 306 670 335

name KEY_SCROLLDOWN
296 807 281 1532 277 1532
249 2806 249 1280 249 1280
249 1003 249 2113 249 13025
249 862 249 1559 249 723
249 1559 247 1003 249 865
247 729 262 713 291

name BTN_5
296 807 282 1532 277 1532
252 2806 252 1281 253 1281
252 1000 252 2113 253 13026
253 862 253 1281 249 723
252 1558 249 1421 260 712
291 684 320 654 349

name BTN_6
296 807 282 1527 279 1529
249 2804 249 1275 249 1275
249 1000 249 2111 249 13026
249 861 253 1139 253 722
253 1558 260 1409 289 824
320 655 349 625 378

name KEY_G
297 807 281 1532 277 1532
251 2806 251 1281 251 1281
251 1003 251 2113 251 13027
251 862 251 1281 250 723
251 1559 251 1003 251 1141
261 714 291 684 320

name KEY_BACK
297 809 280 1532 277 1532
249 2806 249 1279 250 1279
249 1003 249 2113 249 13027
249 862 250 1140 250 724
250 1559 249 1003 239 1290
275 700 306 668 335

name BTN_7
297 807 281 1532 276 1532
249 2806 249 1279 253 1279
249 1002 249 2113 249 13027
249 863 253 1002 253 725
253 1558 249 1002 249 1420
249 725 244 730 276

name KEY_HOME
296 806 299 1511 279 1529
252 2804 252 1278 252 1278
252 1000 252 2113 249 13025
249 861 252 1418 252 723
252 1558 260 991 290 963
319 655 349 625 378

name KEY_RED
297 809 280 1532 277 1532
250 2806 250 1280 250 1280
250 1003 250 2113 250 13027
250 863 250 863 250 726
250 1559 250 1003 250 1559
249 726 250 726 247

name KEY_GREEN
296 807 282 1530 278 1530
250 2804 250 1275 250 1275
250 1001 250 2112 250 13027
250 861 250 1001 250 723
250 1558 245 1426 245 1005
261 714 291 683 320

name KEY_YELLOW
296 809 280 1532 276 1532
276 2784 254 1277 254 1277
254 1001 252 2113 252 13025
250 862 254 724 254 724
252 1557 252 1280 260 1407
289 686 320 656 349

name KEY_BLUE
296 807 282 1527 279 1529
250 2804 250 1279 250 1279
250 1001 250 2113 250 13026
250 861 252 724 250 724
242 1567 260 1409 289 1241
319 656 349 625 378

name KEY_0
297 807 282 1528 278 1531
248 2805 248 1278 252 1278
248 1001 248 2113 248 13026
248 861 252 1140 252 722
252 1558 260 1131 290 1101
319 655 349 625 378

name KEY_1
299 809 280 1532 277 1532
251 2806 251 1277 251 1277
251 1002 251 2113 251 13026
251 861 251 2530 251 722
251 1558 251 722 251 2392
260 714 291 683 320

name KEY_2
295 807 282 1530 278 1530
254 2806 248 1280 248 1280
252 1001 248 2113 248 13026
248 864 252 864 248 724
248 1561 245 1424 275 1115
304 671 334 640 363

name KEY_3
295 807 281 1528 278 1531
251 2805 251 1279 251 1279
251 1001 252 2112 252 13026
249 861 251 1418 251 723
262 1547 288 1242 319 654
349 627 378 597 407

name KEY_4
295 807 282 1532 275 1532
252 2806 252 1278 252 1278
252 1001 252 2113 252 13025
252 861 252 1278 252 723
252 1558 249 1281 246 869
275 699 291 683 320

name KEY_5
297 807 281 1528 278 1531
251 2805 251 1279 251 1279
251 1001 251 2113 251 13025
251 861 251 1141 251 723
251 1558 260 1271 290 963
319 655 349 625 378

name KEY_6
295 807 282 1532 277 1532
248 2806 248 1279 250 1279
250 1002 248 2113 250 13025
250 862 248 1002 248 723
248 1558 248 1282 248 1142
261 713 291 684 320

name KEY_7
296 807 281 1532 276 1532
249 2806 249 1279 251 1279
249 1002 249 2113 249 13027
249 862 251 1557 249 724
251 1557 249 1141 249 724
242 732 276 699 291

name KEY_8
297 807 282 1532 276 1532
276 2784 254 1277 254 1277
254 1001 251 2113 251 13023
254 861 254 1418 251 724
251 1557 251 1140 261 853
291 684 320 655 349

name KEY_9
297 807 282 1527 279 1529
255 2804 255 1279 255 1279
250 1001 250 2114 250 13027
250 862 250 1279 250 724
233 1576 260 1132 290 962
319 656 349 625 378

name KEY_MUTE
294 807 281 1528 278 1531
251 2805 251 1279 251 1279
251 1001 251 2113 251 13026
246 863 251 863 251 724
246 1561 246 1284 261 1269
290 684 320 655 349

end raw_codes

end remote

[Lewis Haley]

Well, there's nothing obviously wrong with the config file...

So, some more questions. Please actually carry out these instructions again,
even if you've done them at some point previously.

What do you get from
% irsend LIST "" ""
?

If you start a GStreamer as:
% gst-launch v4l2src ! ximagesink sync=false
You see the video from your set top box?
And then with the pipeline still up on screen, if you press the actual KEY_HOME
on the physical remote do you see the expected result on screen?

The same thing but do
% irsend SEND_ONCE lirc0 KEY_HOME
?

If you make a test script called test.py that is just:

import stbt

stbt.press('KEY_HOME')

And run
% stbt run --source-pipeline=v4l2src --sink-pipeline='ximagesink sync=false' --control=lirc::lirc0 test.py
Does that work?

[you...@gmail.com]

irsend LIST "" ""

it list reliance (its name of my remote which i have changed from lirc0 to reliance in order to avoid any confusion)

When i start gstreamer using : gst-launch v4l2src device=/dev/video0 ! xvimagesink it plays the current video and i am able to execute actions with my remote control

irsend SEND_ONCE lirc0 KEY_HOME:
i tried send this command and HOME is launched if i do it independently

if i launch gstreamer and then try sending the command, action is not executed.

and when i run the test.py it does not work.

[Lewis Haley]

i tried send this command and HOME is launched if i do it independently

What do you mean "if you do it independently" ?

[you...@gmail.com]

if i use gst-launch v4l2src ! ximagesink sync=false to launch gstreamer

i do not get any video

Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not negotiate format
Additional debug info:
gstbasesrc.c(2830): gst_base_src_start (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
Check your filtered caps, if any
Setting pipeline to NULL ...
Freeing pipeline ...

[you...@gmail.com]

By independently i meant the stb is connected to tv and using redrat device i execute the command

[Lewis Haley]

That's not related to the IRBlaster though.

I can reproduce that error message if I execute that command.

What's the exact pipeline you have given gst-launch to be able to see live tv on-screen (i.e. with movement).

[you...@gmail.com]

i am using gst-launch v4l2src device=/dev/video0 ! xvimagesink

[Lewis Haley]

Have you tried this pipeline instead:

v4l2src device=/dev/video0 ! mpegtsdemux ! video/x-h264 ! decodebin2 ! xvimagesink sync=false

[you...@gmail.com]

On Friday, July 5, 2013 4:28:44 PM UTC+5:30, Lewis Haley wrote:
> Have you tried this pipeline instead:
>
> v4l2src device=/dev/video0 ! mpegtsdemux ! video/x-h264 ! decodebin2 ! xvimagesink sync=false

i just tried did not work gives me an output:

[Lewis Haley]

I'm afraid I'm at a loss then. It is inconceivable that GStreamer would affect the working of irsend - they are completely unrelated.

One final thing to try, is if you launch videotestsrc with GStreamer, and then send an IR signal with irsend to the box which you are
monitoring on a television (i.e. not with GStreamer). The pipeline for videotestsrc will be something like:

gst-launch videotestsrc is-live=true ! video/x-raw-yuv,width=320,height=240 ! xvimagesink

[you...@gmail.com]

The irsend command works but redrat doesn't seem to be working when i execute stbt-record cant figure out whats going wrong??

[you...@gmail.com]

Hi David,

If you can please let me know if there is any link that needs to be established between stbt control & stbt control-recorder because i dont see problem in any other area,
I have been trying to troubleshoot the same but could not think anything apart from this.
Please let me know.

[David Röthlisberger]

On 8 Jul 2013, at 13:22, you...@gmail.com wrote:
> On Thursday, July 4, 2013 6:29:27 PM UTC+5:30, David Röthlisberger wrote:
>>> now when i write a command in test scrip and press enter the screenshot
>>> for live tv is captured but the command is not executed
>>
>> Your infrared emitter isn't working. You need to figure out why.
>> Please read the following for debugging hints:
>> http://stb-tester.com/getting-started.html#using-a-real-control
>> https://groups.google.com/forum/#!msg/stb-tester/fh2Tm1QyaVQ/H2rxVzUsIdYJ
>

> If you can please let me know if there is any link that needs to be established between stbt control & stbt control-recorder because i dont see problem in any other area,

Are you saying that when you run a test script with "stbt run",
the infrared emitter *does* work?

[you...@gmail.com]

No when i run stbt run there is no action executed

[David Röthlisberger]

So why do you think that the problem has anything to do with
"control-recorder"? "control-recorder" is only necessary for "stbt
record", i.e. for interactively recording new test scripts.

If I were you I would focus on getting "stbt run" working, and then
write test scripts by hand, using "stbt screenshot" to capture
screenshots.

[you...@gmail.com]

OK.
But there is one more concern i.e when i am executing stbt record the stbt control does not execute the action so is stbt run & this problem related because when i am executing irsend command it is executed.

[you...@gmail.com]

Hi,

When i am executing

stbt run --control=lirc::reliance --source-pipeline= v4l2src --sink-pipeline='xvimagesink sync=false' test.py

it gives me an error
usage: stbt run [-h] [--control CONTROL] [--source-pipeline SOURCE_PIPELINE]
[--sink-pipeline SINK_PIPELINE] [-v]
script
stbt run: error: unrecognized arguments: test.py

test.py is the script generated from stbt record so how come its not recognized??

[David Röthlisberger]

On 9 Jul 2013, at 05:51, you...@gmail.com wrote:
> stbt run --control=lirc::reliance --source-pipeline= v4l2src --sink-pipeline='xvimagesink sync=false' test.py
>
> it gives me an error
> usage: stbt run [-h] [--control CONTROL] [--source-pipeline SOURCE_PIPELINE]
> [--sink-pipeline SINK_PIPELINE] [-v]
> script
> stbt run: error: unrecognized arguments: test.py

What happens if you add "-v" (for verbose output) and you remove
"test.py" from the command line? What does it think each of the
parameters are?

[you...@gmail.com]

if i execute

stbt run --control=lirc::reliance --source-pipeline= v4l2src --sink-pipeline='xvimagesink sync=false' -v

it give me an output:

stbt-run: Arguments:
control: lirc::reliance
script: v4l2src
sink_pipeline: xvimagesink sync=false
verbose: 1
source_pipeline:
Traceback (most recent call last):
File "/usr/libexec/stbt/stbt-run", line 25, in <module>
stbt.init_run(args.source_pipeline, args.sink_pipeline, args.control)
File "/usr/libexec/stbt/stbt.py", line 616, in init_run
_display = Display(gst_source_pipeline, gst_sink_pipeline)
File "/usr/libexec/stbt/stbt.py", line 685, in __init__
self.source_bin = self.create_source_bin()
File "/usr/libexec/stbt/stbt.py", line 729, in create_source_bin
False)
glib.GError: link without source element

[David Röthlisberger]

And what does this tell you:

> stbt-run: Arguments:
> source_pipeline:

[you...@gmail.com]

Those fields remain blank there is nothing there in the output

[you...@gmail.com]

why does it take

stbt-run: Arguments:
control: lirc::reliance

script: v4l2src (why is it taking script as v4l2src ??????????????????)

[you...@gmail.com]

Oh i had some spaces in my commands this is the command & the output

stbt run --control=lirc::reliance --source-pipeline=v4l2src --sink-pipeline='xvimagesink sync=false' -v

Output:

usage: stbt run [-h] [--control CONTROL] [--source-pipeline SOURCE_PIPELINE]
[--sink-pipeline SINK_PIPELINE] [-v]
script

stbt run: error: too few argumen

[you...@gmail.com]

and when i execute

stbt run --control=lirc::reliance --source-pipeline=v4l2src --sink-pipeline='xvimagesink sync=false' -v test.py

output is:

stbt-run: Arguments:
control: lirc::reliance

script: test.py

sink_pipeline: xvimagesink sync=false
verbose: 1

source_pipeline: v4l2src
stbt-run: LircRemote: Connecting to /var/run/lirc/lircd
stbt-run: LircRemote: Connected to /var/run/lirc/lircd
FAIL: test.py: invalid syntax (test.py, line 4)

Traceback (most recent call last):

File "/usr/libexec/stbt/stbt-run", line 33, in <module>
execfile(args.script)
File "test.py", line 4
stbt.press('press('KEY_HOME')')
^
SyntaxError: invalid syntax

[you...@gmail.com]

Hi David,

The mistake was really silly one while performing stbt record when it asked for key press i was not writing the key name instead i was writing stbt.press keyname where in only keyname is required so there was error generated and hence stbt run was not able to recognize the script now the commands are also getting executed as i generate a test script and stbt run is also working

thanks for your help

[David Röthlisberger]

On 9 Jul 2013, at 09:31, you...@gmail.com wrote:
> stbt.press('press('KEY_HOME')')
> ^
> SyntaxError: invalid syntax

To be able to write stb-tester scripts you will need to learn the python
programming language. I recommend this ebook (it's free of cost):
http://learnpythonthehardway.org/book/

This mailing list is for issues specific to stb-tester. If you need help
with python, use the resources at
http://wiki.python.org/moin/BeginnersGuide/Help

[you...@gmail.com]

Hi David,

One small issue, now when i am executing test scripts which are little lengthy (i.e lot of key presses required in the test) after executing few commands it gives me an error saying:
error: [Errno 11] Failed to connect to Lirc socket /var/run/lirc/lircd: [Errno 11] Resource temporarily unavailable

how do i resolve this??

[David Röthlisberger]

On 11 Jul 2013, at 11:23, you...@gmail.com wrote:
> One small issue, now when i am executing test scripts which are little lengthy (i.e lot of key presses required in the test) after executing few commands it gives me an error saying:
> error: [Errno 11] Failed to connect to Lirc socket /var/run/lirc/lircd: [Errno 11] Resource temporarily unavailable

I recommend that your script use a `wait_for_match` after *every*
`press`. Otherwise it becomes difficult to diagnose errors when the
script fails.

Sometimes, though, it isn't possible to put a `wait_for_match` after
every `press`. For example if you need to type in a multi-digit channel
number -- typically if you wait too long in between key presses, the
set-top box thinks you have finished and doesn't look for further
digits. In this case, you don't want to use `wait_for_match`, but
you *do* want to wait a short amount of time (for example 0.2 seconds)
before pressing the next key (to avoid the LIRC "Resource temporarily
unavailable" problem you saw). Python has a function in its standard
library to do just that -- you'll have to google for it.

The most complete solution of all would be to modify stb-tester itself
so that it retries, instead of failing, when it encounters "Resource
temporarily unavailable". Patches welcome.

[you...@gmail.com]

Hi David,

I tried installing STB Tester on one more system and sailed through entire process only problem where i got stuck is while installing

gst-plugins-good-0.10.31 it give me a error while executing make:

make[3]: Entering directory `/home/stb-tester/STB-TESTER/gst-plugins-good-0.10.31/sys/v4l2'
CC libgstvideo4linux2_la-v4l2_calls.lo
v4l2_calls.c: In function 'gst_v4l2_fill_lists':
v4l2_calls.c:297:12: error: 'V4L2_CID_HCENTER_DEPRECATED' undeclared (first use in this function)
v4l2_calls.c:297:12: note: each undeclared identifier is reported only once for each function it appears in
v4l2_calls.c:298:12: error: 'V4L2_CID_VCENTER_DEPRECATED' undeclared (first use in this function)
make[3]: *** [libgstvideo4linux2_la-v4l2_calls.lo] Error 1
make[3]: Leaving directory `/home/stb-tester/STB-TESTER/gst-plugins-good-0.10.31/sys/v4l2'
make[2]: *** [v4l2] Error 2
make[2]: Leaving directory `/home/stb-tester/STB-TESTER/gst-plugins-good-0.10.31/sys'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stb-tester/STB-TESTER/gst-plugins-good-0.10.31'
make: *** [all] Error 2


when i didnot find any solution over this i went and installed stb tester using:

sudo wget -O /etc/yum.repos.d/stb-tester.repo \http://download.opensuse.org/repositories/home:/\stb-tester/Fedora_17/home:stb-tester.repo

it was successfully installed but this time stbt folder which is generated in etc folder was not generated

i am using kernel 3.9.10-100.fc17.i686

[David Röthlisberger]

On 29 Jul 2013, at 11:40, you...@gmail.com wrote:
> gst-plugins-good-0.10.31 it give me a error while executing make:

Why are you trying to build gst-plugins-good from source?