http://www.mauriciomenon.com.br Aula 1 - Introducao a Informatica:http://www.mediafire.com/?blbbkg6md1io81p Novo site do professor para disponibilizacao do conteudo: https://sites.google.com/site/mauriciomenon/Este blogspot deixara de ser atualizado.https://sites.google.com/site/mauriciomenon/ Sentiu falta da ferramenta de analise de dados (Data analysis tool pack) no Office 2011?Entao, nao e sua culpa nao saber onde esta, nao tem mesmo. Use este, tem uma versao gratuita para ajudar, e possui as principais ferramentas de estatistica embutido. http://www.analystsoft.com/en/products/statplusmacle/screenshots.phtml ref: http://www.ecu.edu/cs-itcs/mac/Excel-2011-Data-Analysis-ToolPak.cfm O macports comecou reclamar do openssl, nao compila e tal?Nao seja orelha seca e verifique a versao da zlib, se e propria para o sistema. O SL e somente 64 bits.Fix: https://trac.macports.org/ticket/20954sudo port clean openssl zlibsudo port uninstall zlibsudo port -d install opensslAndsudo port upgrade --force installed Introducao a Informatica.Criterios de avaliacao, ementa e contato do professor.http://www.mediafire.com/?kgtm736gv1vysv4 Texto completo em: http://x264dev.multimedia.cx/archives/377Overall verdict on the VP8 video formatOverall, VP8 appears to be significantly weaker than H.264 compression-wise. The primary weaknesses mentioned above are the lack of proper adaptive quantization, lack of B-frames, lack of an 88 transform, and non-adaptive loop filter. With this in mind, I expect VP8 to be more comparable to VC-1 or H.264 Baseline Profile than with H.264. Of course, this is still significantly better than Theora, and in my tests it beats Dirac quite handily as well.Supposedly Google is open to improving the bitstream format but this seems to conflict with the fact that they got so many different companies to announce VP8 support. The more software that supports a file format, the harder it is to change said format, so Im dubious of any claim that we will be able to spend the next 6-12 months revising VP8. In short, it seems to have been released too early: it would have been better off to have an initial period during which revisions could be submitted and then a big announcement later when its completed.Update: it seems that Google is not open to changing the spec: it is apparently final, complete with all its flaws.In terms of decoding speed Im not quite sure; the current implementation appears to be about 16% slower than ffmpegs H.264 decoder (and thus probably about 25-35% slower than state-of-the-art decoders like CoreAVC). Of course, this doesnt necessarily say too much about what a fully optimized implementation will reach, but the current one seems to be reasonably well-optimized and has SIMD assembly code for almost all major DSP functions, so I doubt it will get that much faster.I would expect, with equally optimized implementations, VP8 and H.264 to be relatively comparable in terms of decoding speed. This, of course, is not really a plus for VP8: H.264 has a great deal of hardware support, while VP8 largely has to rely on software decoders, so being just as fast is in many ways not good enough. By comparison, Theora decodes almost 35% faster than H.264 using ffmpegs decoder.Finally, the problem of patents appears to be rearing its ugly head again. VP8 is simply way too similar to H.264: a pithy, if slightly inaccurate, description of VP8 would be H.264 Baseline Profile with a better entropy coder. Even VC-1 differed more