libv4l2: error getting pixformat: Bad address

[Sneha Murganoor]

Hi All,
I am getting the below error when i connect sony bd player to HD FURY to HD PVR..
but not when i connect roku set up box to HD FURY to HD PVR.

libv4l2: error getting pixformat: Bad address

Command i use..
gst-launch  v4l2src device="/dev/video0" num-buffers=200 ! mpegtsdemux ! video/x-h264 ! decodebin2 ! ffmpegcolorspace ! xvimagesink sync=false
Setting pipeline to PAUSED ...
libv4l2: error getting pixformat: Bad address
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
^CCaught interrupt -- handling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 2502810354 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Please help me in resolving this..

Thanks,
Sneha

[David Röthlisberger]

On 16 Aug 2013, at 12:49, Sneha Murganoor wrote:
>
> I am getting the below error when i connect sony bd player to HD FURY to HD PVR..
> but not when i connect roku set up box to HD FURY to HD PVR.
>
> libv4l2: error getting pixformat: Bad address

Are you 100% sure that the cause of the libv4l2 error is the Roku vs.
the Sony player? The reason I ask is that the HDPVR has a known
stability problem that is very intermittent (but once the problem
happens, the HDPVR consistently fails until you power-cycle it).
See http://stb-tester.com/hardware.html

Many people here on this mailing list and on the linuxtv and mythtv
mailing lists have repeatedly made wrong assumptions about what was
triggering the problem. The infrequent intermittent nature of the
problem makes it hard to collect statistically significant data, but
once you do, you might find that it is unrelated to the Roku
specifically. Unless, of course, you have *never* gotten the Roku
working with the HDPVR.

Do make sure that the HD Fury's blue light is on; the HDPVR gives the
same libv4l2 error when it has no input video. Note that the upcoming
3.11 linux kernel has a fix to the HDPVR driver so that it gives
different error messages for "no video" and "HDPVR crashed".

[Sneha Murganoor]

Hi David,

After few power cycles of HD PVR with whole of testbed, now both setup box are working fine .. Yes it is intermittent failure, let me try with kernel version 3.11

Thanks,

Sneha

[Sneha Murganoor]

Hi All,

I am facing this issue again .. this time with "Vizio setup box". How to debug and fix this intermittent failures?
Now both Sony BD Player and Roku are working fine as stated connection being : Setup box to HD FURY III to HD PVR.  But when Vizio setup box is placed, it is failing.

I still have to work on lot of devices, is there are a good soln instead of this topology?

Thanks,
Sneha

[David Röthlisberger]

On 21 Aug 2013, at 13:59, Sneha Murganoor wrote:
>
> I am facing this issue again .. this time with "Vizio setup box". How to debug and fix this intermittent failures?
> Now both Sony BD Player and Roku are working fine as stated connection being : Setup box to HD FURY III to HD PVR. But when Vizio setup box is placed, it is failing.

If I understand your question correctly, you are asking about a known
intermittent hardware failure with the Hauppauge HDPVR video-capture
device. I don't think anybody on the GStreamer list is going to be able
to help you, so I'm dropping GStreamer from the discussion by BCCing
them in this email. If they want to re-join the discussion they can
reply.

The Hauppauge HDPVR has known stability problems. You can read all about
it here: http://stb-tester.com/hardware.html

Workarounds have been discussed on the stb-tester mailing list before:
https://groups.google.com/d/msg/stb-tester/OWddTrrwhqY/xiwwtGQxGywJ

As I explained in my last email, the problem is unlikely to be related
to the "Vizio setup box", which I assume is your video source. Do you
have new evidence to suggest that the problem *isn't* intermittent, but
is specifically related to which video source is connected to the HDPVR?

> I still have to work on lot of devices, is there are a good soln instead of this topology?

Some of us on this list are using Blackmagic Intensity Pro video-capture
cards with stb-tester, and others are using SD capture hardware like
http://linuxtv.org/wiki/index.php/Easycap

Cheers,
Dave.

[Sneha Murganoor]

Hi David,

That is right, Problem isnt intermittent. It is related to video source. I had faced similar problem with Roku and Sony which after sometime started working fine.

