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

**URL:** <https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972>\
**Category:** Wowza Streaming Engine\
**Tags:** wowza-streaming-server-java-api\
**Created:** [March 12, 2024, 7:08am UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972 "2024-03-12T07:08:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![heeyeon\_jang](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@heeyeon\_jang](https://community.wowza.com/u/heeyeon_jang)\
**Post date:** [March 12, 2024, 7:08am UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972/1 "2024-03-12T07:08:04Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Scott\_Kellicker2](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/scott_kellicker2/32/1337_2.png) [@Scott\_Kellicker2](https://community.wowza.com/u/Scott_Kellicker2)\
**Post date:** [March 12, 2024, 7:20pm UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972/2 "2024-03-12T19:20:11Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![heeyeon\_jang](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@heeyeon\_jang](https://community.wowza.com/u/heeyeon_jang)\
**Post date:** [March 13, 2024, 12:05am UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972/3 "2024-03-13T00:05:36Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![heeyeon\_jang](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@heeyeon\_jang](https://community.wowza.com/u/heeyeon_jang)\
**Post date:** [March 13, 2024, 12:39am UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972/4 "2024-03-13T00:39:20Z")

</div>

As a result, hls is played very normally.

Why is byte out only for rtsp so slow?

---

<div class="post-metadata">

**Author:** ![Scott\_Kellicker2](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/scott_kellicker2/32/1337_2.png) [@Scott\_Kellicker2](https://community.wowza.com/u/Scott_Kellicker2)\
**Post date:** [March 13, 2024, 2:35pm UTC](https://community.wowza.com/t/bytes-in-is-recorded-at-2-9-3-mbits-s-and-bytes-out-is-recorded-at-336-kbits-s/96972/5 "2024-03-13T14:35:20Z")

</div>

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
