You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In MSS live, playback is achieved by refreshing the manifest, which is not according to the Specification( [MS-SSTR] — v20120705 -Smooth Streaming Protocol Specification).
According to the spec the TFXD and TFRF boxes should be used to get the new fragment info and the same should be used to update the manifest.
Can you please let us know why the manifest was refreshed every time instead of parsing the boxes?
Thanks
Manjunath N
The text was updated successfully, but these errors were encountered:
This fixes issues google#855
----
Merge with feature/mss-noreload branch changes into 2.11.8 version tag
- Update FragmentedMp4Extractor.java with feature/mss-noreload branch changes with additional code in parseUuid() method for TFRF_UUID type
- Update DefaultSsChunkSource.java with feature/mss-noreload branch changes with new getNextChunk() method implementation used only for live manifests
- Update other smoothstreaming classes with feature/mss-noreload branch changes
ojw28
changed the title
MSS Live Playback : Not according to Spec
SmoothStreaming: Use TFXD and TFRF boxes for new fragment info & manifest updates
May 10, 2021
Hello,
In MSS live, playback is achieved by refreshing the manifest, which is not according to the Specification( [MS-SSTR] — v20120705 -Smooth Streaming Protocol Specification).
According to the spec the TFXD and TFRF boxes should be used to get the new fragment info and the same should be used to update the manifest.
Can you please let us know why the manifest was refreshed every time instead of parsing the boxes?
Thanks
Manjunath N
The text was updated successfully, but these errors were encountered: