<br><br><div class="gmail_quote">On Mon, Dec 17, 2012 at 9:51 PM, Ian Evans <span dir="ltr"><<a href="mailto:dheianevans@gmail.com" target="_blank">dheianevans@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just wondering what's happening with Myth's internal lossless<br>
transcode. I used it all the time to save space cutting the<br>
commercials out while not compressing the program itself.<br>
<br>
When I moved to .26 the mythtranscode stopped working as per<br>
<a href="http://code.mythtv.org/trac/ticket/11090" target="_blank">http://code.mythtv.org/trac/ticket/11090</a><br>
<br>
I've been using the new Lossless Cut program but with my HDHomerun<br>
recordings I've noticed issues with the cuts being slightly off or the<br>
audio sync drifting to a noticeable error. For me the lossless cut<br>
mode of mythtranscode worked and worked like gold.<br>
<br>
I'm not able to code in the language used for Myth so I don't know<br>
what's changed, but how did mythtranscode going from 100% solid to a<br>
100% failure for many of us? That's not meant to be a knock, but I'm<br>
just curious what changed between .25 and .26 and why there isn't much<br>
noise about it. I know many argue against compression transcoding here<br>
not worth the CPU/power cost, but I thought the view was different for<br>
lossless transcoding.<br></blockquote><div><br></div><div>It's most likely in the ffmpeg merge. If you happen to be able to test on master compiled from source, I believe another ffmpeg merge was done very recently which could give you something to test against to see if the problem still exists in the latest code.</div>
<div><br></div><div>Kevin</div></div>