Sun Jan 10 10:56:10 CET 2010
1.2.0 status report [201001]
The 1.2.0 cycle is a big leap forward for transcode, featuring an export layer rewritten from scratch (an early preview was delivered, disabled by default, on the 1.1.x releases), a real, stackable profile system, modules autodetection from format, keyed arguments, better introspection tools and the usual bunch of updates all around the places. The new features of the 1.2.0 release outlined above will likely be covered in detail by a serie of articles.
In order to foster and ease the (early) adoption of the 1.2.0, this release also features (and yes, it's already avalaible on HG) the versioned installation. Using this feature, transcode is installed with the version suffix automatically appended to all important installed objects, so you can easily get both transcode 1.1.x and 1.2.x on the same system. That was of course possible with earlier versions, but with a significant more effort.
Sun Nov 1 14:18:43 CET 2009
transcode 1.1.5
Yes, we're alive and kickin'! And transcode 1.1.5 is available for download. This is the fifth maintenance relase of the 1.1.x branch. This releases include minor feature enhancements.
Highlights of the changes since 1.1.4:
Key:
[+] feature added.
[!] bugfix of an existing feature.
[*] changement/improvement (not bugfix) of an existing feature.
[-] feature dropped.
Sun Aug 23 21:09:23 CEST 2009
transcode 1.1.4
transcode 1.1.4 is available for download. This is the fourth maintenance relase of the 1.1.x branch. This release includes the hotfixes for two recently reported serious bugs.
Highlights of the changes since 1.1.3:
Key:
[+] feature added.
[!] bugfix of an existing feature.
[*] changement/improvement (not bugfix) of an existing feature.
[-] feature dropped.
Thu Jul 30 15:22:13 CEST 2009
the 1.2.0 testing dilemma
One of the unwanted, while expected, side-effects of the introduction of the NMS is the explosion of testcases due to the bunch of new, smaller, modules written during the transition. More modules mean more interactions, and thus more testing needed. As found in current HG, we have eight muxer modules and twelve encoder modules. Not all combinations make sense, but we still have roughly fourthy combinations to test. Unfortunately, some schedule glitches and, most important, the neverending lack of developer time exhacerbated this issue, so we ended down with a bunch of new, poorly tested, modules committed to HG. The exit strategy is simple: first, to prioritize the module combinations; second, to automatize as much as possible the test job.
To prioritize the module combinations means to test first the mostly used module combinations. I extracted the first round of them, which will be debugged and tested first (but not in this order). More will come later.
Key: left, the nickname of the combo; right, the combo itself, as video encoder/audio encoder/multiplexor[/auxiliary multiplexor (if any)].
Wed Jul 29 15:38:51 CEST 2009
1.2.0 status report [200907]
Long time no post, so it's time for a new status report for the upcoming 1.2.0 release.
Quick Summary
The overall progress of the new release is fairly good. All the big changes and the invasive patches (except for bugs :^)) have been committed to the default branch. As will be outlined below, the release is mostly feature complete; however, some aspects and some important modules have still to pass an intensive review. Two more important tasks are still ongoing, tests and documentation.
Let's update the tasks outlined into the 1.2.0 roadmap
Still pending. Small task, no core changes scheduled.
The code was committed to default branch and was also backported to the 1.1.2 release.
This code is in fairly good shape, anyway further testing it is always appreciated.
Delayed for 1.3.0 or beyond.
No regressions so far; Documentation and bugfixing still in progress.
As it is found into the default branch, transcode has now only a NMS-powered export layer.
The introduction of a proper, NMS-powered, export layer triggered various others invasive changes, like a module API
refresh, the introduction of a new support library (libtcexport), the introduction of a new part of libtcmodule (the module registry),
the renewal of the tcexport support tool and so on. At this moment, we're actively testing, tuning and documenting all the new code.
The code was committed some time ago and still needs some tuning.
The code is in fairly good shape, anyway further testing it is always appreciated.
The code was committed and needs some intensive testing. Regressions are possible and expected, but they will be fixed.
The code is in fairly good shape, anyway further testing it is always appreciated.
Sun Jul 19 09:41:17 CEST 2009
transcode 1.1.3
transcode 1.1.3 is available for download. This is the third maintenance relase of the 1.1.x branch.
Highlights of the changes since 1.1.2:
Key:
[+] feature added.
[!] bugfix of an existing feature.
[*] changement/improvement (not bugfix) of an existing feature.
[-] feature dropped.
Sun Apr 5 20:35:41 CEST 2009
1.2.0 status report
(already posted on the transcode-devel mailing list)
The main feature of the next 1.2.0 release will be the
introduction of a full-NMS export layer, providing all the long-needed
goodies like support for modern codecs/formats.
Back in january, that was the 1.2.0 roadmap
As is found on today's HG, the following is the current status:
To be done. It's a small task, anyway.
DONE!
Already fairly stable. Needs more testing, though.
Delayed for 1.3.0 or beyond.
DONE!
No regressions so far; needs more documentation, even
though the avalible one is pretty decent.
Some minor bugs can still spawn whatsoever.
I actively searched for design flaws into current architecture,
(of course) found some of them, addressed then solved. All that
is nice, but that required (and requires) some time.
The whole thing it's coming along pretty nice, however.
All the preview modules so far published will still work of course,
and new ones are coming (libavformat muxer support, mkv direct
support very likely).
The merger with public repo is not too distant into the future, but
some weeks more for development are still needed.
DONE!
Still needs testing and tuning. No regressions spotted so far, but
wider testing can eventually let them pop out.
Testing just beginned, expect problems e.g. from the affected filters
(especially).
Short term plans:
Focus on NMS and merge the code as soon as possible. After that, most
of the development is done, the remaining bits are self contained
(mostly modules).
A first 1.2.0 alpha version will be (hopefully) released this summer.
Sat Mar 28 10:32:46 CET 2009
transcode 1.1.2
transcode 1.1.2 is avalaible for download. This is the second maintenance relase of the 1.1.x branch. Beside the usual round of fixes, this is the first releases which can be built without ffmpeg.
Highlights of the changes since 1.1.1:
Key:
[+] feature added.
[!] bugfix of an existing feature.
[*] changement/improvement (not bugfix) of an existing feature.
[-] feature dropped.
Sat Mar 21 10:56:25 CET 2009
News from HG: switching to GraphicsMagick.
A large series of patches is being committed into HG default branch. This patchset implements the support of the GraphicsMagick libraries (from 1.1 to onwards), while on the same time ImageMagick is being phased out. The 1.2.0 release is scheduled to be the first one requiring GraphicsMagick; however, it is possible that the patchset will be backported, once stabilized, into 1.1.x series.
The rationale for this switch is outlined by some highlights of the GraphicsMagick homepage:
Sat Mar 21 10:46:05 CET 2009
Build transcode without FFmpeg.
The ffmpeg libraries are an historical pillar of transcode, providing much used and appreciated export and import modules. However, transcode claim its independency from FFmpeg. So, starting from the approaching 1.1.2 release, it will be possible to build transcode without FFmpeg support. Of course, given the quality and quantity of the features that FFmpeg provides, this is highly discouraged and disabled by default.
Sun Feb 22 09:53:22 CET 2009
transcode 1.1.1
transcode 1.1.1 is avalaible for download. This is the first maintenance relase of the 1.1.x branch.
Highlights of the changes since 1.1.0:
Key:
[+] feature added.
[!] bugfix of an existing feature.
[*] changement/improvement (not bugfix) of an existing feature.
[-] feature dropped.
Wed Jan 28 22:46:32 CET 2009
Switch to mercurial
Starting from this week the codebase moved on Mercurial (HG). The usage of a distributed VCS helps quite a lot the development process. The source code can be accessed here: http://hg.berlios.de/repos/tcforge
The full history of the project was imported from the previous repository, hosted on cvs.exit1.org. The SVN repository is still active for historical purposes; it will also serve as auxiliary space for side projects (e.g. tcrund).
Sun Jan 18 11:40:35 CET 2009
transcode 1.1.0 Final Release
transcode 1.1.0 final is avalaible for download. This is the final relase of transcode 1.1.0, released after two years and counting of development.
We are happy to announce the first release of new transcode development cycle.
A strong effort was made to laid down robust foundations fort further great ehnachments,
opening the road for long-waited and exciting features.
EVERYONE is using early 1.1.0 prereleases or HEAD snapshots it is
encouraged to try this release. 1.0.x users are also encouraged to switch, or to give a try at very least.
Highlights of the changes since 1.1.0 RC 5:
Mon Jan 5 15:23:37 CET 2009
transcode 1.1.0 Release Candidate 5
transcode 1.1.0 rc 5 is avalaible for download.
This release candidate was due to a bug found on --psu_mode.
Except for further critical bug, this is the last RC before 1.1.0 final.
EVERYONE is using early 1.1.0 prereleases or HEAD snapshots it is
encouraged to try this release.
PLEASE help also report any bug or regression found using the bugtracker
(link above) or the transcode-devel mailing list (the first way is the preferred way).
Highlights of the changes since 1.1.0 RC 4:
Tue Dec 30 10:07:31 CET 2008
1.1.0 final release delayed
A recently-reported bug in PSU mode (http://article.gmane.org/gmane.comp.video.transcode.devel/4763) eventually showed up a serious design flaw into current framebuffer code (affects all modern branches: 1.1.0, CVS HEAD, SVN). Unfortunately, this issue can't be quickly fixed, so some serious changes are needed, as well as a new RC which is expected in the early days of 2009. The 1.1.0 RC final is due a couple of weeks after. The new (candidate) release date for 1.1.0 final is then 2009/01/18.
Thu Dec 25 10:47:29 CET 2008
Status Report
Long time no post. But hey, it's Christmas, and as little present I'd like to give a little status report about what's going on here on transcode forge.
For any question, request or further discussion. Drop us a mail on transcode-devel-at-exit1-dot-org. Happy Holydays!
Sat Dec 13 18:05:53 CET 2008
transcode 1.1.0 Release Candidate 4
transcode 1.1.0 rc 4 is avalaible for download.
This is the last scheduled release candidate of transcode 1.1.0.
EVERYONE is using early 1.1.0 prereleases or HEAD snapshots it is
encouraged to try this release.
PLEASE help also report any bug or regression found using the bugtracker
(link above) or the transcode-devel mailing list (the first way is the preferred way).
Highlights of the changes since 1.1.0 RC 3:
Sun Nov 16 11:35:30 CET 2008
transcode 1.0.7
transcode 1.0.7 is avalaible for download.
This is the final release of transcode 1.0.7.
This release is expected to compile (and work, of course ;) ) cleanly
on: x86, x86_64.
Highlights of the changes since 1.0.6:
