[FFmpeg-user] How to publish rtmp to multiple destinations

[Loadlinx]

On Mon, Jun 9, 2014 at 10:53 AM, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:
> Loadlinx <limiteddi <at> gmail.com> writes:
>
>> Codec for stream 0 does not use global headers but
>> container format requires global headers
>
> This means you forgot to add -flags +global_header
> which is mentioned in the documentation of the tee
> muxer.
>
> As said, please don't use -deinterlace, it may have
> funny effects particularly with specific muxers like
> tee. Explicitely specify a deinterlacing filter instead.
>
>> Output #0, tee, to
>> '[f=flv]rtmp://192.168.0.105:1935/live/test1|
>> [f=flv]rtmp://192.168.0.106:1935/live/test2':
>>   Metadata:
>>     encoder         : Lavf55.35.101
>>     Stream #0:0: Video: h264 (libx264), yuv420p,
>> 544x480 [SAR 20:17 DAR 4:3], q=-1--1, 90k tbn, 29.97 tbc
>>     Stream #0:1(eng): Audio: aac (libfdk_aac), 44100 Hz,
>> stereo, s16, 32 kb/s
>> Stream mapping:
>>   Stream #0:0 -> #0:0 (mpeg2video -> libx264)
>>   Stream #0:1 -> #0:1 (mp2 -> libfdk_aac)
>> Press [q] to stop, [?] for help
>> root <at> rub:~/bin#
>>
>> Still doesnt look like its seeing a request for second Output?
>
> The tee muxer never prints more, I would assume it is sending
> the streams to two rtmp connections. Is it not working with
> the global_header flag added?
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Thank you for that - it worked flawlessly.
But I might have misunderstood the purpose of this andt it seems like
the publishing needs a transcode process for each output. I was under
the impression that transcoding is only done once and simply the
transcoded stream is sent to 2 different locations?
Right now the process takes ~140% of CPU as opposed to ~65%