On Tue, 26 Sep 2006 13:09:35 +0200 (CEST) <[EMAIL PROTECTED]> wrote: > Hm, I guess it's a bit disappointing to see how little users make use of > HEAD.
It's understandable, I fully agree on usefullness and need for formal releases, and I fully agree that building transcode from source is annoying due to high dependency count. (From here I'm talking in general, that isn't a direct specifi answer to you ;) ) But we've changed (and hopefully improved) a lot since 1.0.x, making foundation for further BIG improvements. So testing (and, of course, patches ;) ) are definitively appreciated. Some numbers about last year (!!) work on 1.1.0 since September 2005: * +151k approx. Changelog size increment * +3892 approx. Changelog lines added * +373 approx. Changelog Entries (a fair amount of those refers to multiple files) from maintainer team (Andrew + me) There is a lot new under the hood ;) Let me remark that even if CVS HEAD IS NOT ready and stable, both me and Andrew we use it in our everyday usage, so it isn't so bad after all ;) Everyone please note that I'm not trying to push users to CVS HEAD. Let me say again: ISN'T yet read. IT HAS known issues. It's CVS after all :) I'm just trying to encourage people that can do so to follow more closely development: (constructive :P) feedback and partecipation in development it's always useful :) And most important: DON'T think transcode is dead or dying or starving. Not yet ;) > Since I'd like transcode to make progress (but can't contribute with > code :( ) I decided to make a fresh CVS HEAD checkout (which I just > installed). Actually, that solved a compiling issue I had with ffmpeg from > svn :) Hopefully we'll be able to put 1.1.0 in alpha ASAP so we can eventually get rid of ancient 1.0.x codebase. > Heh, "braveness" remindsme of the days when I tried to get started with > transcode. Digging the man page and a lot of trial and error was necessary > to make it work. Admittedly I switched over to mencoder from time to time > though (or used the mplayer import plugin (one of the most useful in my > opinion!)). On this topic, I've heard some complaints about transcode documentation. OK, I'm involved in development, but except for some known problems not command line switches nor manpages seems worse than mencoder counterparts... Anyway, anyone not satisfied of transcode documentation is encouraged to post on transcode-users or/and on transcode-devel his/her complaints, requests *and suggestions* :) best regards, -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact : (email first, Antispam default deny!) icq://27-83-87-867 known bugs : http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!)
