In version 4.7.5, the playback URL for the published DASH stream on Akamai is:
https://<playback-host/dash/live////manifest.mpd
e.g. https://live-xx-xxx.akamaized.net/dash/live/123456/09876dash/master/manifest.mpd
After upgraded to version 4.8.0, we found that for the same Stream Targets settings, the URL for the MDP file didn’t change, but the element inside MPD file changed from
<BaseURL>../../../123456/09876dash/</BaseURL>
to
<BaseURL>../../123456/09876dash/master/</BaseURL>
As you can see the base url became invalid, i.e. any file would be resolved to:
https://live-xx-xxx.akamaized.net/dash/live/123456/123456/09876dash/master/
When it should be:
https://live-xx-xxx.akamaized.net/dash/live/123456/09876dash/master/
It worked fine before the upgrade. Now, the playback doesn’t work because of 404 error for the segments.
Can you confirm if this is a bug? Or is there anything wrong in our usage?
By the way: If we don’t set the Akamai Event Name, the playback works again. In that case, the MDP URL becomes:
https://live-xx-xxx.akamaized.net/dash/live/123456/master/manifest.mpd
With
<BaseURL>../../2006802/master/</BaseURL>
Does it mean the Akamai Event Name setting is unsupported in the new version?