Same setup when I try with Vizio setup box it fails with
"libv4l2: error getting pixformat: Bad address" and immediately i try with Sony/Roku setup box, it works fine. So it is not because hardware gets heated up.

How to debug? Which mailing list can i post this?

Thanks,

Sneha

[David Röthlisberger]

On 21 Aug 2013, at 16:46, Sneha Murganoor wrote:
>
> That is right, Problem isnt intermittent. It is related to video source. I had faced similar problem with Roku and Sony which after sometime started working fine.
>
> Same setup when I try with Vizio setup box it fails with
> "libv4l2: error getting pixformat: Bad address" and immediately i try with Sony/Roku setup box, it works fine. So it is not because hardware gets heated up.

How many times have you tried this? An intermittent problem means that
you have to repeat your experiments many times before you can be certain
of the root cause.

> How to debug? Which mailing list can i post this?

This mailing list is the right place. :-)

How to debug: Are you sure that the Vizio device is connected properly?
Is the blue light on the HD Fury on? If you connect the Component output
of the HD Fury to a TV, do you see video? If you connect the HD Fury to
the HDPVR again, and you connect the HDPVR's Component pass-through
output to a TV, do you see video?

[karthik...@gmail.com]

Hi Dave-

We are also currently facing same problem as what Sneha initially faced.

We connected HDPVR with our STBT and installed gstreamer-ffmpeg package. Restarted the system and try to execute below commands.

[root@localhost ~]# gst-launch v4l2src device="/dev/video0" ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink

Setting pipeline to PAUSED ...
libv4l2: error getting pixformat: Bad address
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
^CCaught interrupt -- handling interrupt.
Interrupt: Stopping pipeline ...

Execution ended after 6524418384 ns.

Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

We restared HDPVR many times but still getting same error, can you please suggest us on this?


Thanks for your support.

Best Regards,
Karthik

[Lewis Haley]

> libv4l2: error getting pixformat: Bad address

This message basically means "I'm not getting any video/frames." You will see it, amongst many other reasons,
if the device/STB you are testing it not turned on. Make sure your HDFury is lit up (it lights up bright blue - you
can't mistake it).

As far as it being a HDPVR error, try turning it off for a while (several minutes).

[karthik...@gmail.com]

Hi Lewis-

Thanks for your response.

We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR (Model 1212) and executed above said comments but encountered with errors.

We've installed only Gstreamer -ffmpeg.

We tried this on both Fedora 18 and 19.

Should I need to install any additional drivers/packages on Fedora? Please let me know your suggestions.

Thanks
Karthik

[Máté Szendrő]

> We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR

Which output of the set-top-box is connected? If you're using the HDMI output with a simple HDMI to component converter, you might be interested in this article: http://www.hdfury.com/hdmi-hdcp/hdcphdmi-definition/ or check the following topic: https://groups.google.com/forum/#!searchin/stb-tester/hdcp/stb-tester/JwBZfyo-nmk/voxxt76nb68J.

Regards,

Máté

--
You received this message because you are subscribed to the Google Groups "stb-tester" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stb-tester+...@googlegroups.com.
To post to this group, send email to stb-t...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/stb-tester/9e534729-add2-4364-b7f6-454e9900e554%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[David Röthlisberger]

On 25 Sep 2013, at 08:44, karthik...@gmail.com wrote:
>> libv4l2: error getting pixformat: Bad address
>

> We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR (Model 1212) and executed above said comments but encountered with errors.

If you're not using the HDPVR's component input, you might need to tell
it which input to use, with `v4l2-ctl` (install the `v4l-utils`
package). Use `v4l2-ctl --help`; there will be a way to show the
available inputs and a way to choose the input you want.

[David Röthlisberger]

P.S. I have added this information to
http://stb-tester.com/hardware.html#hauppauge-hd-pvr

[karthik...@gmail.com]

On Wednesday, September 25, 2013 2:52:45 PM UTC+5:30, David Röthlisberger wrote:
> On 25 Sep 2013, at 09:54, David Röthlisberger wrote: > On 25 Sep 2013, at 08:44, karthik...@gmail.com wrote: >>> libv4l2: error getting pixformat: Bad address >> >> We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR (Model 1212) and executed above said comments but encountered with errors. > > > If you're not using the HDPVR's component input, you might need to tell > it which input to use, with `v4l2-ctl` (install the `v4l-utils` > package). Use `v4l2-ctl --help`; there will be a way to show the > available inputs and a way to choose the input you want. > P.S. I have added this information to http://stb-tester.com/hardware.html#hauppauge-hd-pvr

David and Mate- Thanks for your respones.

We tried setting the input using v4l2-ctl and executed full command but we are encountered with same bad address error. do we need to check any other things on this? please suggest.

Thanks
Karthik

[Lewis Haley]

So, what actually is your setup? Set top box => HDPVR => PC?
What type of cable are you connecting the set top box to the HDPVR with?
What did you change in v4l2-ctl?

[karthik...@gmail.com]

On Thursday, September 26, 2013 5:02:18 PM UTC+5:30, Lewis Haley wrote:
> So, what actually is your setup? Set top box => HDPVR => PC? What type of cable are you connecting the set top box to the HDPVR with? What did you change in v4l2-ctl?On Thursday, 26 September 2013 12:06:20 UTC+1, karthik...@gmail.com wrote: On Wednesday, September 25, 2013 2:52:45 PM UTC+5:30, David Röthlisberger wrote: > On 25 Sep 2013, at 09:54, David Röthlisberger wrote: > On 25 Sep 2013, at 08:44, karthik...@gmail.com wrote: >>> libv4l2: error getting pixformat: Bad address >> >> We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR (Model 1212) and executed above said comments but encountered with errors. > > > If you're not using the HDPVR's component input, you might need to tell > it which input to use, with `v4l2-ctl` (install the `v4l-utils` > package). Use `v4l2-ctl --help`; there will be a way to show the > available inputs and a way to choose the input you want. > P.S. I have added this information to http://stb-tester.com/hardware.html#hauppauge-hd-pvr David and Mate- Thanks for your respones. We tried setting the input using v4l2-ctl and executed full command but we are encountered with same bad address error. do we need to check any other things on this? please suggest. Thanks Karthik

Hi Lewis-

We have the setup as Set top box => HDPVR => PC. We used Composite cable between set top box and HDPVR, used USB cable between HDPVR and PC.

For v4l2-ctl, we have installed v4l-utlis package,

==> v4l2-ctl --list-inputs
then we searched for list of inputs and found composite as 2, then we set input as 2
==> v4l2-ctl --set-input 2

After this we executed below command in terminal, we haven't encountered any error but the video wasn't displayed.

[root@localhost root123]# gst-launch v4l2src device="/dev/video0" ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink

Setting pipeline to PAUSED ...

Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

which is the blocker on this? do we need to use different cables/ need to change anything in the command? Please let us know.

Thanks
Karthik

[Máté Szendrő]

> We used Composite cable between set top box and HDPVR

If you're using analogue input then the capture card cannot negotiate the video format. You have to specify it in the `norm` property of `v4l2src`. Run `gst-inspect v4l2src` to see the available options.

Cheers,

Máté

Thanks
Karthik

--
You received this message because you are subscribed to the Google Groups "stb-tester" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stb-tester+...@googlegroups.com.
To post to this group, send email to stb-t...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/stb-tester/fb0ff12c-f498-4c43-ab12-1c3b1ae4e98f%40googlegroups.com.

[karthik...@gmail.com]

On Thursday, September 26, 2013 6:39:08 PM UTC+5:30, Máté Szendrő wrote:
> > We used Composite cable between set top box and HDPVRIf you're using analogue input then the capture card cannot negotiate the video format. You have to specify it in the `norm` property of `v4l2src`. Run `gst-inspect v4l2src` to see the available options. Cheers,MátéOn 26 September 2013 14:06, <karthik...@gmail.com> wrote: On Thursday, September 26, 2013 5:02:18 PM UTC+5:30, Lewis Haley wrote: > So, what actually is your setup? Set top box => HDPVR => PC? What type of cable are you connecting the set top box to the HDPVR with? What did you change in v4l2-ctl?On Thursday, 26 September 2013 12:06:20 UTC+1, karthik...@gmail.com wrote: On Wednesday, September 25, 2013 2:52:45 PM UTC+5:30, David Röthlisberger wrote: > On 25 Sep 2013, at 09:54, David Röthlisberger wrote: > On 25 Sep 2013, at 08:44, karthik...@gmail.com wrote: >>> libv4l2: error getting pixformat: Bad address >> >> We are not using HD Fury, we've connected STBT only with Hauppuage HDPVR (Model 1212) and executed above said comments but encountered with errors. > > > If you're not using the HDPVR's component input, you might need to tell > it which input to use, with `v4l2-ctl` (install the `v4l-utils` > package). Use `v4l2-ctl --help`; there will be a way to show the > available inputs and a way to choose the input you want. > P.S. I have added this information to http://stb-tester.com/hardware.html#hauppauge-hd-pvr David and Mate- Thanks for your respones. We tried setting the input using v4l2-ctl and executed full command but we are encountered with same bad address error. do we need to check any other things on this? please suggest. Thanks Karthik Hi Lewis-We have the setup as Set top box => HDPVR => PC. We used Composite cable between set top box and HDPVR, used USB cable between HDPVR and PC. For v4l2-ctl, we have installed v4l-utlis package,==> v4l2-ctl --list-inputs then we searched for list of inputs and found composite as 2, then we set input as 2 ==> v4l2-ctl --set-input 2After this we executed below command in terminal, we haven't encountered any error but the video wasn't displayed. [root@localhost root123]# gst-launch v4l2src device="/dev/video0" ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink Setting pipeline to PAUSED ...Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ...New clock: GstSystemClockwhich is the blocker on this? do we need to use different cables/ need to change anything in the command? Please let us know. ThanksKarthik-- You received this message because you are subscribed to the Google Groups "stb-tester" group. To unsubscribe from this group and stop receiving emails from it, send an email to stb-tester+...@googlegroups.com. To post to this group, send email to stb-t...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/stb-tester/fb0ff12c-f498-4c43-ab12-1c3b1ae4e98f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.

Hi Mate-

Thanks for your help,

We set Norm property and tried executing the command as below

gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink

We didn't face any error but still the video was not grabbed.

Note: We are working on Oracle VM Box and fedora 19(now).

Please suggest if anything else i need to check.

Thanks
Karthik

[David Röthlisberger]

On 27 Sep 2013, at 07:51, karthik...@gmail.com wrote:
> Note: We are working on Oracle VM Box and fedora 19(now).

Try with native hardware to rule out issues with the VM (the HDPVR is
very fragile if your PC hardware isn't fast enough). If that works, then
you can investigate why the VM isn't working (is direct USB access not
configured properly, or is your hardware just too slow to run a virtual
machine, etc.)

[karthik...@gmail.com]

On Friday, September 27, 2013 3:41:40 PM UTC+5:30, David Röthlisberger wrote:
> On 27 Sep 2013, at 07:51, karthik...@gmail.com wrote: > Note: We are working on Oracle VM Box and fedora 19(now). Try with native hardware to rule out issues with the VM (the HDPVR is very fragile if your PC hardware isn't fast enough). If that works, then you can investigate why the VM isn't working (is direct USB access not configured properly, or is your hardware just too slow to run a virtual machine, etc.)

Hi,

We dumped the raw video for 1 min on Linux(which installed on VM Box)via command and the video was playing in VLC player.
So what we feel is that there is no problem with driver or the set up. But we have problem in construting the pipeline for gst-launch.

Can anyone share what is the pipline command used with HD-PVR?
We have used below one, do we need to change anything on this command.

gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink

Thanks for your help.

[Lewis Haley]

x-H264. You've had this wrong from your first post...
 

Thanks for your help.

[karthik...@gmail.com]

On Friday, September 27, 2013 9:30:16 PM UTC+5:30, Lewis Haley wrote:
> On Friday, 27 September 2013 14:23:57 UTC+1, karthik...@gmail.com wrote: On Friday, September 27, 2013 3:41:40 PM UTC+5:30, David Röthlisberger wrote: > On 27 Sep 2013, at 07:51, karthik...@gmail.com wrote: > Note: We are working on Oracle VM Box and fedora 19(now). Try with native hardware to rule out issues with the VM (the HDPVR is very fragile if your PC hardware isn't fast enough). If that works, then you can investigate why the VM isn't working (is direct USB access not configured properly, or is your hardware just too slow to run a virtual machine, etc.) Hi, We dumped the raw video for 1 min on Linux(which installed on VM Box)via command and the video was playing in VLC player. So what we feel is that there is no problem with driver or the set up. But we have problem in construting the pipeline for gst-launch. Can anyone share what is the pipline command used with HD-PVR? We have used below one, do we need to change anything on this command. gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink x-H264. You've had this wrong from your first post...  Thanks for your help.

Thank you for your reply.
We are trying both vidoe/x-264 and video/x-H264. we are not getting any error when we try to execute the command. But we are not getting any gstreamer pop-up where we can see the video stream.
Can anyone help us on this. we are completely struck with not getting the gstreamer pop up.

[Lewis Haley]

Try a lowercase h.

[karthik...@gmail.com]

On Monday, September 30, 2013 2:38:53 PM UTC+5:30, Lewis Haley wrote:
> Try a lowercase h. On Monday, 30 September 2013 07:05:43 UTC+1, karthik...@gmail.com wrote: On Friday, September 27, 2013 9:30:16 PM UTC+5:30, Lewis Haley wrote: > On Friday, 27 September 2013 14:23:57 UTC+1, karthik...@gmail.com wrote: On Friday, September 27, 2013 3:41:40 PM UTC+5:30, David Röthlisberger wrote: > On 27 Sep 2013, at 07:51, karthik...@gmail.com wrote: > Note: We are working on Oracle VM Box and fedora 19(now). Try with native hardware to rule out issues with the VM (the HDPVR is very fragile if your PC hardware isn't fast enough). If that works, then you can investigate why the VM isn't working (is direct USB access not configured properly, or is your hardware just too slow to run a virtual machine, etc.) Hi, We dumped the raw video for 1 min on Linux(which installed on VM Box)via command and the video was playing in VLC player. So what we feel is that there is no problem with driver or the set up. But we have problem in construting the pipeline for gst-launch. Can anyone share what is the pipline command used with HD-PVR? We have used below one, do we need to change anything on this command. gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-264 ! decodebin2 ! ximagesink x-H264. You've had this wrong from your first post...  Thanks for your help. Thank you for your reply. We are trying both vidoe/x-264 and video/x-H264. we are not getting any error when we try to execute the command. But we are not getting any gstreamer pop-up where we can see the video stream. Can anyone help us on this. we are completely struck with not getting the gstreamer pop up.

Hi,
I tried lower case. For lower case I'm getting error.
gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-h264 ! decodebin2 ! ximagesink

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data flow error.
Additional debug info:
gstbasesrc.c(2625): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming task paused, reason not-negotiated (-4)
Execution ended after 685818092 ns.

Setting pipeline to PAUSED ...

[David Röthlisberger]

On 30 Sep 2013, at 11:40, karthik...@gmail.com wrote:
> gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-h264 ! decodebin2 ! ximagesink

Thank you for including the actual command line and the actual output.
Now we can see what's happening. Before we had to guess.

> ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data flow error.

This shows that the error is coming from the "v4l2src" element. In other
words, the error isn't from later parts of the pipeline; you simply
aren't getting video from the HDPVR. Maybe your "norm" parameter is
wrong. Use "gst-inspect v4l2src" to see all the possible values.

[David Röthlisberger]

On 30 Sep 2013, at 11:40, karthik...@gmail.com wrote:
> gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-h264 ! decodebin2 ! ximagesink

P.S. Are you sure that "/dev/video0" is your HDPVR device?

[karthik...@gmail.com]

Hi David,
Thanks for your reply.
Yes /dev/video0 is my HDPVR device. I confirmed using dmesg command.

Regards,
Karthik

[David Röthlisberger]

On 1 Oct 2013, at 09:22, David Röthlisberger wrote:
> On 30 Sep 2013, at 11:40, karthik...@gmail.com wrote:
>> gst-launch v4l2src device="/dev/video0" norm=PAL ! mpegtsdemux ! video/x-h264 ! decodebin2 ! ximagesink

>> ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data flow error.

Try also "xvimagesink" instead of "ximagesink".