Bytes in is recorded at 2.9~3 Mbits/s, and bytes out is recorded at 336 Kbits/s

[heeyeon_jang]

In Wowza, I added the rtsp address to the stream file and added that address to the incoming stream as rtp.

But here’s the problem
Bytes in is recorded at 2.9~3 Mbits/s, and bytes out is recorded at 336 Kbits/s.
When playing a video in VLC player, it takes a huge amount of time to load.

The port’s rtsp address is wowza -> rtsp address 554 TCP (one-way), and the vlc calling that address is vlc->wowza 1935 TCP (one-way).

What can I do? Please take a guess

[Scott_Kellicker2]

How are you playing the stream as HLS (playlist.m3u8?). Things like GOP length of incoming stream, and segment(chunk) size will also come into play

I would try it with another player, like Wowza’s player or hls.js. Try Phil Cluff’s players (google it bc I cannot put a link in this post). this hosts a bunch of different players, open source and commercial

[heeyeon_jang]

Only rtsp can be used… Please help me figure out what the problem is. hls is not used.

This is a situation where wowza is called through rtsp.

[heeyeon_jang]

As a result, hls is played very normally.

Why is byte out only for rtsp so slow?

[Scott_Kellicker2]

Hmm, I’m not sure. Not that ,many people stream rtsp OUT of Wowza, at least to my knowledge

I would check the wowza logs, and try a different rtsp player to eliminate VLC as a source of the problems. There may also be some debug settings you could set to get additional logging info