Skip to content

4. Send the stream and verify playback โ€‹

Updated

Send a test signal to the transmission path configured in the previous three steps, and check the StreamPackage origin and the CSS CDN in turn.

Prerequisites โ€‹

  • Verify that the StreamLink flow and the StreamLive channel are started.
  • Prepare the actual push address of the StreamLink input.
  • Prepare the StreamPackage endpoint URL and the CSS playback URL.
  • Check the allowed push IP policy, the required authentication information, DNS, and the HTTPS certificate.
  • Prepare FFmpeg / ffprobe / ffplay, or OBS and the HLS playback player.

The URLs below are for illustration purposes.

1. Sending the test signal โ€‹

In OBS, enter the server address and stream key that match the StreamLink input settings and start streaming. If you use FFmpeg, you can send a video pattern and the 440Hz test tone as shown below. Lower the volume before playing the test tone.

bash
STREAM_PUSH_URL='rtmp://YOUR_STREAMLINK_HOST/YOUR_APP/YOUR_STREAM_KEY'
ffmpeg -re \
  -f lavfi -i "testsrc=size=1920x1080:rate=30" \
  -f lavfi -i "sine=frequency=440:sample_rate=48000" \
  -c:v libx264 -preset veryfast -b:v 4000k -maxrate 4000k -bufsize 8000k \
  -pix_fmt yuv420p -g 60 \
  -c:a aac -b:a 128k -ar 48000 \
  -f flv "$STREAM_PUSH_URL"

Check the number of pushed frames and the time in the FFmpeg log, along with the StreamLink input address / protocol / port / allowed IP and the destination receiving status.

2. Checking transmission and processing status โ€‹

SegmentWhat to check
Encoder โ†’ StreamLinkInput connection and receiving status
StreamLink โ†’ StreamLiveFlow output destination and StreamLive input receiving status
StreamLive โ†’ StreamPackageOutput group, destination channel ID, output status
StreamPackage โ†’ CDNDomain connection, bidirectional service permission, origin access policy

Check the RUNNING status, the input / output metrics, and the final playback together.

3. Checking the origin master playlist โ€‹

bash
STREAM_ORIGIN_URL='https://YOUR_PACKAGE_HOST/YOUR_ENDPOINT_PATH/index.m3u8'
curl --fail-with-body --show-error --silent --max-time 20 "$STREAM_ORIGIN_URL"

If endpoint authentication is configured, apply the headers or authentication information required for that request separately.

The following is a format example of a list that contains two resolutions. File names and values vary depending on the actual configuration.

m3u8
#EXTM3U
#EXT-X-STREAM-INF:BANDWIDTH=2128000,RESOLUTION=1280x720,FRAME-RATE=30.000
720p.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=4128000,RESOLUTION=1920x1080,FRAME-RATE=30.000
1080p.m3u8

If both entries appear, the two outputs are declared in the master list. To verify that the video of each output is normal, you need to go down to the media playlist and the actual segments.

4. Checking media playlists and segments โ€‹

Resolve the media playlist URI written in the master against the actual master URL. If it is only a file name, use the same directory; if it starts with /, use the root of the same host. If it is a complete URL, use that address as is.

bash
STREAM_MEDIA_URL='https://YOUR_PACKAGE_HOST/YOUR_ENDPOINT_PATH/720p.m3u8'
curl --fail-with-body --show-error --silent --max-time 20 "$STREAM_MEDIA_URL"

Re-check the list in the following format at intervals of a few seconds.

m3u8
#EXTM3U
#EXT-X-TARGETDURATION:4
#EXT-X-MEDIA-SEQUENCE:100
#EXTINF:4.000,
segment100.ts
#EXTINF:4.000,
segment101.ts
  • Check whether new segments are added during the live push.
  • For a sliding playlist, check whether MEDIA-SEQUENCE also increases over time.
  • Check whether the segment URLs written in the playlist are actually accessible.
  • Check whether video / audio is included in 720p and 1080p respectively.
bash
ffprobe -v error -show_entries stream=codec_type,codec_name,width,height,r_frame_rate \
  -of json "$STREAM_MEDIA_URL"

The ffprobe result is used to check the media format. Whether there is a black screen, muting, or stuttering must be checked separately through actual playback.

5. Verifying playback through CDN โ€‹

Repeat the same check with the CSS playback URL connected to StreamPackage.

bash
STREAM_CDN_URL='https://YOUR_PLAYBACK_DOMAIN/YOUR_ENDPOINT_PATH/index.m3u8'
curl --fail-with-body --show-error --silent --max-time 20 \
  --dump-header - --output /dev/null "$STREAM_CDN_URL"
ffplay "$STREAM_CDN_URL"

Check whether the video pattern and the test tone play in the player and whether playback continues without interruption for a certain period of time. Because automatic quality selection may play only one resolution, inspect each media playlist separately as well.

Verify HTTPS playback with a valid certificate / host name / certificate chain.

Identifying the failing segment โ€‹

SymptomCheck first
StreamLink input โ€”Encoder push address / key, protocol, firewall and allowed IP
StreamLive input โ€”Flow output address and StreamLive security group
Origin playlist 404Endpoint path, whether the origin is being pushed, output destination
403 from the origin or CDNPermission of the request referrer, header / query authentication, IP restrictions, domain connection
Master normal / media result checkMedia URI resolution, path and authentication information
Media normal / segment result checkSegment URI and access policy, validity of the cached playlist
Playlist refresh stoppedOrigin push, input / output status, playlist cache
Origin playback / CDN result checkCSS origin access permission, Host / path / authentication forwarding, DNS / TLS
Video plays but sound โ€”Origin audio track, audio selection and output template

Check the host / path / response / per-segment logs of the request together.

Completion criteria โ€‹

  1. Confirm origin reception and output delivery in StreamLink and StreamLive
  2. Confirm the required resolution list in the StreamPackage master
  3. Confirm the refresh of each media playlist and segment access
  4. Confirm actual video / audio playback in the origin and the CSS CDN
  5. Confirm input / output status and continuous playback during playback

Ending the test โ€‹

For FFmpeg, press Ctrl+C in the running terminal to stop the push. Then stop the StreamLink flow and the StreamLive channel used for the test. Deletion is optional; first check whether there are shared resources and dependencies.

Check the running resources and the storage / transfer usage together.

Built with VitePress ยท Deployed on Tencent EdgeOne Pages