We have our Wowza streaming engine (version 4.7.1) hosted on AWS.
We use the following ffmpeg command to stream our camera to wowza server :
ffmpeg -f dshow -s 320x240 -i video=“HP TrueVision HD” -crf 32 -vcodec h264 -pix_fmt yuv420p -r 6 -g 10 -tune zerolatency -ttl 0 -f rtsp -muxdelay 1.0 rtsp://default:firstname.lastname@example.org:1935/live/nIwh43fs7205AwG2_V1
The command works fine when used within our internal network. However when we run the ffmpeg command from external wifi/mobile networks we get an error -> “the network throughput 0 @ 0 bits/s”.
Would greatly appreciate your help in resolving this error. thanks.
Hello @Felix Mohan
Are you seeing the “the network throughput 0 @ 0 bits/s” error in the ffmpeg command line or in the Wowza logs? This could just be an issue with the ffmpeg syntax.
The other thing to look at is the Wowza Engine Manager Source Security. Make sure the Client Restrictions are configured correctly to allow the encoder.
Constant Rate Factor is not compatible with streaming media and as such you must use a bitrate based encode. Please look at the following example command line and adjust accordingly.
ffmpeg -f dshow -s 320x240 -i video="HP TrueVision HD" -pix_fmt yuv420p -vsync 1 -vcodec libx264 -r 6 -g 12 -threads 0 -b:v: 256k -bufsize 256k -maxrate 384k -minrate 128k -preset veryfast -profile:v baseline -tune zerolatency -x264opts no-scenecut -rtsp_transport tcp -f rtsp rtsp://default:email@example.com:1935/live/nIwh43fs7205AwG2_V1
-vsync 1 will create frames at an even distance.
-g 12 will create keyframes, also known as a Group of Pictures or GOP, every two seconds based on your six second frame rate.
-x64opts no-scenecut ensures that your keyframes are evenly spaced. This is optional in newer builds of FFmpeg.
-rtsp_transport tcp will use TCP for both negotiation and data. This is also known as RTSP interleaved.