public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Linux and Kernel Video <video4linux-list@redhat.com>,
	SPCA50x Linux Device Driver Development
	<spca50x-devs@lists.sourceforge.net>
Subject: libv4l release: 0.5.1 (The Skype release)
Date: Mon, 13 Oct 2008 13:49:45 +0200	[thread overview]
Message-ID: <48F335D9.5020104@hhs.nl> (raw)

Hi All,

After much frustration about the very poor implementation of v4l in skype, I'm 
happy to announce libv4l-0.5.1, in which after much pain, I've managed to 
implemented a fix for the skype problem in a way which does not make me feel dirty.

libv4l-0.5.1
------------
* Add support for software cropping from 352x288 -> 320x240 / 176x144 ->
   160x120, so that apps which will only work with vga resolutions like
   320x240 (Skype!) will work with cams/drivers which do not support cropping
   CIF resolutions to VGA resolutions in hardware. This makes all 2.6.27 gspca
   supported cams, except for the pac7302 which only does 640x480 (and skype
   wants 320x240), work with skype
* The v4lconvert_convert function was becoming a bit of a mess, so split the
   functionailiy into separate v4lconvert_convert_pixfmt, v4lconvert_rotate and
   v4lconvert_crop functions, and make v4lconvert_convert a frontend to
   these
* Do not link the wrapper libs against libpthread (patch from Gregor Jasny)


Get it here:
http://people.atrpms.net/~hdegoede/libv4l-0.5.1.tar.gz

Regards,

Hans



--
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-10-13 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 11:49 Hans de Goede [this message]
2008-10-21 21:39 ` libv4l release: 0.5.1 (The Skype release) Gregor Jasny
  -- strict thread matches above, loose matches on Subject: below --
2008-10-23 12:12 Hans de Goede

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=48F335D9.5020104@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=spca50x-devs@lists.sourceforge.net \
    --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