Hi Francesco and Andrew, Appreciate the status update, and the background story -- it's a lot of fun to see where you guys are taking the project.
A/V sync is a big deal of course, and encoder profiles sounds like a sane way of handling options. What about documentation? I still don't understand the X11 module. Is it essentially a remote video screen capture? What does aclib accelerate? Dave Francesco Romani wrote: > > On 2/5/07, *David Liontooth* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > [...] > > Could either of you give us a "state of the project" report -- where > we're headed and how far we've come? > > > Andrew has already outlined the main topics. > > I've spent most of time on new encoder layer (that unfortunately will > not come into > 1.1.0 for reasons already exposed by Andrew), reorganizing/refactoring > the code > into support libraries and also dealing with framebuffer code. > > Let me summarize the work done and the future directions for new encoder > layer (people that already followed discussions on -devel can safely > jump to next > --MARK-- since there is nothing new in here :) ) > > Aside for the task of rewriting modules in a better and more modular > fashion, as > Andrew already outlined, my focus was on sanitizing encoder profiles > support. > For `encoder profile' I mean a set of predefined settings tuned for a > particular > situation, like transcoding to cellphone/portable console, TV > transcoding, making a DVD-compliant > MPEG2 stream, and whenever you like. > > The idea is to ship a set of profile data files, as well to allow user > to easily write new ones. > Then, just do something like > > transcode -i input -o output --export_prof myprofile.cfg [other options] > > and let the magic happens. No more kilometer-long command lines, > unless of course > user *explictely want* to do that. Don't be fooled: that's no > userfriendliness nor > usability, that's just lazyness since I'm tired of writing long > command lines or scripts > to embed them ;) > > In the long shot, this will also allow to do just > > transcode -i input -o output --export_prof myprofile.cfg > > and let the autoprobe and the profile infrastructure do all the dirty > work. > > Until transcode 1.0.x, profile configuration is just embedded in > export modules, so changing or adding data is not > trivial (to be optimist...) > > --MARK-- > > That's the most visible change, but I've also spent some time in > making encoder code better. There is still a lot of work, anyway, but > most important modules are going in place. I'd like to add fancy stuff > like a mp4 muxer and a full-featured > Xiph stack (vorbis/theora encoder + ogg muxer), as well as mkv > muxer/demuxer and more. Expect this stuff in 1.2.x > and following, or just fetch CVS HEAD and start hacking. > > Almost all other stuff that I've done isn't user-visible except for > new improved integration with mplayer for importing > and new X11 import module, replacing old VNC import module. This last > new piece is still experimental, but it will > be in 1.1.0 and it will have a decent functionality. > > That's less or more all, expunged from gory development details :) > > bests, > > PS: anyone feel free to ask more about some specific topics > > -- > > Francesco Romani
