Hi Hans Verkuil,
                 Thanks for your reply, I used ivtvctl --log-status for determining the video signal
I did'nt wrote any daemons nor did I hacked up driver code
I going to try ur suggestions and will get back to you soon

On 5/8/06, Hans Verkuil <[EMAIL PROTECTED]> wrote:
On Thursday 20 April 2006 07:22, Rishi Pathak wrote:
> Hi all
> Please read to get an understanding:
>
> We are having a large setup of systems having these
>  ivtv card for live
>  streaming of 150 TV channels.The output from these
>  card after
>  encoding(MPEG2)are sent to a central streaming
>  server which directs these
>  output streams from every card to users.Now for
>  regular monitoring of
>  every card(and in such every channel) I need to know
>  the following
>  1.A way by which I could test whether there is any
>  input to the card from
>  the cable(i.e. I want to know if the feeder cable is
>  plugged in or not and
>   the cable is providing input or not).

This is easy: just call VIDIOC_G_TUNER (see the V4L2 spec
http://v4l2spec.bytesex.org/spec/r8313.htm) and check the signal field.
It is 0xffff when a valid signal is available and 0 otherwise.

>  2.A method to find that encoder is giving output

Huh? You are the one that is capturing from the encoder, so you know
whether there is output or not, aren't you?

>
>  I am thinking of hooking up my monitoring code into
>  the driver code so
>  that when any problem regarding the card occur's,
>  then my code would raise
>  an alarm (i.e. send a failed service status to the
>  central monitoring
>  unit).
>  By having a hook up in your code I will not have to
>  run a daemon to
>  monitor the card.

??? What's wrong with having a daemon doing this? That's precisely what
daemons are used for. Of course, the driver is open source so you can
hack it yourself. You might look at ivtv_dualwatch_set_dual() in
ivtv-kthreads.c which runs periodically (but not yet for all hardware
types, but that is going to change soon). It already calls
VIDIOC_G_TUNER so it is easy to add your monitoring code there.

>  I tried but couldn't any document's that will
>  describe the working of the
>  driver

The source is the documentation, I'm afraid.

>  I would be very thankful if someone could give me any help.


_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to