This is a little nerdy but might be of help to somebody. You can save an animation to webm by integrating the Hype Video Export runtime in your project and sprinkle in some Whammy and HTML2Canvas. This has the limitations of HTML2Canvas and certainly will use a lot of RAM, but it runs on a frame by frame basis, so no frame should be dropped. On the contrary, you can define your framerate, scale and even the HTML element to be recorded.
Notice: Make sure to update HYPE.video.js with the latest version. The file can always be found inside the resources' folder of your Hype-application. The example file uses built using and for the Hype 734 build version.
Another sidenote: The WebM format generated doesn't calculate interframe compression or applies any major optimizations. This is acceptable for my cases, but bad for cases that demand low file size. In such circumstances, you can use a compressor to get the best results.
Press the record button as often as you need and then hit the arrow to download and start a new recording. Make sure to updateHYPE.video.js found under Hype.app/resources (in the package) to match the current version of Hype you are using.
Updated all the dependencies, thank you @h_classen for the hint. The whammy.js dependency especially isn't maintained anymore, but some people are still providing pull request. That fixes some issues. The new whammy.js in the example is taken from Jannchie (on Github). Seems to be fixing a render bug and an overflow beyond 32 seconds.
The Download and example above have been replaced. Furthermore, make sure to always update to the latest HYPE.video.js found in the Hype.app/resources/
it's not about an export from Hype, but building a webversion, that can export video direct from the browser ...
this way you can setup standrad-animations using diffent texts and images ... say for socialteam ...
You can easily use something like WordPress, ACF and Hype Data Magic to create a custom post type that allows to export videos based on dynamic data without the need to export from Hype. You can just run the above encoding in the browser…
… an elementary idea is also to use editable fields approach without a backend. Allowing the user to change test by setting contenteditable and even uploading images locally.