A component for scroll-based (or other externally controlled) playback. See /demos
for full example usages.
Add html container to your page:
<div id="scrolly-video"></div>
Require javascript in your page and create the object (before </body>
):
<script src="https://cdn.jsdelivr.net/npm/scrolly-video@latest/dist/scrolly-video.js"></script>
<script type="text/javascript">
new ScrollyVideo({
scrollyVideoContainer: "scrolly-video",
src: "https://scrollyvideo.js.org/goldengate.mp4"
});
</script>
You can replace @latest
with specific version, example @0.0.2
.
Install npm module with npm install scrolly-video --save
:
Import component in your application:
import ScrollyVideo from 'scrolly-video/dist/ScrollyVideo.jsx';
Add the component where you need it:
<ScrollyVideo src="https://scrollyvideo.js.org/goldengate.mp4" />
Install npm module with npm install scrolly-video --save
:
Import component in your application:
import ScrollyVideo from 'scrolly-video/dist/ScrollyVideo.svelte';
Add the ScrollyVideo component to your application:
<ScrollyVideo src="https://scrollyvideo.js.org/goldengate.mp4" />
Install npm module with npm install scrolly-video --save
:
Import module in your src/App.vue
and config:
import ScrollyVideo from 'scrolly-video/dist/ScrollyVideo.vue';
Add html code to your html component:
<ScrollyVideo src="https://scrollyvideo.js.org/goldengate.mp4" />
Parameter | Description | Values | Default |
---|---|---|---|
src | The URL of the video (required) | URL | |
scrollyVideoContainer | The DOM element of the container, only used for plain js | String / Element | |
transitionSpeed | Sets the maximum playbackRate for this video | Number | 8 |
frameThreshold | When to stop the video animation, in seconds | Number | 0.1 |
cover | Forces the video to cover in it's container | Boolean | true |
sticky | Whether the video should have position: sticky |
Boolean | true |
full | Whether the video should take up the entire viewport | Boolean | true |
trackScroll | Whether this object should automatically respond to scroll | Boolean | true |
useWebCodecs | Whether the library should use the webcodecs method, see below | Boolean | true |
videoPercentage | Manually specify the position of the video between 0..1, only used for react, vue, and svelte components | Number | |
debug | Whether to log debug information | Boolean | false |
Additionally, to set currentTime manually:
setCurrentTimePercent (setPercentage | Number
): A number between 0 and 1 that specifies the percentage position of the video.
To make this library perform optimally in all browsers, three different approaches are taken to animating the video.
Using the new WebCodecs API we are able to get all frames in the video and have them ready to draw to a canvas. This method is the most performant, but has two drawbacks: first, depending on the device and the size of the video, using the WebCodecs API will take some time to process all the frames, so the animation will not be available immediately upon page load. Secondly, the WebCoedecs API is currently only available on Chrome, and the WebCodecs polyfill does not work for this application.
If WebCodecs is not supported by the browser or has not finished processing all frames, it falls back to method 2:
This method simply embeds the video with an HTML <video>
tag, and it plays the video when the video needs to be animated. To adjust to the scroll speed, this method modulates the playbackRate
attribute on the video in order to dynamically mimic a faster or slower scroll speed. This method is extremely smooth when the scroll direction is moving the video forward, but unfortunately does not work in reverse because playbackRate
cannot be a negative value.
Thus, if the video needs to be animated backwards, this library falls back to method 3.
This method is the way that scrollytelling videos have traditionally been done, using an HTML <video>
tag and skipping directly to frames using currentTime. However, this method requires the video to be encoded at keyframe = 1, which causes the video to be a lot larger or the quality to drop. Unfortunately, this is the only option for scenarios where methods 1 and 2 are not supported, or on mobile safari browsers where somehow this method performs better than method 2. Thus, to achieve maximum performance under all circumstances, it is still recommended to encode videos with keyframe = 1, if possible.
Created by: Daniel Kao