Hi all, and happy new year :) Eventually I got time and chance to get back on work. 1.1.0 is back on track, 1.0.3 is pretty near to be released.
I'd like to know if there is someone, user or packager, that does NOT enable the statbuffer handling in transcode. statbuffer was enabled by default from pretty long time, so it must be disabled explicitely; in this case, I'd like to know why :) In other words, there is someone out there that uses --enable-statbuffer=no (or --disable-statbuffer) Or just sees [...] Summary for transcode $VERSION: ---------------------------------------- core options ---------------------------------------- static AV-frame buffering no [...] On his configure's option? +++ Let me point out that this is NOT stuff that would change in 1.1.0, there is already too much stuff undergo. That's post-1.1.0 preliminary study (hey, I know surveys take long time to gather enough responses to be useful ;) ) +++ Best regards and happy 2007 again. -- 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!)
