I will not be investing significant effort in the very near future to review and address issues on this repository. However I do want my software to be useable!
If you have an issue that must be resolved for your work, please open a pull request to fix it, and send me a direct email to make sure that I see it. I ignore most messages from GitHub these days.
I'm also happy to help out if you have a question about how to use the library.
My email can be found at the top of this commit.
Keep in mind that I have a full-time job and a personal life as well as other hobbies that have taken priority over open source, so I might not respond immediately. But don't hesitate to follow up after a few days if you think I've missed your email.
Cassette is a zero-config-required media player component library for React. The default responsive UI works great in desktop or mobile web browsers. The flexible core handles the logical complexities of common audio and video player paradigms, while allowing you to implement any UI you can come up with.
See version 1 (also known as react-responsive-audio-player
) here!
@cassette/core
provides React Context-based components which expose an API for consuming and updating media player state@cassette/components
contains some convenient React component building blocks which can be used in media player user interfaces created with@cassette/core
@cassette/player
provides a responsive, zero-config-needed React media player component, implemented with@cassette/core
@cassette/hooks
provides optional React Hooks for consuming media player state
If you wanted to install, for instance, the @cassette/core
and @cassette/player
packages, you would run:
npm install @cassette/core @cassette/player
I do not control, nor do I have any contact with the owner of, the npm package called cassette
(without the @
). If you npm install cassette
, you will be using the wrong library! However it turns out this package is used for managing playlist data. So if you really want to confuse the other devs on your team, you can try using cassette
and @cassette
together!
If you're not using npm and you need production-ready scripts to include in your project, check out the releases. You can also look on unpkg, e.g. here.
What can you build with Cassette? Here are some examples:
A site showcasing creative content, including several podcast series which can be listened to while navigating the rest of the site.
The MediaPlayerControls
UI from the @cassette/player
package can be seen at the bottom of the page, featuring the included play/pause, mute toggle, and media progress controls (with some custom CSS styles applied). PlayerContextProvider
wraps the whole page, and is used on each of the podcast pages where we can select a podcast to play, and see an indication of which podcast is playing currently.
A web app where users can explore curated popular podcasts and schedule queues of podcasts to listen to in the browser.
Instead of using Cassette's default UI, OwlTail's player UI is all custom-built. It relies on a page-level PlayerContextProvider
to provide media data and functionality. The control UI at the bottom of the screen features some controls which don't even exist in the default Cassette UI, like a playback rate control, and buttons for skipping back and forward by 30 second intervals; even though Cassette doesn't provide this UI, its callbacks make it simple to implement this sort of behavior. The progress bar, although featuring custom UI, relies on the MediaProgressBar
helper from the @cassette/components
package, which is designed to work well with both mouse and touch devices.
The UI in the rest of the app is synced with the player via the PlayerContextProvider
wrapper, so that the currently-playing podcast will always display as such when encountered in the queue or a podcast listing.
A React component which is a clone of the Media Player application that shipped with Windows 95. It supports video and audio playback.
Although the UI is totally different than what ships with Cassette, all the media playback internals are handled by Cassette. This means you can configure it the same way you would configure the MediaPlayer
component from @cassette/player
. The website features a video playlist and an audio playlist, and PlayerContextGroup
from @cassette/core
is used to prevent both audio from both pieces of media from playing simultaneously.
A personal site featuring a portfolio of work, including some video game soundtrack pieces, which can be sampled while browsing the rest of the site's content.
This site uses @cassette/player
's PlayPauseButton
and ForwardSkipButton
components, while wrapping the MediaProgressBar
helper from @cassette/components
for a custom progress navigation UI. Because the PlayerContextProvider
wraps the whole page, we can integrate playback controls inline on the music portfolio page, dynamically displaying a media progress control below the description for the currently-selected track.
For building and testing instructions, see CONTRIBUTING.md.
Thanks to BrowserStack for providing their platform free of charge for this project (and many other open source projects). We're using BrowserStack to test compatibility across multiple browsers and platforms.
The standard control components make use of icons from various sources.
The CSS YouTube-style play/pause button and the skip button were authored in part by @benwiley4000, with heavy assistance from this CodePen by @OxyDesign.
The SVG repeat, shuffle, fullscreen and volume icons come from Google's material-design-icons.