[mythtv-users] Remote Transcoding

[Raymond Wagner]

On 11/17/2011 10:54, P. Laflamme wrote:
>> Since you couldn't write to the file you were reading from, you need a
>> call to tell the remote backend to rename that file once you're done.
>> Alternatively, you could just alter the basename in the database and
>> delete the old file.
> I'd be happy to try to produce a patch that will update the filename
> in the database after transcoding. Would it be accepted if it's done
> this way?

Adding a command to mythprotocol to allow remote moving of files is 
fairly trivial, compared to the glue needed to allow mythtranscode to 
operate on remote files rather than local ones.  In any case, the only 
transcoding you should be using mythtranscode for is lossless 
MPEG2->MPEG2, just to clip out commercials.  Anything else will produce 
MPEG4ASP in a NuppelVideo container, for a modest gain in compression 
efficiency over the original MPEG2, and next to zero playback support 
outside of MythTV.

If you're doing lossless transcoding, you're really not using much in 
the way of CPU.  It's little more than a file transfer, skipping over 
the cut points, and doing a bit of recompression on any hanging P/B 
frames.  Even a wimpy ZBOX will have no trouble managing that.  If 
you're not doing lossless transcoding, you would be better off with some 
external utility, in which case any effort towards allowing 
mythtranscode to operate remotely is moot.