public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: OT: Why is usb data many times the cpu hog that firewire is?
Date: Mon, 21 Feb 2005 18:40:24 +0000	[thread overview]
Message-ID: <421A2B18.2000102@grupopie.com> (raw)
In-Reply-To: <200502211325.55013.gene.heskett@verizon.net>

Gene Heskett wrote:
> On Monday 21 February 2005 12:58, Oliver Neukum wrote:
>[...]
>>A video stream over usb1.1 must be compressed due to bandwidth
>>available. Decompression needs cpu.
>>
> 
> Thats what I was afraid of, which makes using it for a motion detected 
> burgular alarm source considerably less than practical since the 
> machine must be able to do other things too.  Darn.  And its usb1.1 
> even when plugged into a 2.0 capable port.

Depending on the camera model you can try some bandwidth reduction 
measures to try to make it send uncompressed video:
  - reduce frame rate. Something as low as 2 fps should be enough for 
motion detection.
  - reduce requested resolution. This of course depends on whether you 
have enough resolution or not.
  - selecting gray scale images. I don't know if your motion detection 
software is greatly affected by this, or not.

USB1.1 bandwidth is enought for 640x480, 8 bits gray scale (or color, 8 
bits bayer pattern), at 3 fps.

Of course, you can always buy a USB2.0 camera :)

-- 
Paulo Marques - www.grupopie.com

All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)

  parent reply	other threads:[~2005-02-21 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 17:16 OT: Why is usb data many times the cpu hog that firewire is? Gene Heskett
2005-02-21 17:58 ` Oliver Neukum
2005-02-21 18:25   ` Gene Heskett
2005-02-21 18:29     ` Wichert Akkerman
2005-02-21 22:08       ` Gene Heskett
2005-02-22 23:10         ` Matt Mackall
2005-02-23 13:13           ` Paulo Marques
2005-02-23 17:15             ` Geert Uytterhoeven
2005-02-21 18:40     ` Paulo Marques [this message]
2005-02-21 18:46     ` Oliver Neukum
2005-02-24 11:52     ` David Ford
2005-02-22  8:53 ` Barry K. Nathan
2005-02-22 13:12   ` Gene Heskett
2005-02-23 23:28 ` Bill Davidsen
2005-02-24 23:50 ` H. Peter Anvin

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=421A2B18.2000102@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    /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