Opting out of UI V4 with modular player, bitmovin-player-ui, and ui:false

Discussion
,
1

Version 8.245.0 uses the V4 UI. It offers a way to opt out when using the UI integration. However I’m using the bitmovin-player-ui framework with webpack and setting ui:false in player config as described in the docs. I have a custom UI so I don’t use the built-in methods (buildUI, buildModernTvUi and so on).

It’s not clear to me how I can opt out of V4 with this setup. Can anyone help?

Many thanks

2

Hi Jose,

If you have already ui: false in the player config, the built-in UIv4 won’t be used (as no UI will be auto-loaded by the player). Further, I assume you install the bitmovin-player-ui package from NPM if you use it with webpack, where you can specify the major version in your package.json. i.e. using bitmovin-player-ui: ^3.105.1 won’t install UI v4 (you would need to use ^4.0.0 or higher to use v4).

3

Thanks Daniel,

It was my mistake. It turns out the css I was importing in the webpack entry point was from bitmovin-player, not bitmovin-player-ui, and I hadn’t noticed until now:

import 'bitmovin-player/bitmovinplayer-ui.css';

Since I’m using bitmovin-player-ui, I should import the css from there instead:

import 'bitmovin-player-ui/dist/css/bitmovinplayer-ui.css';

That made the existing v3 UI work transparently with player version 8.245.

Many thanks