On 08/04/11 23:42, Axel Thimm wrote:
On Fri, 2011-04-08 at 17:39 -0400, Jeffrey J. Kosowsky wrote:
Jeffrey J. Kosowsky wrote at about 17:18:14 -0400 on Friday, April 8, 2011:
> Has anybody heard any news on this?
> It still amazes me that such a *critical* bug in the default
> transcoding program remains broken.
Just as a follow-up, I see that Jean-Yves posted on 3/31 that he believes
he fixed the bug in trunk and backported it to his own
jyavenard/backports/fixes/0.24 branch.
See: http://www.gossamer-threads.com/lists/mythtv/users/466592
HOWEVER, the bug remains in the latest atrpms version of fixes that I
have (0.24-269).
Axel, does 269 include the backported fixes yet? (or should I be
waiting for a new version of mythtv for atrpms that includes the fix
:) )
As long as it isn't in the official 0.24-fixes branch I wouldn't want to
jump the gun. When Jean feels comfortable to push it into fixes we will
automatically pick it up.
Today's post by JYA in myth-users on this topic:
For a fix to appear, it needs to be fixed first.
For a fix to be found, the problem has to be able to be reproduced by
a dev. This is done by people providing samples, arguments on how
mythtranscode is called and logs.
So far I'm yet to read anything that could be helpful in any ways.
It's always : it doesn't work. It's messed up. I'm using mythtranscode
default etc etc...
While this is the case, no fix will be worked on.
Maybe you saw it: it doesn't look as if a fix will be appearing in
ATrpms just yet :-)
John P
_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users
