Video On-Demand (VOD) files are for playing back uploaded videos or live stream recordings. Mux calls these Assets. These are most like regular YouTube videos.
There are three ways of creating an Asset:
- Live stream recording.
- Video file upload.
- Clips created from other Assets.
- There is no limit to the file size, number of uploads or time spent uploading.
- Audio-only uploads are supported.
- Each new asset is billed ($) per minute of time.
Uploads are sent directly to the cloud physically close to your location making transfers fast and avoiding congestion to your web server. Video files are usually available very quickly, usually seconds, after upload with Mux's Just-In-Time delivery. Some types of files, the more unique or professional codecs, may need additional encoding time. See Mux's Documentation on how to reduce those times.
What makes Mux different than other services like YouTube is that only the streaming link is provided, and nearly any player can be used. With Mux you have the ability to customize what player is used, how it looks, and how it behaves. The advantage is much more flexibility and customization, but does require some additional work in setting up the player. Mux comes with a simple EE tag that embeds a simple player to get started, and includes a number of examples of players.
Mux also has a brand new shinny player that uses native web components.
IDs & Playback
Each Asset has a unique Mux ID to identify the video, and to get metadata such as duration, and resolution. Playback IDs are used in a URL to play the video, or get images. With separate IDs, this means the video's playback links can be freely changed for security without needing to re-upload the video.
MuxEE supports signed playback as of v2. This is great for subscriptions or protected video content from being distributed outside your website. Each link has an expiration time, default is 24 hours, and can be locked to a domain. This also includes all image links.
This option is currently a global setting for all video, both assets and live streams, and can be changed at any time.
Mux's Guide on Assets: https://docs.mux.com/guides/video/stream-video-files
Each playback link will be to an Http Live Streaming (HLS) file. HLS is a protocol for streaming video. The video is cut into usually 3 second chunks and linked in a file for the player to download when needed. HLS can also include video quality levels for the player to jump to when bandwidth is low or for a small screen size.
Several examples are included as templates with the module. We can help with basic implementations, but advanced player needs would best be handed by the player's support teams.
Mux Guide on Playback: https://docs.mux.com/guides/video/play-your-videos
When getting started, you will need test uploads. So Mux provides a ‘test’ parameter when creating Assets. This includes all Assets (uploads, clips, live stream recordings) as well as Live Streams. Tests are FREE and incur no per-minute charge.
When first installing the add-on, all media is set as tests in the MuxEE Settings. Tests are a global setting for assets, and a separate global setting for live streams.
About Test Assets:
- Clipped to 10 seconds, if pre-recorded
- Limited to 5 minutes, if live streamed [then disabled]
- Automatically deleted after 24 hours [sometimes]
- Test assets can not be switched to normal assets at a later time.
The blog post on Tests https://mux.com/blog/new-test-mux-video-features-for-free/
Creating Your First Upload - The Super Fast Way
The shortest possible way to upload a video.
Creating Your First Upload - In Entries
Normally you would want to upload videos directly in an entry. The Assets Fieldtype is designed to help with this.
Clips and Live Stream Recordings are covered in their own guides.
To show videos in templates, head to the template guide.
- Content editors should try to upload videos to entries, and avoid uploading through the add-on's administrative page as much as possible. Copying IDs from the gallery to entries is intended to be for occasional content adjustments, not as a primary workflow.
- Use additional EE fields to add video metadata. Videos themselves have a title, upload date and user, but will not have additional fields to enter more information. It may be a better for your content to create a channel specifically for video and its related metadata that includes a Mux Asset field, and then use Relationships to link the video to another entry, like a blog.