freetubeapp / videojs-http-source-selector Goto Github PK

at video.js 8.2.1 the icon change like that

https://user-images.githubusercontent.com/17196859/226865103-6201beaf-0470-4d30-a18b-548a0d637b96.png

just like than

i use js like that to solve it

player.on('canplaythrough',function(){
  if (player.qualityLevels().length==0) {
        document.getElementsByClassName("vjs-http-source-selector vjs-menu-button vjs-menu-button-popup vjs-control vjs-button")[0].style.display = 'none';
        }
  else {
        document.getElementsByClassName("vjs-http-source-selector vjs-menu-button vjs-menu-button-popup vjs-control vjs-button")[0].style.display = 'block';
        };
    });

not icon and some eeror in console

Custom controls appear when using the example on the videojs homepage:
https://videojs.com/

"Would it be possible to trigger an event like qualitySelected when a user click on the menu list item?
It could be useful to track users' preference among the listed choices."
jfujita#18

"Presently there are two options for default bitrate: low and high. I have a broadcast with:

270p
480p
540p
720p
1080p
I wish to default to 480p, but low sets it to 270p and high sets it to 1080p

I would prefer if I could do something like:

default: 480
If there is no "480p" then this could find the closest match (540p in my case)
"
jfujita#12

Hello
I get this in the console

DevTools failed to load source map: Could not parse content for https://example.com/videojs/videojs-http-source-selector.min.1.17.js: Unexpected token '!', "
!function("... is not valid JSON

Hi, I just forked this repo and having trouble getting the { default: "auto" } option to work locally (seemed to work on the codesandbox with the original package though). Wondering if someone could point me to the part of the code that handles this!

Currently the button is placed to the left of the full screen or it is the rightmost button if there is no full screen button

Hey - thanks for keeping this rolling, especially for Video JS 8.

I've got everything working OK if I import the module contained in the dist of this commit, however if I download the codebase, rebuild the plugin and then import it I get an error.

I'm not sure if I'm missing a step during the build, or doing something wrong to end up with code that breaks. For context, I'm:

1. Downloading the ZIP
2. Unzipping
3. Running npm install
4. Running npm build

Everything seems to build OK and the dist folder is populated as expected, however when I include this new build I get the following console error:

Would welcome any thoughts!

Description
First of all thank you for the work done guys !

Here, the video player is blocked after the quality change (either with 360p or 480p) on the 1st segment of the video.
Nothing comes up in the logs or as errors in the VHS representations part: the player is just stucked.

Have you had this problem before ? How to work around the problem ? (reset buffer ? ...)

Reduced test case
https://perso.mediatech.fr/aa/

Steps to reproduce

1. Click on the button play
2. In the first eight second switch to the 360p quality. It is normally enough to stuck the player. Otherwise you can play with the 360p and 480p quality during the first eight second and the player will be stuck too.
3. The debug mode is enabled with the provided test case: https://perso.mediatech.fr/aa/.

Errors
No errors.

What version of Video.js are you using?
8.0.4 (but reproductibled with the version 7)

Video.js plugins used.
http-source-selector, contrib-quality-levels

What browser(s) including version(s) does this occur with?
Chrome 108

What OS(es) and version(s) does this occur with?
Linux, Windows

Video.js 7.21.1
videojs-contrib-quality-levels @Version 3.0.0
videojs-http-source-selector v1.1.7

follow image is the mpd change src to common video

not icon and some eeror in console

"actually it might be as simple as adding removequalitylevel to this list https://github.com/FreeTubeApp/videojs-http-source-selector/blob/development/src/components/SourceMenuButton.js#L38 and then removing the reinit"
- @absidue

Do not work on iphones (chrome/safari) and ipads