Use of older Playback tool 2.0 in BBB V2.4

[Wolfgang Pein]

Hi all,

for some reason we would like to use the old playback tool 2.0 in a V2.4 environment.

We are aware the fact that this might be a riscy approach and may mean that we have to individually maintain Bigbluebutton for this special configuration.

Nevertheless we would like to know whether it would be possible at all to do this and what needs to be configured in BBB to have this work.

We recognized that all playback tools including version 2.0 still exist in BBB V2.4 environment (directory /var/bigbluebutton/playback/presentation). Particularly there are directories for Version 2.0 and 2.3 (the current playback tool).

So what we would like to know is what BBB configuration files need to be adapted to use V2.0 of the playback tool rather than the current version 2.3.

Is there 1 specific configuration file for this change (and what parameter need to be changed?) or are there several files which need changes?

We are aware that we are loosing functionality compared to playback tool 2.3.

("The 2.0 javascript player won't see some of the newer recording artifacts, like external video urls, and some of the custom polling results/notes etc that appear in the newer 2.4 react playback tool.") but for our environment this will be acceptable.

Thanks for your help!

Wolfgang

[Pedro Beschorner Marin]

I think the easiest way to do that would be using nginx to redirect the v2.3 URL to v2.0. Take a look at /etc/bigbluebutton/nginx/presentation.nginx and try reverting this part https://github.com/bigbluebutton/bigbluebutton/commit/47af1a391b53a04681ed585f308ef4c47466015d . You will also need to add this 301 return in /etc/bigbluebutton/nginx/playback.nginx to point it out to the player you want to use.

[Wolfgang Pein]

Thanks for the quick answer. However I am not sure whether this helps.

I should have mentioned that we do not use Greenlight but our own frontend on another server.

[Hiroshi Suga]

Just by coincidence, I was doing very much the same thing. And what Pedro says worked. Even if you are using your own frontend, it wouldn't be a problem as long as it specify the URL  https://YOUR_SERVER/playback/presentation/2.0/playback.html?meetingId=YOUR_MEETING_ID

[Wolfgang Pein]

Great! Thanks! We will give it a try!

[Pedro Beschorner Marin]

Just out of curiosity, what exactly are the problems with using the new player?

[Wolfgang Pein]

Hi guys, especially Pedro and Hiroshi,

you are great, thank you so much. This was the solution for our problem/question.

I work in the admin group so I am not able to tell you why exactly we need this approach other then providing the following statement by a developper:

" Submenus in the video-list-items have been changed, from V2.4.1 onwards  there is a new "video pin" feature included ".

I will ask the developement group to answer Pedros question in more detail!

Thanks again, this was so important for our project!

:-) Wolfgang