public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: "Jean-Francois Moine" <moinejf@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: SPCA1527A/SPCA1528 (micro)SD camera in webcam mode
Date: Sun, 30 May 2010 19:55:22 +0200	[thread overview]
Message-ID: <201005301955.24442.linux@rainbow-software.org> (raw)
In-Reply-To: <20100530133455.489c4f46@tele>

On Sunday 30 May 2010 13:34:55 Jean-Francois Moine wrote:
> On Sat, 29 May 2010 21:32:07 +0200
>
> Ondrej Zary <linux@rainbow-software.org> wrote:
> > The Color Space/Compression reported by the driver is only one: RGB 24
> > The driver also uses these files which may (or may not) be related to
> > used compression: iyuv_32.dll, msh263.drv, msyuv.dll, tsbyuv.dll
> > In standalone mode, the camera records video in MJPEG format.
>
> Hello Ondrej,
>
> Bad news, the images are compressed by an unknown algorithm (unknown
> from Linux point of vue). The decompression function could be found in
> some part of the ms-win driver, but:
> - first, I have no time to search and disassemble this function,
> - then, I did have this problem with an other webcam (17a1:0118), and
>   after searching for a long time, nobody could find the function, and
>   the driver is in stand-by since 2 years,
> - eventually, is this legal?

That's bad...

The driver contains file sp5x_32.dll which is registered in system.ini file as
[drivers32]
VIDC.SP54=SP5X_32.DLL

Seems that the codec is called SP54 - hope that it's used to decompress the 
data.

> All I can do is to code the driver and let you or anyone find the
> decompression function...

Maybe we can dump some data, create AVI file from that and try to decode the 
file using that codec.

-- 
Ondrej Zary

  reply	other threads:[~2010-05-30 17:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29 17:09 SPCA1527A/SPCA1528 (micro)SD camera in webcam mode Ondrej Zary
2010-05-29 18:24 ` Jean-Francois Moine
2010-05-29 19:32   ` Ondrej Zary
2010-05-30 11:34     ` Jean-Francois Moine
2010-05-30 17:55       ` Ondrej Zary [this message]
2010-05-30 18:13         ` Jean-Francois Moine
2010-05-31  2:36           ` Andy Walls
2010-05-31  3:15             ` Theodore Kilgore
2010-05-30 19:26         ` Andy Walls
2010-05-30 21:28           ` Ondrej Zary
2010-05-30 21:58             ` Andy Walls
2010-05-30 22:03               ` Ondrej Zary
2010-05-31  3:06                 ` Theodore Kilgore
2010-05-31  7:19                 ` Jean-Francois Moine
2010-05-31  7:56                   ` Ondrej Zary
2010-05-31 12:43                   ` Andy Walls
2010-05-30 18:30       ` Andy Walls

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=201005301955.24442.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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