[mythtv-users] pluggable mythtranscode

Raymond Wagner raymond at wagnerrp.com
Mon Mar 26 18:22:46 UTC 2012

On 3/26/2012 14:11, Jeremy Jones wrote:
> On Mon, Mar 26, 2012 at 12:35 PM, Brian J. Murrell 
> <brian at interlinx.bc.ca <mailto:brian at interlinx.bc.ca>> wrote:
>     Given the pace of progress in transcoding in the general sense it
>     would
>     be nice if mythtrancode supported "plugging" in user-defined
>     transcoding
>     modules.
>     That is, mythtranscode could be told that it should set up the
>     audio/video decode pipes and then call a (say) script that is
>     given the
>     pipe locations and the expected destination file file as
>     arguments.  The
>     script then does the transcoding and muxing, etc. and when done,
>     mythtranscode could then pick up the result and handle to have it
>     properly replace the original.
>     Thoughts?
> If I understand you correctly, then that can be done now using this 
> <http://www.mythtv.org/wiki/Transcode_wrapper_stub>, and replacing the 
> default transcode command with one to call your script. Unless it 
> changed with .25, this is done in myth-setup.

Not quite.  He's wanting something that actually manages data access, 
and routes audio and video streams around.  Take a look at AviSynth for 
an example.  The wrapper stub just points at the current location on 
disk of the initial recording.  It does not (although it would not be 
all that difficult) pipe the data through stdin/out to allow for 
operation against remote storage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120326/c9dffbe0/attachment.html>

More information about the mythtv-users mailing list