On Fri, 02 Feb 2007 11:31:41 +0530 "Robrek V." <[EMAIL PROTECTED]> wrote:
[...] > I really hope i can come up to speed on understanding the internals, so > as to make a meaningful contribution. I will be looking forward to your > email as much as the Arsenal Match over the weekend. :) OK, let's be honest: internals of transcode aren't too good (at least they aren't good too often). A major task for 1.1.0 release is to start improving our situation by providing a better infrastructure: better code, better organization, better STYLE, better, documentation. Moreover, there are some areas in that transcode can be a very good example of how things should _not_ be done :) But ok, that's life, there is still hope and we're here to fix things and make life better -- even at slow rate ;) > Yes. I did download the tar archive to get a hang of things. I am > getting my machine into shape for things to come. Read: installing > support libraries etc. > I also downloaded the htdocs which i found quite helpful so far. Currently most of developing time is spent in export layer, by rewriting it almost from scratch. I'm writing a couple of modules in those days, most notably the libavcodec interface. There is an almost-updated list of missing modules here: http://fromani.exit1.org. new modules API is quite stable but is not fixed in stone forever (..yet), so it can still be changed if we're in need. On this topic, I'd like to propose a couple of changes on next days. For modules, main documentation is in docs/module-system-API.txt Feel free to send any comment about that. > >> As i move ahead - i would like to use transcode to write an > >> application that will successfully convert any given input into a > >> MPEG2/MPEG4 Transport Stream (is this already supported?). > > That would be really nice ;) > Fo shizzle!! > It would be interesting to initiate a discussion on the technical issues > in the processing chain involving the steps of: > file src -> container demux/splitter -> audio decode to raw /Video > decode to raw -> encode to mpeg layer2, mp3 Audio, encode to mpeg2 video > -> TS Mux with __perfect__ AVsync, utilising clock information resultant > from step 2 (container demux/splitter) > you,What say? I'll say that our import layer is very very crude and naif, so achieving perfect A/V depends heavily by source goodness. About the issues that comes into my mind, the very first are - timestamp preserving on frame sources - proper frame marking (based on above) - dealing with missing/skipped/corrupted frames on source - frame rate conversions - filter reordering (if any) or delay (if any) - proper muxing decision based on all of above And much, much more. I must say that there are a good amount of pieces that we just miss in current codebase before to face this task (and others). We plan to address those issues incrementally, and releasing 1.1.0 which will offer a MUCH saner base both for developers and users is our first goal right now. Bests, -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact : (email first, Antispam default deny!) icq://27-83-87-867 tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!) known bugs : http://tcfoundry.hostme.it/mantis (EXPERIMENTAL)
