public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas@bppiac.hu>
To: video4linux-list@redhat.com
Subject: [Fwd: [gst-devel] RFC: multi channel frame grabber card support]
Date: Wed, 30 Apr 2008 13:48:41 +0200	[thread overview]
Message-ID: <48185C99.807@bppiac.hu> (raw)

hi,
a few weeks ago i send this mail to gstreamer-devel but it seems nobody 
reply to it. i'd like to know the v4l people's opinion's about it. or 
may be we've to modify the v4l or v4l2 interface in the bellow case to 
give us more device?
i'd like to know your opinion.
thanks in advance.
yours.

-------- Original Message --------
Subject: [gst-devel] RFC: multi channel frame grabber card support
Date: Fri, 11 Apr 2008 14:51:23 +0200
From: Farkas Levente <lfarkas@bppiac.hu>
To: Gstreamer <gstreamer-devel@lists.sourceforge.net>

hi,
as i wrote earlier we'd like to add support for multi channel frame
grabber cards in gstreamer. what's the problem:
currently there are the only hardware video input supported by gstreamer
is the v4l or v4l2 compatible video sources. there are good for common
hardware like ip camera, tv card (with tunner) or other hardware like
s-video input etc. but there are many kind of card which has more
(4,8,16,24) input channel (usually analog input). there card can give
raw or encoded video sources. but these usually has one physical devices
ie. one /dev/videoX devices (in this case we've got n composite input).
we'd like to build in this case n pipeline for the n input channel. one
of the simple example IVC-100 card which has one bt878 chip and 4
composite input and one 4 channel multiplexer.
http://www.iei.com.tw/en/product_IPC.asp?model=IVC-100G
in this case we can use v4l and choose one of the channel but we'd like
to build 4 pipeline and set different parameters on the different
pipeline's source properties (like frame rate, resolution etc). what's
more we'd like to modify the source element properties during it's
running eg. i'd like to modify the 2nd channel frame rate while wouldn't
like to stop the other 4 pipeline!!! and it's an important feature.
what we can do?
- we can create a new source element with 4 output pads,
- or create a new source element with one output pad, but we'd like to
create 4 such source element which can parallel use the same device's
different input channel.
the first would be the easier, but in this case we can't modify one of
the input channel's parameter without stop the other pipelines:-( or can
i do it somehow? and in this case all of the pipeline has to be run in
the same process.
in the second case we can start and stop the pipeline independently
what's more use them in different process, but we probably have to
create some kind of master/controller process which control the access
of the source elements to the device.
what do you think about it?
what do you suggest about it?
what's your comments?
thanks in advance.
yours.

-- 
    Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

-- 
   Levente                               "Si vis pacem para bellum!"

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

             reply	other threads:[~2008-04-30 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 11:48 Farkas Levente [this message]
2008-04-30 13:54 ` [Fwd: [gst-devel] RFC: multi channel frame grabber card support] Daniel Glöckner
2008-04-30 14:12   ` Farkas Levente

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48185C99.807@bppiac.hu \
    --to=lfarkas@bppiac.hu \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox