<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 3/26/2012 14:11, Jeremy Jones wrote:
<blockquote
cite="mid:CADCRbW32tYqN4G1tT9CiutYe2a7BSg6Yq7XrRfEyRPzogx0MMQ@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Mar 26, 2012 at 12:35 PM, Brian
J. Murrell <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Given the pace of progress in transcoding in the general sense
it would<br>
be nice if mythtrancode supported "plugging" in user-defined
transcoding<br>
modules.<br>
<br>
That is, mythtranscode could be told that it should set up the<br>
audio/video decode pipes and then call a (say) script that is
given the<br>
pipe locations and the expected destination file file as
arguments. The<br>
script then does the transcoding and muxing, etc. and when
done,<br>
mythtranscode could then pick up the result and handle to have
it<br>
properly replace the original.<br>
<br>
Thoughts?<br>
<span><font color="#888888"><br>
</font></span></blockquote>
<div>If I understand you correctly, then that can be done now
using <a moz-do-not-send="true"
href="http://www.mythtv.org/wiki/Transcode_wrapper_stub"
target="_blank">this</a>, and replacing the default
transcode command with one to call your script. Unless it
changed with .25, this is done in myth-setup.</div>
</div>
</blockquote>
<br>
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.<br>
</body>
</html>