Slashdot Mirror

← Back to Stories (view on slashdot.org)

Nancy Goes Head-to-Head With MPEG-4

Posted by Hemos on from the battle-head-to-head dept.

Justin Rossi writes: "EE Times has an article about Nancy, 'the lightest video codec' which is taking Asia by storm and finally bringing streaming Video to handheld devices. What I wonder is how it shall fare against MPEG-4, Ogg Tarkin, and MC-10."

3 of 176 comments (clear)

  1. Hmmmm by Corporate+Troll · · Score: 3, Informative
    I still don't get this hype about "video-on-cell-phone". Now correct me if I'm wrong but standalone "videophones" were "to be the future", they never catched on. Why would it be different for cell-phones even if you have the bandwith?

    I just can say: cool a new codec, which will perhaps allow me to watch some extra pr0n on this slow computer....but then I'm running Linux and this thing is proprietary, so implementation probability is about 10%. However the chinese got their hands in it, so not all is lost.

  2. Not MPEG4 killer... by dserpell · · Score: 5, Informative
    Reading the article:
    MPEG-4 uses discrete-cosine-transform and motion-estimation technologies. By contrast, Nancy uses only the four fundamental processes of arithmetic (addition, subtraction, multiplication and division), along with comparison and bit-shift operation. This keeps its operation light, said Koichi Kato, chief technology officer at Office Noa.
    This is nosense... DCT is also only addition and multiplications (no divisions, so it have to be faster...) Also:
    The codec will run "even if CPU power is not high," said Kato. "A 50-Mips CPU can compress and decompress video at 30 frames per second with QCIF [176 x 144-pixel] resolution [using Nancy]. There is no other video codec in a software form that can encode and decode." The program for real-time video compression and decompression takes 30 to 40 kbytes of memory, "and consumes about one-tenth of the power compared with MPEG-4 operation," he added
    He shoud take a look at ffmpeg's libavcodec. In 240kbytes you have coder and decoder for: Video MPEG1/2/4, MSMPEG4, MJPEG, H263, RealVideo, AC3, Audio MPEG-Layer3... And with assembler routines for x86 and arm cpu's. Getting 30fps of QCIF at 50mips isn't as difficult...
  3. Hrumf by xiphmont · · Score: 3, Informative

    >I've been waiting for the 1.0 release of Ogg >Vorbis for a few years now

    Really? Development only began in 1998, and nothing was even announced to the world until 2000 (right here in slashdot, a few months before we'd have liked word to leak out). No one has even known about it 'for a few years'. :-)

    >Yes, it's a nice CODEC, but the development >timeline has been less than ideal for commercial >adoption.

    MPEG required ~10 years. Our code has been production grade since beta1, and every bitstream make since May 8th, 2000 will work forever. That's less than two years from beginning to frozen. The '1.0' label is just waiting on a paper list of features that has grown over time.

    Hrumf. We should have just called 'rc1' 1.0 and no one would have known the difference.

    > Ogg Tarkin is still in
    > extremely early development,

    very true.

    > without even alpha code to show for the effort.

    Running Tarkin code exists; we actually have three competing implementations, two in CVS, and the 'w3d' module at cvs.xiph.org is the current frontrunner (and the one we're actively developing).

    But this is not release grade code.

    Monty