Wowza Community

4.7.5 to 4.7.7 upgrade breaks Akamai PushPublish behaviour

We recently upgraded to 4.7.7 and the move broke some of the logic of the Stream Target (pushpublish) behaviour, such that making API driven changes to the pushpublish map causes different undesirable change.

Previously changing the http.playlistCount value, would cause the chunklist to grow and/or shrink according to the value without reseting the sequence.

so having a http.playlistCount = 1000

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-TARGETDURATION:6

#EXT-X-MEDIA-SEQUENCE:20

#EXTINF:6.0,

i0dmdoji/00000000/media_20.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_21.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_22.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_23.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_24.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_25.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_26.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_27.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_28.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_29.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_30.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_31.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_32.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_33.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_34.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_35.ts

THEN changing to http.playlistCount = 0 (forces the default which is the main app config = 3 chunks) becomes

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-TARGETDURATION:6

#EXT-X-MEDIA-SEQUENCE:35

#EXTINF:6.0,

i0dmdoji/00000000/media_35.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_36.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_37.ts

then changing back would be

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-TARGETDURATION:6

#EXT-X-MEDIA-SEQUENCE:37

#EXTINF:6.0,

i0dmdoji/00000000/media_37.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_38.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_39.ts

#EXTINF:6.0,

i0dmdoji/00000000/media_40.ts

etc.

this behavour now has completely vanished so that any change made forces the chunklist to revert to

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-TARGETDURATION:6

#EXT-X-MEDIA-SEQUENCE:1

#EXTINF:6.0,

5ysqnzdv/00000000/media_1.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_2.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_3.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_4.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_5.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_6.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_7.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_8.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_9.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_10.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_11.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_12.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_13.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_14.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_15.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_16.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_17.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_18.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_19.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_20.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_21.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_22.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_23.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_24.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_25.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_26.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_27.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_28.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_29.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_30.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_31.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_32.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_33.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_34.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_35.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_36.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_37.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_38.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_39.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_40.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_41.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_42.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_43.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_44.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_45.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_46.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_47.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_48.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_49.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_50.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_51.ts

now changes to

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-TARGETDURATION:6

#EXT-X-MEDIA-SEQUENCE:49

#EXTINF:6.0,

5ysqnzdv/00000000/media_1.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_2.ts

#EXTINF:6.0,

5ysqnzdv/00000000/media_3.ts

Which is just plain old wrong, sine the CDN will already have a chunk with that name and everything just breaks.

Discussing this with engineers and will respond asap. Sorry for your trouble @Joe Bray.

You might be using other parameters that need to be updated in order to give you correct functionality @Joe Bray…The engineering team did look at what you have posted, but are unable to reach a conclusion without more info.

They would like you to request a support ticket and ask you please provide all logs and configs as directed when you submit it. Thanks for reaching out about this and you can submit a ticket here:

https://www.wowza.com/support/open-ticket

I don’t believe I am, but i have zipped and sent as a support ticket.

This was resolved in ticket 311923.

Summary:
Changes in the Wowza Streaming Engine software version 4.7.6:

  • Only the group name was used in the URL rather than the event name and the group name, because we thought that aligned better with Akamai recommendations for encoders.

Other related changes in 4.7.6:

  • Changed the “adaptiveGroups” (plural) parameter to “adaptiveGroup” (singular), meaning a target can only be part of one group We initially completely dropped support for “adaptiveGroups” (plural), but added it back later (post-4.7.6.) for backward compatibility.
  • The “streamName” folder (which contains all of the chunks) in the push and playback URLs is no longer directly located under the “akamai.streamId” folder, but instead moved under the “adaptiveGroup” folder for the group the target belongs to. If not in a group then the “streamName” folder is placed under the eventName folder, which is either the “akamai.eventName” value specified in the target, or a default evenName of “defEvent”.

We plan to return to the previous behaviour where both the event name and the group name are provided in a future version of the Wowza software.

Regards,
Jason Hilton
Wowza Support Engineer

Actually Jason, this wasn’t resolved in 311923, that ticket was for the change in behaviour for group vs. eventnames and was resolved in a clarification/modifcation of the 4.7.7 behaviour. The issue above is are being dealt with in ticket 312279 and is still on-going.