From: Damien Bobillot <damien.bobillot@m4x.org>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Video/Audio codecs in ocaml
Date: Thu, 17 Nov 2005 10:17:57 +0100 [thread overview]
Message-ID: <640063C5-4B83-4635-9E9B-755E0F80D5A3@m4x.org> (raw)
In-Reply-To: <ad8cfe7e0511162116m75d9d812ib6aca11d2e1d8ca1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Jonathan Roewen wrote :
>> Has anyone done anything with video and/or audio processing
>> using ocaml?
>
> Even better: would anyone like to help with an mpeg2 decoder written
> completely in ocaml?
>
> OCaml is supposed to be good at numerical processing right? So I hope
> performance for a 100% software based decoder will be okay...
With OCaml you can't use features like SIMD instructions of CPUs, and
will do many bound checking, so it will be slower.
I'm a bit sceptical that ocaml may be as good as C for pure signal
processing.
> My goal is to get something going within one week =P I have no idea if
> it can be done, so we'll see...
Writing a mpeg2 decoder won't take less than a week !!! (except
perhaps if you've already spent time on a mpeg2 decoder)
If you have to write something, a ocaml wrapper for ffmpeg may be a
good start.
--
Damien alias Schmurtz
aim:goim?screenname=schmuuurtz
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2375 bytes --]
next prev parent reply other threads:[~2005-11-17 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 4:41 Jonathan Roewen
2005-11-17 5:16 ` Jonathan Roewen
2005-11-17 9:17 ` Damien Bobillot [this message]
2005-11-17 9:25 ` Jonathan Roewen
2005-11-17 9:51 ` Damien Bobillot
2005-11-17 18:46 ` David MENTRE
2005-11-17 18:48 ` Jonathan Roewen
2005-11-17 14:39 ` Brian Hurt
2005-11-17 14:56 ` skaller
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=640063C5-4B83-4635-9E9B-755E0F80D5A3@m4x.org \
--to=damien.bobillot@m4x.org \
--cc=caml-list@yquem.inria.fr \
--cc=jonathan.roewen@gmail.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