[mythtv-users] mythtranscode just deleted my file
Paul Gardiner
lists at glidos.net
Sun Nov 20 22:37:15 UTC 2016
On 20/11/2016 20:31, George Bingham wrote:
> On Sun, Nov 20, 2016 at 8:38 AM, Stuart Auchterlonie
> <stuarta at squashedfrog.net <mailto:stuarta at squashedfrog.net>> wrote:
>
> On 20/11/16 14:35, Paul Gardiner wrote:
>
> For some years now, I've been using mythtranscode in --fifodir mode,
> often running it several times on the same recording to transcode
> different parts. All has worked well, until I updated to v 0.28:
> now it seems mythtranscode deletes the original file even in
> --fifodir
> mode. Madness! Any way I can stop it doing that?
>
>
> Known issue, a patch is being worked on.
>
> If you manually link the original recording and give the link a ".tmp"
> extension, then the mythtranscode command will not delete the original
> recording and restore it from the .tmp link - provided that you have it
> set in the mythbackend settings to preserve the original recording.
Is that a link in the linux sense? Does it matter soft or hard? I
might add that to my script as a work around for now. Do you know
what the logic is behind that behaviour - why it needs both the
.tmp file and the setting?
Cheers,
Paul.
More information about the mythtv-users
mailing list