search for: fdct

Hi. I am trying to find calls of idct/fdct.c functions by tracing png2theora.c calls. But found only: analyze.c:oc_dct_cost2() Where and when idct/fdct/mmxidct/mmxfdct.c functions are used? Mentions of "dct" word: ==== pacify at optima-amd64:/usr/src/libtheora-1.2.0alpha1/lib$ grep dct *.c | cut -f1 -d":" | uniq -c ???...

...64 for luma plane, and 28 28 28 36 32 36 52 40 40 52 60 56 52 56 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 for chroma plane? 3) Third question. How do you restore the original matrix after fdct and quantize ... Used dequantize + idct?

Hi, Is there anything special I need to know about VP3's IDCT? I mean besides the fact that there are separate IDCTs to handle sparse coefficient matrices. Are the IDCT functions mathematically equivalent to any textbook IDCT functions? Thanks... -- -Mike Melanson --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

...use the -mllvm -debug option for clang but without much success. Do I need to build in any specific manner for this to work ? On using -mllvm -debug as follows I get the error below. $>clang -ccc-host-triple armv7-none-linux-gnueabi -mfloat-abi=softfp -mfpu=neon -mcpu=cortex-a9 -mllvm -debug fdct.i -S clang (LLVM option parsing): Unknown command line argument '-debug'. Try: 'clang (LLVM option parsing) -help' clang (LLVM option parsing): Did you mean '-lanum'? Other options with -mllvm (e.g. print-after-all) work fine. Thanks in advance. Pranav

...this in a proper RDO framework eliminates vast swaths of heuristics and fragile thresholds from the 1.0 encoder. 2. Better motion search ? The new motion search generates better results in less time, and does not suffer from CPU spikes under heavy motion like the 1.0 encoder's did. 3. Better fDCT ? The 1.0 encoder's forward transform was not well-matched to the inverse DCT used in the decoder, and was as a result responsible for substantial loss of detail and texture at high rates. It has been replaced with a forward DCT that gives much smaller round-trip error. The inverse DCT in the d...

...this in a proper RDO framework eliminates vast swaths of heuristics and fragile thresholds from the 1.0 encoder. 2. Better motion search ? The new motion search generates better results in less time, and does not suffer from CPU spikes under heavy motion like the 1.0 encoder's did. 3. Better fDCT ? The 1.0 encoder's forward transform was not well-matched to the inverse DCT used in the decoder, and was as a result responsible for substantial loss of detail and texture at high rates. It has been replaced with a forward DCT that gives much smaller round-trip error. The inverse DCT in the d...

...@@ -41,6 +41,9 @@ internal.c \ quant.c \ state.c \ +i386/state_mmx.c \ +i386/frag_mmx.c \ +i386/cpu.c \ LIBTHEORABASE_CHEADERS = \ dct.h \ @@ -75,8 +78,7 @@ psych.c \ LIBTHEORAENC_CHEADERS = \ -${LIBTHEORABASE_CHEADERS} \ -encint.h \ +${LIBTHEORABASE_CHEADERS} \encint.h \ enquant.h \ fdct.h \ huffenc.h \ @@ -156,7 +158,7 @@ ${PLAYER_EXAMPLE_TARGET}: ${PLAYER_EXAMPLE_OBJS} ${LIBTHEORABASE_TARGET} \ ${LIBTHEORADEC_TARGET} mkdir -p ${TARGETBINDIR} - ${CC} ${CFLAGS} -o $@ ${PLAYER_EXAMPLE_OBJS} ${LIBS} \ + ${CC} ${CFLAGS} -o $@ ${PLAYER_EXAMPLE_OBJS} ${LI...

...@@ -41,6 +41,9 @@ internal.c \ quant.c \ state.c \ +i386/state_mmx.c \ +i386/frag_mmx.c \ +i386/cpu.c \ LIBTHEORABASE_CHEADERS = \ dct.h \ @@ -75,8 +78,7 @@ psych.c \ LIBTHEORAENC_CHEADERS = \ -${LIBTHEORABASE_CHEADERS} \ -encint.h \ +${LIBTHEORABASE_CHEADERS} \encint.h \ enquant.h \ fdct.h \ huffenc.h \ @@ -156,7 +158,7 @@ ${PLAYER_EXAMPLE_TARGET}: ${PLAYER_EXAMPLE_OBJS} ${LIBTHEORABASE_TARGET} \ ${LIBTHEORADEC_TARGET} mkdir -p ${TARGETBINDIR} - ${CC} ${CFLAGS} -o $@ ${PLAYER_EXAMPLE_OBJS} ${LIBS} \ + ${CC} ${CFLAGS} -o $@ ${PLAYER_EXAMPLE_OBJS} ${LI...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date. In addition, the FreeBSD 6.0 End of Life is presently scheduled