I am testing SRT on Wowza Streaming Engine. The on-prem live encoder is sending srt stream with Dolby Audio in it. The Wowza Encoding Engine does not recognize the audio and gets rid of audio stream and publishes DASH and HLS outputs without audio in it.
If I configure on-prem live encoder with AAC audio, it works and I see audio track as part of DASH and HLS outputs.
See the tech specs of Wowza Streaming Engine here: https://www.wowza.com/products/streaming-engine/specifications; it supports AC3 (Dolby Digital) and EAC3 (Dolby Digital Plus), is it either of these that you’re sending from your encoder?
I had filed a bug related to codec signaling (Dolby audio related) which got fixed in ver 4.7.8. Last week, I have had success with UDP ingest ( by following those steps) and outputting DASH and HLS with expected codec signal.
I am exploring what does SRT do? My setup is this: On-prem live encoder + SRT server sending SDR+DolbyAudio.srt (srt://IP:Port) to Wowza Streaming Engine in EC2 as an ingest. Wowza Engine packaging that .srt stream to DASH and HLS. This output doesn’t include Dolby audio.
You could consider reviewing this article since you can enable passthrough as an option for your workflow and potentially have some success there.
Hello Karel Boek,
I am aware that SRT is codec agnostic and it supports those audio codecs.
Right now I am testing this: On-prem live encoder + SRT server sending SDR+DolbyAudio to Wowza Streaming Engine in EC2. Wowza Engine packaging .srt stream to DASH and HLS.
When I use Dolby Audio (stereo or 5.1) to begin with Wowza Engine does not use audio and creates DASH and HLS with video only streams. If I use AAC (stereo or 5.1) with the same setup, DASH and HLS streams get both audio and video.
Have you checked the logs? I suppose there’s some warning or error about this …