Launch HN: Tella (YC S20) – Collaborative video editing in the browser

Launch HN: Tella (YC S20) – Collaborative video editing in the browser

Tella (https://www.tella.tv/) is a collaborative online video editor for screen and camera recordings. We're making video creation accessible to people who have no prior editing experience.

Sharing screen and camera recordings is a rapidly growing way for people to communicate at work, especially in technology where the subject matter is often on screens (new features, code, designs). But while people are creating more video for work, it's usually for the convenience of the creator and not the viewer. One-take screen recordings can be long, boring, and difficult to watch. We're trying to change this by letting people produce and edit their recordings so that it's a better experience for viewers.

Michiel and I used to work at a large remote company and this was where we saw the potential of edited video content in the workplace. One of the biggest challenges was keeping business teams up-to-date with product teams. The most effective solution was product teams sharing videos about their work over Slack, which the rest of the organisation watched in their own time. Product teams made videos about new projects, progress updates, launches, user research, and so on.

The most interesting aspect of the approach was that the videos weren't just screen recordings, they were edited and often well-produced videos. The better the production, the better the engagement was. Teams approached the production of these videos in the same way as preparing a slide deck for a presentation.

We loved the format and saw its potential, especially in a remote workplace, but it had some problems. Video editing is time consuming, and working on a video with a teammate takes even longer. Video editing also has a high barrier to entry. Purchasing Screenflow or Final Cut (or other long-format editors) and then learning how to use it prohibits people from trying video as a form of sharing information.

So we set out to build a video editor that focuses on screen and camera recording (where most of the subject matter comes from at work), allows for collaboration (many people work in teams and expect the tools they use to support this), and makes editing straightforward (putting together a video should be as simple as putting together a slide deck).

Our implementation takes a different approach to most editors. We wanted something that was fast, lightweight, and could run in a web browser—appealing to people completely new to video editing. We also wanted to support real-time collaboration. Instead of transcoding all content to a video format, we created our own video player that controls the timing and display of HTML elements. Let's say your video consists of a couple recordings, some text, and some images. Tella plots these different bits of content on a timeline and then plays them back in sequence on a webpage.

The benefit of this is that we can use anything that you can do with HTML, CSS and JS to create a video. We're not bound to ffmpeg or other transcoders to generate our video for us. We take the document the user created and display that in the same way to the viewer (no converting step in between). This means we can stay lightweight and let you update the video whenever you like. There are no “snapshots” stored and the link always shows the source of truth.

The challenge with this is keeping all the content in sync. Using our earlier example: the first recording should play after the text and then the second recording exactly after the first ends. A more complex scenario would be where two videos need to play back at the same time: a screen recording and a camera recording—these need to start and stop at the same moments. This is called “Media Synchronization”, or MediaSync for short (https://www.springer.com/gp/book/9783319658391). At the moment browsers don’t have a lot of stable APIs that can help us, but they are in the works! One notable example is the Timing Object (https://webtiming.github.io/timingobject/) which outlines how you can sync multiple media elements to the same clock. Right now Tella mostly works by manually syncing all video elements on actions like “play” or “seek”. Eventually we want to implement more of the techniques outlined in MediaSync, like slightly changing the speed of out of sync videos to let them catch up.

So far, people have been using Tella to create product demos, team updates, company announcements, sales pitches, investor pitches, and tutorial videos, as well as making video content for blogs and newsletters.

We'd love to hear what you think and answer any questions you might have. Thanks!

Discussion 81 comments · 221 points · 9ranty · 2020-08-14
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.