Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@mux/mux-audio-react
Advanced tools
<MuxAudio/>
is a Mux-flavored React audio component.
If you are familiar with using <audio />
+ Hls.js in your application, then you'll feel right at home with this React component.
If you're using npm
or yarn
, install that way:
yarn add @mux/mux-audio-react
or
npm i @mux/mux-audio-react
Then, import the library into your application with either import
or require
:
import '@mux/mux-audio-react';
or
require('@mux/mux-audio-react');
Without <MuxAudio/>
, if you want to use the browser built-in HTML5 audio element for playback you would have to wire up Hls.js and Mux Data yourself.
<MuxAudio/>
will automatically handle recoverable errors that happen during audio playback. This is particularly handy for live streams that may experience disconnects.
<MuxAudio/>
will use the optimial Hls.js settings for Mux Video so you don't have to worry about that. <MuxAudio/>
will also periodically test new versions of Hls.js and upgrade to known stable versions so you don't have to worry about upgrading to a new version of Hls.js yourself.
Loading this library in the browser will register a custom web component for <mux-audio>
.
Now you are free to use this web component in your HTML, just as you would with the HTML5 <audio>
element.
const MuxAudioExample = () => {
return (
<div>
<h1>Simple MuxAudio Example</h1>
<MuxAudio
style={{ height: '100%', maxWidth: '100%' }}
playbackId="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe"
metadata={{
video_id: 'audio-id-123456',
video_title: 'Super Interesting Audio',
viewer_user_id: 'user-id-bc-789',
}}
streamType="on-demand"
controls
autoPlay
muted
/>
</div>
);
};
playbackId: string
: This is the playback ID for your Mux Asset or Mux Live Stream. The playback-id is the variable you may have used before to construct a .m3u8
hls url like this:https://stream.mux.com/{PLAYBACK_ID}.m3u8
. For more, check out the Mux Docs.envKey: string
: This is the environment key for Mux Data. Note that this is different than your API Key. Get your env key from the "Mux Data" part of your Mux Environments Dashboard. If undefined and you are playing a Mux Video (audio) asset, the environment will be inferred.
metadata: Object
: This is an object for configuring any metadata you'd like to send to Mux Data. For a detailed discussion of the available metadata fields and what they represent, check out the Mux Data docs. A few high priority keys that you'll likely want to set are:
video_id: string
: Your internal ID for the audio.video_title: string
: Title of the audio player (e.g.: 'Awesome Show: Pilot')viewer_user_id: string
: An ID representing the viewer who is watching the stream. Use this to look up video views for an individual viewer. If no value is specified, a unique ID will be generated by the SDK. Note: You should not use any value that is personally identifiable on its own (such as email address, username, etc). Instead, you should supply an anonymized viewer ID which you have stored within your own system.streamType: string
: Enum value: one of "on-demand"
, "live"
(HLS live stream), "ll-live"
(low latency live). Not strictly required, but preferred so that <MuxAudio/>
can make optimizations based on the type of stream.startTime: number (seconds)
: Set this to start playback of your media at some time other than 0.In addition, any props that you would use on a <audio>
element like poster
, controls
, muted
and autoPlay
are available and should work the same as they do when using a audio element in react. One sidenote about autoPlay
though -- read this to understand why that might not always work as expected.
By default <MuxAudio/>
will try to use native playback via the underlying <audio/>
tag whenever possible. However, it can also instead use an in-code player as long as the browser supports Media Source Extensions. This includes MSE in Mac OS Safari.
If you prefer to use the in-code MSE-based engine (currently hls.js) whenever possible, then simply set the preferPlayback
prop to mse
.
<MuxAudio
playback-id="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe"
metadata={{
video_id: 'audio-id-123456',
video_title: 'Super Interesting Audio',
viewer_user_id: 'user-id-bc-789',
}}
preferPlayback="mse"
controls
/>
By default <MuxAudio/>
will try to figure out the type of media you're trying to play (for example, an HLS/m3u8 media source, an mp4, etc.) based the extension of the file from the src
attribute's url. This allows <MuxAudio/>
to determine whether it can/should use an in-code player or native playback. By way of example, the code below has an identifiable "mp4" extension, so <MuxAudio/>
will rely on native playback via the underlying <audio/>
tag.
<MuxAudio
src="https://stream.mux.com/DS00Spx1CV902MCtPj5WknGlR102V5HFkDe/high.mp4"
metadata={{
video_id: 'audio-id-123456',
video_title: 'Super Interesting Audio',
viewer_user_id: 'user-id-bc-789',
}}
controls
/>
Sometimes, however, your src
URL may not have an identifiable extension. In these cases, we recommend relying on the type
attribute, similar to the <source/>
tag's type attribute. Below is an example of explicitly declaring the MIME type for an HLS/m3u8 media source:
<MuxAudio
src="https://stream.notmux.com/path/to/an/hls/source/playlist"
type="application/vnd.apple.mpegurl"
metadata={{
video_id: 'video-id-123456',
video_title: 'Super Interesting Video',
viewer_user_id: 'user-id-bc-789',
}}
controls
/>
Or, for convenience, we also support the shorthand type="hls
:
<MuxAudio
src="https://stream.notmux.com/path/to/an/hls/source/playlist"
type="hls"
metadata={{
video_id: 'audio-id-123456',
video_title: 'Super Interesting Audio',
viewer_user_id: 'user-id-bc-789',
}}
controls
/>
Mux supports a number of query parameters on HLS playback URLs. Most commonly the token=
param is used for signed URLs.
In order to use token=
-- or any other query params, pass them through with the playbackId
prop:
playbackId="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe?token=jwt-signed-token"
<MuxAudio/>
with TypeScript
?Yes! In fact, @mux-element/mux-audio-react
is written entirely in TypeScript
and provides a definitions file automatically (no additional installs needed).
No, you do not. The way Mux delivers HLS is compliant with the HLS spec. Any audio player that supports HLS will work with Mux Video.
You sure can! Instead of passing in playbackId=""
prop, pass in src=""
with an HLS url. You can still use envKey=""
to get all the features of Mux Data with your non-Mux audio.
FAQs
A custom mux audio element for React that Just Works™
We found that @mux/mux-audio-react demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.