Since October 2025, this plugin uses a new architecture due to Elastic Transcoder being decomissioned.

See the migration guide for how to migrate and consideration.

Much of the information in this README is now out of date.

Smart media aims to enhance Moodle's processing and delivery of multimedia while simplifying the process of managing multimedia for teachers and students.

The smart media plugins in Moodle aim to solve the following two user stories:

As a teacher I have a video that works on my local device and I want to make that video available to my students in a suitable format, by adding it to any rich text area in Moodle. Without the need for me to do any other operations on the video apart from uploading to Moodle.

As a student I want to be able to view any video on my chosen device; added to a rich text area in Moodle by a teacher. Regardless of the environment I’m accessing the video or my bandwidth limitations.

Smart media leverages cloud services provided through Amazon Web Services (AWS) in order to conduct video transcoding into required formats and provide additional analytics functionality for multimedia.

The following sections outline how to install the required smart media plugins in Moodle. For advanced setup and plugin usage once the plugins have been installed please see the project wiki.

This plugin currently supports Moodle:

• 4.5+

There are several dependencies required and steps to complete in order to setup smart media in your Moodle instance.

Note: These instructions assume knowledge of Git, Moodle plugin functionality and that you have access to the infrastructure that runs your Moodle instance.

1. Clone the local_smartmedia plugin git repo into your Moodle codebase root git clone [email protected]:catalyst/moodle-local_smartmedia.git local/smartmedia
2. Install dependency plugin filter_smartmedia. See filter_smartmedia
3. Install dependency binary FFmpeg on your Moodle server. See FFmpeg
4. Setup the AWS Stack. See AWS Stack Setup
5. Update plugin settings. See Plugin Settings

The filter_smartmedia plugin is a dependency for local_smartmedia, it provides rendering of converted smart media assets in the Moodle UI.

You can install this by cloning the git repo into your Moodle codebase:

git clone https://github.com/catalyst/moodle-filter_smartmedia filter/smartmedia

More detailed information is available at https://github.com/catalyst/moodle-filter_smartmedia in the README

FFmpeg is an open source multimedia framework and provides the multimedia stream analyser ffprobe, facilitating the collection of metadata for multimedia.

This metadata is utilised to identify which files in your Moodle instance to convert and to present reports on what media is actually in your Moodle instance.

FFmpeg is a requirement for running the local/smartmedia scheduled tasks.

To install FFmpeg, if your using a Debian based Linux distribution:

sudo apt-get update
sudo apt install ffmpeg

For Windows based or any other servers follow the instructions and link at https://ffmpeg.org/download.html

You can get more info about FFmpeg at https://ffmpeg.org/

The following steps will setup the Amazon Web Services (AWS) infrastructure. The AWS infrastructure is required to do the actual processing of multimedia files. While setting up the AWS infrastructure is largely automated by scripts included in this plugin, a working knowledge of AWS is highly recommended.

For more information on how the submitted files are processed in AWS please refer to the topic: Conversion Architecture

Note: Full support on setting up an AWS account and API access keys for AWS stack infrastructure provisioning is beyond the scope of this guide.

Note: This plugin currently does not support multiple Moodle's sharing Smartmedia Infrastructure. The AWS stack setup must be performed on an environment by environment basis, with a unique stack per environment.

To setup the AWS conversion stack infrastructure:

1. Create an AWS account, see: https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/ for information on how to do this.
2. Create an AWS API user with administrator access and generate a API Key ID and a API Secret Key, see: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html for information on how to do this.
3. Change to your Moodle instance application directory. e.g. cd /var/www/moodle
4. Run the provisioning script below, replacing <keyid> and <secretkey> With the AWS API Key ID and AWS API Secret Key that you obtained in step 2.
   Replace <region> with the AWS region you wish to set up your AWS stack, e.g. ap-southeast-2.
   The command to execute is:

sudo -u www-data php local/smartmedia/cli/provision.php \
--keyid=<keyid> \
--secret=<secretkey> \
--region=<region> \

Note: the user may be different to www-data on your system.

Record the ouput from the resources section of the script information.

Once the dependency plugins are installed, the local/smartmedia plugin is installed, ffmpeg is installed and the AWS stack has been setup; it is now time to configure Moodle.

To do this:

1. Log into the Moodle UI as a site administrator
2. Navigate to Site Administration > Plugins > Local plugins > Smart Media.
3. Set all required fields. All of these with the exception of the FFProbe path will be gained from the output of the AWS stack provision script.
4. All other settings can be left as their defaults
5. Click save changes.
6. Navigate to Site Administration > Plugins > Filters > Manage Filters.
7. Enable the Smart media filter
8. Move the Smart media filter to be higher in priority (before) the Multimedia fitler in the list of filters.

The following sections outline testing of the Smartmedia plugin from the CLI. Testing from the CLI is a good debugging technique, that verifies that the AWS architecture is setup correctly. It does not depend on Moodle or the configured plugin settings.

Once the AWS architecture has been setup using the provisioning script, it can be tested from the command line.

The following test command runs a basic conversion in AWS and returns the result status. To run the script:

1. Change to your Moodle instance application directory. e.g. cd /var/www/moodle
2. Run the following command, replacing <keyid> and <secretkey> With the AWS API Key ID and AWS API Secret Key that you obtained in the AWS Stack Setup.
   Replace <region> with the AWS region from the AWS stack set, e.g. ap-southeast-2.
   Replace <inputbucket> and <outputbucket> with the buckets from the setup.
   Finally enter the path to the file wish to process.:

sudo -u www-data php local/smartmedia/cli/test.php \
--keyid=<keyid> \
--secret=<secretkey> \
--region=<region> \
--input-bucket=<inputbucket> \
--output-bucket=<outputbucket> \
--file='/var/www/moodle/local/smartmedia/tests/fixtures/SampleVideo1mb.mp4'

Note: the user may be different to www-data on your system.

The following sections provide an overview of some additional topics for this plugin and it's associated AWS architecture.

The below image shows the high level architecture the plugin provisioning process sets up in AWS.

2019 Catalyst IT Australia

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

This plugin was developed by Catalyst IT Australia:

https://www.catalyst-au.net/