From: Ryan Raasch <ryan.raasch@gmail.com>
To: Shun-Yu Chang <shunyu.chang@gmail.com>
Cc: V4L-Linux <video4linux-list@redhat.com>
Subject: Re: Camera preview, thin lines in the frames
Date: Thu, 12 Nov 2009 14:49:51 +0100 [thread overview]
Message-ID: <4AFC127F.4070300@gmail.com> (raw)
In-Reply-To: <e858e0620911120339t68172862i7f6ec38e88bcf426@mail.gmail.com>
Shun-Yu Chang wrote:
> Hello, list:
> I am new to v4l2. I am working on integrating a usb camera device on
> the beagleboard(Omap3530 dev board).
> Now I met a camera preview issue that is there are thin lines coming out
> in the frames.
> I still have no idea how to describe this exactly. It's like the images
> shows here,
> http://0xlab.org/~jeremy/camera_preview.html
I have two guesses. One is the jpeg compression ,or is it jpeg? Try
saving in raw RGB or Ycbcr format and viewing with imagemagick.
Does this happen in live preview? Maybe write data from camera directly
to screen to see if happening there.
The second would be the FIFO (hadn't worked with omap before) levels of
the data lines to the processor in the kernel.
Look at the system processor (top) usage to see how much cpu% is being
used. USB has high overhead.
Regards,
Ryan
> I modified capture.c sample to save the frames to picture files. So in
> my guess, the problem is not in userspace. And this is not happen on my
> laptop with the usb camera.
> Could anybody give me a clue ? Any one would be thankful.
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2009-11-12 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 11:39 Camera preview, thin lines in the frames Shun-Yu Chang
2009-11-12 13:49 ` Ryan Raasch [this message]
2009-11-12 15:54 ` Shun-Yu Chang
2009-11-12 16:03 ` Ryan Raasch
2009-11-12 16:35 ` Shun-Yu Chang
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=4AFC127F.4070300@gmail.com \
--to=ryan.raasch@gmail.com \
--cc=shunyu.chang@gmail.com \
--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