Hi all I'd like the announce the avalability of transcode 1.0.4 RC 0, the first Release Candidate that will lead (hopefully) soon to transcode 1.0.4. ImageMagick 6.3.x HDR fix is the main missing piece to complete the 1.0.4 cycle, but it is expected (relatively) soon[1].
Beside the usual fixes, 1.0.4 release highlights are - Fix interaction of export audio modules with newer libavcodecs (done) - Drop gtk+ support (done) - Fix interaction with ImageMagick 6.3.x with HDR enabled (TODO) Please note the `drop gtk+ support' item. transcode remains one of few apps still depending from old, unsupported gtk+ 1.x. transcode uses gtk+ to display preview frames in `preview' plugin. But usage of gtk+ path is deprecated AND it has alternatives both using preview filter itself, AND switching to `pv' filter. So, looks like dropping gtk+ code both make some sense and should hurt anyone. To gain a little more confidence: is there outside someone that specifically needs *gtk+* preview code (let me remark again that preview support itself is NOT been removed and it will NEVER be)? If noone complaints, gtk+ support is officially dead in transcode itself (both 1.0.x and 1.1.x and further). +++ While here let me say a few words about 1.1.x status. Q: Why 1.0.x progresses and 1.1.x seems to starve? A: 1.1.x is harder to develop. We have *much* higher quality standards, *and* we doing harder things, like redesign/rewrite core components. 1.0.x has much lower entry barrier for patches and changes. I know 1.0.x has messy codebase. I can live with that. I know we must improve this situation: we're doing so, in 1.1.x :) Q: What are the showstoppers left to 1.1.x? A: The same old one: only new decoder code, that must handle multiple inputs gracefully. Q: New decoder code doesn't look so hard. A: It isn't, but code is still messy AND has a lot of dependencies, corner cases, and doing the wrong thing can broke a lot of stuff in subtle ways. I've eventually gave up and I'll start to add new code using a separate code path. I know that's uglier, but it's the only way to improve things lowering (not avoiding, unfortunately) the risks. We already have enough core changes to deal with. +++ [1] Even if I've seen somethings in ImageMagick API that seems to be *really* scaring. I guess I've seen wrong :P +++ Of course, I'm avalaible for any question and/or thought :) Bests, -- Francesco Romani // Ikitt
