On Sat, 27 May 2006 09:08:08 -0500 [EMAIL PROTECTED] wrote: [...] > Performance is pretty good. I transcoded a VOB to mpeg4/mp3 with > ffmpeg and averaged 38 fps (on a G5 dual 2.0).
Uhm, this sound quite strange to me since I got _at least_ ~40 fps in similar circustances on a single-core/single-processor Athlon64 3200+. (No CPU flame intended, I like G4/G5s! :) ) > Any benefit to compiling transcode from CVS HEAD? Are there specific > branches considered relatively stable outside of the tarball release? Well, if you're a transcode enthusiast and you like to live on the bleeding edge, or if you want development, or finally if you want help debugging/testing, there is a lot of benefits using CVS HEAD since CVS is changed a lot since 1.0.2, and changes won't end here, there is still a lot to do planned or on going before 1.1.0 release, and even more after. Changelog is already pretty huge, I'll extract only a few highlights: - completely rewritten aclib (low-level asm-acclerated routine library), with new optimizations for i386/amd64. Unfortunately, there is nothing for Altivec because we (current active developers) lack of hardware, and because I lack expertise :P - heavily rewritten processing core, with new routines for audio and video internal transformations (resize, zoom, deinterlace...). Same story here for ASM accelerations. - Completely revamped module system with new API, new code, documentation and so on. Separation between encoders and multiplexors, new capabilities check code, more module in(tro)spection capabilities and so on. Still to come (enhanced filter and import layer) after the 1.1.0 - Brand new output rotation code and export profiles code. New code is (at least on intentions :P) more flexibile, usable and smells better ( ;) ). Profiles are no longer hardcoded into export modules, but are generalized, editable by the user and tunable via command line - (Planned) Brand new encoder/multiplexors, like x264 module and (as soon as is possible) vorbis encoder module and ogg/ogm multiplexor module. More to come after 1.1.0 (I'm particulary interested in mpeg and mkv I/O). - Introduction of stable, machine friendly optional output for most popular programs like transcode itself (for progress output) and tcprobe. - Really huge internal refactoring, consolidation and documentation effort with reorganization/rewriting of code, even this is mostly developer-oriented (yet). Even here more will come. And i've for shore forgot something important :P Uh, just one last word. I've introduced a simple WAV I/O support library; of course I'd like to expand and improve it, but unfortunately I'm not fast enough in designing/coding/testing and days are "only" 24hr long ;) Well, enough drama: the problem is that library isn't tested at all on big-endian systems (lack of hardware!), and I seriously suspect that's broken on those system. For interested people, there is a tarball with wavlib alone avalaible here: http://fromani.exit1.org/ (duh, this version is pretty outdated, I'll updated ASAP. If someone is interested just let me know so I'll speedup update process :P) Feedback of course very appreciated ;) Sorry for long email, I just hope this could be interesting for someone ;) Best regards, -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact: (email-me, I have antispam default deny!) icq://27-83-87-867 some known bugs: http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase
