Add maxVideoBufferSize option to limit the amount of video data (in kilobytes?) the RxPlayer will push on low-end devices

[achrafl0]

No description provided.

[peaBerberian]

Because one RepresentationStream is created per-type of buffer (one audio, one video, one text...), I'm under the impression that the current code could possibly lead to number_of_buffers * buffer_size, no?

In any case, I'm wondering if that buffer size setting would not be better per-type: especially one for audio and one for video.
What do you think?

[peaBerberian]

Can you also rebase on master so the new GitHub actions are run?

[peaBerberian]

Almost done.
To me, there's still:

1. the config documentation to update.
2. The point about gcedPosition to clarify
3. the api documentation to add (both in /doc/api/Creating_a_Player.md for constructor options and I guess in the /doc/api/Buffer_Control directory for the buffer size methods)
4. I would like that we first merge performance tests (Add performance tests #1062) so we can officially use them here before merging

[peaBerberian]

I also updated the base branch to next as we usually do for new features (the idea is that, in a case of a huge issue in production, a less risky patch version without any new feature can be derived from the master branch)

[peaBerberian]

When adding documentation files, you have also to update the .docConfig.json file in that directory so that the documentation generator knows the order the page have to be shown in.

Without it, the corresponding page won't be converted into HTML.

[peaBerberian]

I think we shouldn't expose the name of our internal variable for two reasons:

• it might confuse the user
• it might change at any new version, without us thinking to update that part of the documentation

[peaBerberian]

Needs to be rebased on next (I supposed since the config PR has been merged)