Moodle ActiveProLearn Documentation

This plugin installs the standard way:

1. Unzip archive into the 'mod' directory of Moodle
2. Browse to administration notifications to finish installation.

The global settings mostly deal with default values for many advanced parameters.

Chooses the default technology used when creating a new instance. Both player may not provide exactly the same options, JW Player, f.e., natively is provided to play YouTube streams, but uses Flash tecnhology. flowplayer is provided in html5 technolgy, but may not support adaptative bitrate.

Special feature for the full javascript API player setup (flowplayer). Displays the complete JS script for debugging prupose.

If enabled, the teacher in the course may be allowed to switch the player technology for the instance.

Player expected width. Some external constraints such as theme or other layout situation may force this with not to be maintained.

the value should be compatible with a CSS width: attribute, in percent or pixels.

Height, in pixels (no relative nor percent).

the default skin of the JW player.

Shows or hides video control commands and icons.

If player allows to, will change the location of the controls on the player interface.

If player allows to, changes the foreground color of the video GUI.

If player allows to, changes the background color of the video GUI, f.e. the backgorund when no vido nor poster is playing.

If player allows to, changes the light color of the video GUI, tis usually afects the player control texts.

If enabled, new player instances will autoplay media as a default.

If enabled, the full screen switch is available for users as a default for new instances.

Modes of image adjustement to outbounds of the player.

Default volume for new player instances.

Some devices have some special behavious with the full screen feature. Usually those device provide a simulation of standard full-screen behaviour, rather than device native. If you experience some difficulties with the full screen among your users, this may help to fix some inadequate behaviours.

The MPlayer module can cooperate with a defered video stream player. When feeding Moodle with videos, the media file is first upladed in moodle the standard way, then it is mooved to the remote storage and replaced locally by a manifest text file.

For this configuration to work, you will need locally mounting a remote volume from the media server filesystem.

Till now we worked in two opensource/community directions:

• Wowza server
• Apache pseudo-streaming using H264 additional module (https://www.apachehaus.net/modules/mod_h264_streaming/)

Main domain for the HTTP access to media .mp4

Relative media path. this will be append to the server URL.

Give the local mount path for the remote storage volume. this needs to be an absolute path in your local system (mount point).

The rtmp url of the flow server. In case the server exploits HLS (over HTTP) or is using an H264 over apache distribution, this setting is not relevant.

Many streaming server propose several applications: VOD (video ondemand) is the standard application when reading a stored video, and live streaming when the stream comes from an active camera.

Give the local mount path for the remote storage volume. this needs to be an absolute path in your local system (mount point).

Return to the component index - Back to common plugin index - Back to home