As we incrementally improve our GUI video editor I thought I’d create this thread to keep everyone updated on what we are working on now, what we are working on next and all the things we know don’t yet work.
Our goal is to eventually reach feature parity with the features available in the API itself. This will be a huge task, especially considering many features are not supported in the browser such as QuickTime mov support or luma mattes. Or recreating and animating all the transitions and motion effects. But we will find a way to recreate or represent these types of features as we go.
We’ll focus on the most important/impactful features first that tackle some of the biggest blockers - like previewing the position and size of elements on the screen.
Bear in mind that the preview and rendered result might not be 100% the same so always do a test render and consider that the source of truth, not what you see in the editor preview.
We welcome all feedback of course. Let us know what your most important features/blockers are and that will help guide our efforts.
Here’s a breakdown of the key features and parity with the API.
Key
Status
Done to an acceptable / usable standard
Not done yet
Under construction / in progress
Progress
Feature
Status
Timeline
Tracks
Tracks ordering JSON
Soundtrack
Fonts
Background
Clips
Start
Length
Fit
Scale
Position
Offset
Opacity
Transition
Effect
Filter
Transformation
Assets
Video asset
Image Asset
HTML Asset
Video Volume
Audio Asset
Title Asset (deprecate)
Luma Asset
Image and Video Crop
HTML styling of multiple tags and child tags
Transitions
Todo
Output
Rotate
Skew
Flip
Format
Resolution
Aspect Ratio
Custom Size
Range
scaleTo
mp3 format
Poster image
Thumbnail image
GUI Features
Preview area
Editor panels
Drag and drop
Click/drag to resize
Playback controls
Scrubber
Timeline view
Timeline view editing (drag and drop)
Upload support (instead of URL only)
Order tracks and clips via GUI
Known issues
Only first HTML element is supported in HTML assets - i.e. <p>Hello World</p>. <p>Hello</p><p>World</p> or <p>Hello <span>World</span></p> will not display correctly.
CSS line height in preview does not match rendered video
Drag and drop only works correctly when anchor is set to center.
Hi, I’m trying to create a video for testing, but after yesterday’s update Luma Mattes stopped working. I add 2 images and transition to them using Luma Mattes, but if I do it in the template editor in the visual part, the tracks can’t be expanded and I can’t see the layer order in it, I switch to JSON Viewer, I fix the code and submit its on render and there is no transition if i switch back to visual editor all my layers are flipped to different tracks and i dont know how to make this work
We have rolled out a fix that will let you edit the JSON and switching to the UI won’t affect it in any way. Lumas can only be modified in JSON for the time being though.
Hey there!
Is there a way to embed such a preview into our dashboard app so our customer can see a preview of their video before I send the json to your API to let the video finally render?
Best, Carsten
This is on our roadmap and something we are investigating. Right now we don’t have a date when we would deliver this.
For now a few options are to render a preview that is scaled down using the output scaleTo setting. You can also render a segment of a video using the output range settings or you could render key frames within the video by creating images at key points in the video using the range start and format jpg.
It’s not as good as a real time preview but it may quickly help you users get an idea of how their video will look.
Only first HTML element is supported in HTML assets - i.e.