dvd::rip

->ABOUT / NEWS

->DOCUMENTATION
-TABLE OF CONTENTS
-INSTALLATION
-USING THE GUI
-CLUSTER MODE
-FAQ

->KEY FEATURES

->DOWNLOAD

->SUPPORT

->TRANSLATIONS

->MAILING LIST
-SEARCH ARCHIVE

->CHANGE LOG

->CREDITS

->TODO

->LINKS

http://www.exit1.org/


Re: [dvd::rip] ANNOUNCE: dvd::rip stable release 0.52.7

Subject: Re: [dvd::rip] ANNOUNCE: dvd::rip stable release 0.52.7
From: Francesco Romani <fromani@xxxxxxxxx>
Date: Sun, 19 Mar 2006 10:17:23 +0100
On Sat, 18 Mar 2006 13:46:11 +0100
Jörn Reder <joern@xxxxxx> wrote:

Hi there,

[...]
> The transcode guys (in particular Francesco) are working hard on the new
> version with much effort on the internals and I hope these things will 
> get fixed along with it.

Well, since I've been evoked ( ;) ) I'll post a brief summary of situation;
I'll also post a longer summary soon on transcode-devel, since I _must_
take a break from coding for a couple of weeks starting from tomorrow.

First of all, I fully acknowledge the pthread problems in transcode.
In fact, this, as well as some other threading support issues, is one of my 
first concerns.

Unfortunately, from my point of view, fixing threading in transcode isn't a
easy nor a quick task, since doing so requires _really a lot_ of
infrastructural work to make room for improvements.
I know this is annoying since threading problems are one of most visible
issues, but since transcode's codebase _already_ loudly asks for a massive
cleanup and reorganization, I've take this way:
My road plan is to fix first as much 'peripheral code' as I can (examples:
avilib, encoder, filters, import layer, hopefully avilib, and a lot more)
without touching the core (the threading code!), then, when the codebase is
(seems?) reasonnably tested, featured and good-looking, start to dig into
thread madness.
I'm so reluctant doing this step because changing the thread part may lead
to a massive rewrite of such code and to a possibly large time period of 
high instability (threads aren't easy to code well and aren't easy _at all_
to debug)

To summarize, don't expect big fixes about threading from me for 1.1.0
and very likely neither for 1.2.0.
I simply don't know if Andrew or someone else has different plans, I think
this is a good subject for discussions on transcode-devel. :)

PS: discussions and comments (and of course patches ;) ) welcome, but
please use private email or better post to transcode-devel.

Best regards,

-- 
Francesco Romani - Ikitt ['people always complain, no matther what you do']
IM contact: (email-me, I have antispam default deny!) icq://27-83-87-867
some known bugs: http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase

 

Archive powered by MHonArc. Search powered by ht://dig.

[ top ]