# mp3 hls chunk packetizer not stable

**URL:** <https://community.wowza.com/t/mp3-hls-chunk-packetizer-not-stable/51318>\
**Category:** Wowza Streaming Engine\
**Created:** [May 15, 2018, 11:14am UTC](https://community.wowza.com/t/mp3-hls-chunk-packetizer-not-stable/51318 "2018-05-15T11:14:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![huy\_vo1](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@huy\_vo1](https://community.wowza.com/u/huy_vo1)\
**Post date:** [May 15, 2018, 11:14am UTC](https://community.wowza.com/t/mp3-hls-chunk-packetizer-not-stable/51318/1 "2018-05-15T11:14:40Z")

</div>

I use Wowza for many vod/audio streaming origin application. My cdn will cache chunk from Wowza origin server as user request. With .mp4 and .m4a extension, Wowza work well. With .mp3 extension, problem is: - with simillar streaming url, chunk ts is change by session (although i use origin setting), i check it by md5sum value. - my cdn cache chunk from many session and then user hear error audio. This is my link: [http://123.30.233.190/music\_audio3/_definst_/mp3:media1/song/web1/8/65555/65555.mp3/playlist.m3u8](http://123.30.233.190/music_audio3/_definst_/mp3:media1/song/web1/8/65555/65555.mp3/playlist.m3u8) my audio file [http://103.216.120.24:85/file/audio.mp3](http://103.216.120.24:85/file/audio.mp3) All config,log of wowza is total4.zip. My wowza is 4.6.0. a.zip and a1.zip is chunk of similar streaming link at diffirent chrome tab.

Log files:

[https://www.dropbox.com/s/iox48t61q71otny/a.zip?dl=0](https://www.dropbox.com/s/iox48t61q71otny/a.zip?dl=0)

[https://www.dropbox.com/s/iox48t61q71otny/a.zip?dl=0](https://www.dropbox.com/s/iox48t61q71otny/a.zip?dl=0)

---

<div class="post-metadata">

**Author:** ![huy\_vo1](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@huy\_vo1](https://community.wowza.com/u/huy_vo1)\
**Post date:** [April 17, 2019, 7:29am UTC](https://community.wowza.com/t/mp3-hls-chunk-packetizer-not-stable/51318/2 "2019-04-17T07:29:38Z")

</div>

Did wowza fix this problem?
