Once you are done recording, there are still a few steps required to get your ractive polished and cross-compatible. We call this the mastering or post-processing phase.
At the end we provide a checklist to go through when deploying a ractive to production.
It can be convenient to record several audio segments separately. However, due to the Web Autoplay Policy, you need to join them into a single audio file when you are finished. See https://trac.ffmpeg.org/wiki/Concatenate#demuxer for how to do this with ffmpeg.
The audio file produced by the browser will not have the correct metadata for seeking. To fix it:
It is necessary to provide audio in both webm and mp4 format. To convert the webm recording:
How to do noise reduction using ffmpeg and sox (skip steps 1 and 5)
You may want a "static" (traditional mp4/webm) version of your ractive so that you can upload it to Facebook/YouTube/Twitter (and then link to the interactive version). You can make these with the
rp-master render command:
Your ractive will be a lot easier to navigate if you have thumbnail previews on the scrubber bar. These can be generated with the
rp-master thumbs command:
These are then passed to the thumbs prop of Player.
- Remove the
- Ensure fat-fingers etc. for mobile
- Make sure that mouseUp events are appropriately intercepted.
- Join audio audio files into a single file.
- Fix webm file produced by browser.
- Ensure that audio files are available as both webm and mp4.
- Generate thumbnails and add highlights.
- Make sure there is CSS to load custom fonts etc.
- Make sure MEDIA_URL is set to production assets host
- Compress CSS
- Make static recordings for social media/discoverability