[mpeg-dash] .smil file has stop after play a first chunk

[Larry_Kim]

Hi all,

I found some weird issue about mpeg-dash adaptive streaming with smil file on Wowza engine.

After playing a first chunk, the second chunk always returns 404 not found error.

But without smil file the streaming chunks are no problem.

Is there anybody can help me to solve this issue?

[Using smil file] - the second chunk returns 404 not found error.

http://dev-streaming.koomvr.com/vods3/definst/smil:amazons3/dev-vod.koomvr.com/video_8c32d650-e0a8-462a-9546-29131a29d1ca_03.smil/manifest.mpd

[Using mp4 file] - without smil is ok.

http://dev-streaming.koomvr.com/vods3/definst/mp4:amazons3/dev-vod.koomvr.com/video_8c32d650-e0a8-462a-9546-29131a29d1ca_03.mp4/manifest.mpd

http://dev-streaming.koomvr.com/vods3/definst/mp4:amazons3/dev-vod.koomvr.com/video_8c32d650-e0a8-462a-9546-29131a29d1ca_03_low.mp4/manifest.mpd

[Spec]

• Wowza version 4.1.1

• log : https://dl.dropboxusercontent.com/u/5284271/logs.tar.gz

• conf : https://dl.dropboxusercontent.com/u/5284271/conf.tar.gz

-Larry

I tried to post the replay but I couldn’t. coz I’m adding my reply on the below of this post.

---

Hi JasonH,

Thanks for your replay,

I used jwplayer(web) and exoplayer(android) for testing.

http://www.jwplayer.com/labs/roadmap/mpeg-dash/

http://developer.android.com/guide/topics/media/exoplayer.html

One thing makes me starange is following clip doesn’t make same issue.

http://streaming.koomvr.com/vods3/definst/smil:amazons3/vod.koomvr.com/video_1d0c302b-f8ba-4396-bc7d-bd43c9face9a_03.smil/manifest.mpd

Following clip’s duration is 48seconds but it alwasys stops at 24 seconds even on the wowza test player.

http://streaming.koomvr.com/vods3/definst/smil:amazons3/vod.koomvr.com/video_e76f6643-3cd0-4274-8c7c-cc2bbd018d8c_03.smil/manifest.mpd

Thanks,

-Larry

[Jason_Hilton]

Hi Larry,

Using the MPEG-DASH player in the Wowza Streaming Engine Manager, these streams (including the .smil) played without issue.

Can you confirm this is the case for you and give more detail on the MPEG-DASH player you’re using for playback?

Jason

[Mathias_StjernstrA_m]

PING!

Anyone updates on this issue?

[Mathias_StjernstrA_m]

Thanks for the reply Paul. We are still investigating it (we have the same problem as the initial poster). We think it can be caused of videos which is not correctly bitrate aligned. We will continue to investigate and post when we have more info/data to share.

[Jason_Hilton]

Hi Larry,

Using JW player’s MPEG-DASH player I don’t see any issue with playback either. In fact I think it handles this particular stream better than our MPEG-DASH Test Player because after playing the content using the JW player I do see the content is longer than what is being played in the MPEG-DASH Test Player. For some reason I was only getting 21 seconds using our player.

I recommend that you test using the bigbuckbunny content and bigbuckbunny.smil file which can all be downloaded from the article below.

How to do adaptive bitrate streaming

If you’re seeing issues with this content too, I recommend opening a ticket with our support team (support@wowza.com) so that we can take a closer look.

When creating a ticket ensure that you include a ZIP file containing the [Wowza-Install]/conf/ and [Wowza-Install]/logs/ directories for analysis.

The new logs should include the testing done using the content downloaded from the ABR streaming article linked above.

I also recommend using a regular VOD application for this test to rule out any issues with MediaCache and getting content from your S3 bucket.

Regards,

Jason

[Paul_Shields]

Hi,

You’re replying to a post that is over a year old, so it would be best to know what issue you are experiencing, particularly as there have been many changes both to the DASH spec and to how we process these streams in that time period. Please provide an example of a stream showing this issue and steps required to reproduce and we can check it out for you. If you don’t wish to make such details public then consider opening a support ticket and you can be assured it will be looked into for you.

Regards,

Paul

[Larry_Kim]

Hi Larry,

Using the MPEG-DASH player in the Wowza Streaming Engine Manager, these streams (including the .smil) played without issue.

Can you confirm this is the case for you and give more detail on the MPEG-DASH player you’re using for playback?

Jason

Hi JasonH,

Thanks for your replay.

I used jwplayer(http://www.jwplayer.com/labs/roadmap/mpeg-dash/) and exoplayer(http://developer.android.com/guide/topics/media/exoplayer.html) for testing.

One thing strange to me is this clip(http://streaming.koomvr.com/vods3/definst/smil:amazons3/vod.koomvr.com/video_1d0c302b-f8ba-4396-bc7d-bd43c9face9a_03.smil/manifest.mpd?ver) doesn’t have this issue on any player.

Following clip’s duration is 47 seconds but in playing at 24 seconds the issue always occurs even on Wowza test player.

I could see the 404 errors on the browser console as well.

http://streaming.koomvr.com/vods3/definst/smil:amazons3/vod.koomvr.com/video_e76f6643-3cd0-4274-8c7c-cc2bbd018d8c_03.smil/manifest.mpd

Thanks,

-Larry

[Larry_Kim]

Hi JasonH,

Thanks for your replay,

I used jwplayer(web) and exoplayer(android) for testing.

http://www.jwplayer.com/labs/roadmap/mpeg-dash/

http://developer.android.com/guide/t…exoplayer.html

One thing makes me starange is following clip doesn’t make same issue.

http://streaming.koomvr.com/vods3/_d…l/manifest.mpd

Following clip’s duration is 48seconds but it alwasys stops at 24 seconds even on the wowza test player.

http://streaming.koomvr.com/vods3/_d…l/manifest.mpd

Thanks,

-Larry

[Infomac_Solucoes_em]

Hi all,

I know this thread is old but I’ve the same issue here.

Have a sample video in smil file and mp4 source, the stream works on mp4 directly but not in smil file over MPEG DASH.

It’s funny because in HLS and HDS protocol works fine, without issues. If I put only one source at smil file it works fine too, even on MPEG DASH.

Larry, did you have a solution?

Thanks,

Luciano