On 8/13/07, Udo Wolter <[EMAIL PROTECTED]> wrote: > > That's very correct for 1.0.x branch. > > In 1.1.0 cycle we've got some significant improvements in logo filter. > Ok, at least I helped myself out with doing it in several steps and > picture after picture via ppm export. It just was a small and short > video (http://bigmedia.dicke-aersche.de/video/disk_destroy.avi) and > therefore not a real problem. Anyway, it would be fine if there's the > possibility to change the logo during the transcode run.
OK, just add a note on our issue tracker (http://tcfoundry.hostme.it/mantis) or wait, I'll add in the next days. > > xvid API isn't changed much after 1.0 released; moreover, in transcode > > slang, xvid4 == xvid1.x :) > Strange, when I try to use xvid-import it just says, there's no > libxvidcore.so.1. When I try to set a symbolic link from > libxvidcore.so.4 to libxvidcore.so.1 it says: > > xvid: init failed. Wait a minute: I'll try to clarify. XviD API was updated several times. The last update is the fourth one (so API v4, or e "xvid4" in transcode slang), and this came out with XviD 1.0.x release. After XviD 1.0.x release, the XviD API wasn't changed dramatically, so it is still version 4. Step back. libxvidcore.so.1 is an old old release of XviD that uses XviD API version 1. Unfortunately, our (transcode) XviD import module was obsolete, so it still was developed to fit with such ancient API. For this and other reasons we've just dropped the XviD import module for 1.1.0 release. That of course do NOT means that XviD import module is banned forever. Is someone ask for it or (better :) ) provides update, clean patches, it will be back in a time of a blink (well, almost) :) > I did it because the original movie from my camera came in xvid > format. The video wasn't a big problem, just the audio was. I'm not sure > which audio codec really is inside, mplayer was my help to squeeze it > out of the original stream. Therefore I did it all together with imlist > and external audio file. This shouldn't be the way to go I'd say... maybe it is u-law, don't know. What is tcprobe saying? > > Of course, this is a very much desired feature for transcode 1.1.0 and > > beyond. Patches welcome :) > I think you wouldn't like my patches, I'm a horrible developer. :) Well, what I meant is we're going to implement the features that we (as dev team) need, and the ones that are requested (if feasible). Providing patches just speed up the process :) > But I'm willing to test, I did it with transcode since the first days > it came out. That is very very appreciated as well. Consider trying 1.1.0 alphas, they are some of the best transcode releases ever since I have memory (back in old glorious 0.6.x days), and I'm NOT saying so because I'm (partly) written them :) Bests, -- Francesco Romani // Ikitt
