Reply to thread

Message

<blockquote data-quote="Valk" data-source="post: 506523" data-attributes="member: 18631">{0} and {1} are the input and output file locations used by the encoder so I can pass the active media stream to the encoder and pull the transcoded output back into StreamTv to send to the client.Currently only named pipes are implemented as an input / output method (though I do plan to do a few others).{0} is the input for the encoder (data been passed to the encoder).{1} is the output of the encoder (data been passed back to streamTv)named pipes are formatted something like: \\.\pipe\pipenameThe pipename part is generated at runtime so that it will never overlap with another active pipe.If it works with ffmpeg all you should need to know is that for the input file you use {0} and the output file you use {1}.If it doesn't work you will have to wait until I do another input method like UDP or something else.Hope that clears it up.</blockquote>

[QUOTE="Valk, post: 506523, member: 18631"] {0} and {1} are the input and output file locations used by the encoder so I can pass the active media stream to the encoder and pull the transcoded output back into StreamTv to send to the client. Currently only named pipes are implemented as an input / output method (though I do plan to do a few others). {0} is the input for the encoder (data been passed to the encoder). {1} is the output of the encoder (data been passed back to streamTv) named pipes are formatted something like: \\.\pipe\pipename The pipename part is generated at runtime so that it will never overlap with another active pipe. If it works with ffmpeg all you should need to know is that for the input file you use {0} and the output file you use {1}. If it doesn't work you will have to wait until I do another input method like UDP or something else. Hope that clears it up. [/QUOTE]

Verification