[mythtv-users] Alternatives to lossless transcode
jlistspam
jlistspam at gmail.com
Sat Nov 2 15:32:40 UTC 2013
On 11/2/2013 7:59 AM, Anthony Giggins wrote:
>
>
>
> On 2 November 2013 02:01, John Finlay <finlay at moeraki.com
> <mailto:finlay at moeraki.com>> wrote:
>
> On 9/29/2013 5:21 PM, Michael T. Dean wrote:
>
> On 09/29/2013 04:33 PM, John Finlay wrote:
>
> I'm beginning to think that mythtranscode has been
> intentionally changed to still work with mythtv but to
> make post-processing of the losslessly transcoded file
> impossible. Even mythffmpeg can't process the cut files.
>
>
> No, we had no intention of adding DRM/"lock in" to MythTV.
> Just a bug that someone needs to figure out. If someone can
> figure out what MythTV is breaking (and, ideally, how to fix
> MythTV to not break it), we'll put that patch in...
>
> For anyone who has had a problem with 0.26 and 0.27 lossles mpeg2
> mythtranscode I think I figured out the problem and added a patch
> to http://code.mythtv.org/trac/ticket/11213 that should fix the
> problem.
>
> John
>
>
> Thanks John,
>
> When this gets merged can someone please advise which version it's in?
>
> Cheers,
>
> Anthony
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
My Bad. I misread the bug report and the fix. I looked at the patch
and see that the fix is the saving of the pts and replacing it, not
changing back the function call.
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20131102/160f0d3a/attachment.html>
More information about the mythtv-users
mailing list