Closed loicraux closed 1 year ago
I'm reviewing and the player works correctly and there are 5 downloads in parallel.
The difference with the bitmovin stream is that your stream uses HTTP2 and the bitmovin stream uses HTTP 1.1
The graph you see in the devtools indicates the number of open TCP connections. In HTTP2, mutiplexing is used and the same channel is used, which is why in the graph you do not see several in parallel even though they are done in parallel.
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen
in a comment.
Have you read the FAQ and checked for duplicate open issues? Yes
If the problem is related to FairPlay, have you read the tutorial? N / A
What version of Shaka Player are you using? Latest version
Can you reproduce the issue with our latest release version? Yes
Can you reproduce the issue with the latest code from
main
? YesAre you using the demo app or your own custom app? Own custom app
If custom app, can you reproduce the issue using our demo app? Correct me if I'm wrong, but I think I cannot download assets using the Shaka Player demo app (which kind of makes sense)
What browser and OS are you using? Chrome 117.0.5938.132 (Official Build) (64-bit)
For embedded devices (smart TVs, etc.), what model and firmware version are you using? N/A
What are the manifest and license server URIs?
What configuration are you using? What is the output of
player.getConfiguration()
? Player configuration right before the call tostorage.store
:Note that
offline.numberOfParallelDownloads
is set to 5 (default value)What did you do?
Download a
.mpd
asset for offline playback using shaka player'sstorage.store
API and the above configurationWhat did you expect to happen?
offline.numberOfParallelDownloads
setting being set to 5, I would expect to have 5 chunks downloaded in parallel.With some other .mpd manifests (e.g. https://bitmovin-a.akamaihd.net/content/playhouse-vr/mpds/105560.mpd),
.m4s
chunks (also DASH segments) for example are downloaded in parallel (5 downloads in parallel in this case, which corresponds to the default value ofnumberOfParallelDownloads
) and the download is therefore much faster...What actually happened?
.dash
chunks are downloaded, but they are downloaded one after the other, in other words there is no parallelisation of chunk downloads, despiteoffline.numberOfParallelDownloads
setting being set to 5 (default value) and the download is consequently slow :