Hello All,
I have run into an issue while using a Tesla K80 with NVENC to transcode an incoming RTSP H.264 stream, then push said stream back out as an mpeg-ts stream for multi-cast playback (“PushPublishing”). When using the “default” Encode Implementation (software based transcoder) push publishing works and I am able to playback the multicast streams. When changing the Encode Implementation setting in Wowza to NVENC, the transcoded streams function properly, but the “pushpublish” function ceases to function. I have verified that with NVENC enabled, I can view the transcoded stream via VLC and the Wowza RTMP test player. There just seems to be a limitation on the “pushpublish” side which is preventing the add-on from ingesting the hardware-based transcoded stream.
Here is a quick overview of my current configuration;
H.264 RTSP Ingestion Stream -> Wowza Transcoder Resizes Stream to 576p (704x576) -> PushPublish creates MPEG-TS stream for multicast playback on the local network
Example Ingestion Stream -> Saved as myStream.stream
rtsp://10.10.10.1/video?inst=1
Example Transcoded Stream:
myStream.stream_576p
Listed below is a sample of my “PushPublishMap.txt” file.
myStream.stream_576p={profile:“mpegts”, streamName:“myStreamMPEGTS”, host:“227.101.0.1”, port:1234, rtpWrap:false}
When using the “default” software based transcoding method this works without issue. When using hardware acceleration transcoding via NVENC, this configuration does not work. It is as if the PushPublish function does not see the stream all together when using NVENC for transcoding.
Any assistance or pointers would be greatly appreciated.