[mythtv-users] possible bug in 0.28 mythtranscode

Mark Perkins perkins1724 at hotmail.com
Sat Aug 6 13:44:50 UTC 2016


On 6 August 2016 9:20:48 PM ACST, Jim Abernathy <jfabernathy at outlook.com> wrote:
>
>> >> Ok just checked and mythtranscode is NOT deleting the original
>file in
>> > fixes/0.27 using fifo mode.
>> >>
>> >> Sorry for the bad info.
>> >> _
>> >
>
>So is there any further testing needed on my part to help fix this
>issue?  My reasoning is that if you see why it worked correctly in 0.27
>on fresh install, but not is later patches including 0.28, then I'll
>just move on to 0.28 for it's other advantages and wait to test
>mythtranscode with -o option until a fix is released?
>
>Does that make sense?
>
>Jim A
>
>

My 2 cents - i think there is little to be gained doing further testing on fixes/0.27. Even if a bug is found in 0.27 a fix may not get backported anyway, if there is actually a bug.

In 0.28 there is a tickbox in mythtv-setup / 1. General / Job Queue (global) about page 9 or so "save original files after transcoding". Does mythtranscode honor this switch if mythtranscode is called from an external script? If my test 0.28 backend is correct the tickbox defaults to unticked, ie original files are not saved. So this might be the issue / fix.


More information about the mythtv-users mailing list