Note: This is my submission for the Deepgram x DEV hackathon.
Nutshell allows students to quickly summarise their entire video lectures in just a few minutes. Whether it's for a quick revision, catching up on missed classes, or simply a reference for what happened, Nutshell helps students by providing them with the most important parts of the class without them having to watch a second of the recorded video.
And the best part is that it's not just limited to online lectures. Anyone in need of summarising a video-based session can make use of Nutshell and get all the meat. Be it online conferences, meetings, presentations, seminars, or workshops, you just have to upload the recorded video with clear audio, and Nutshell takes care of the rest.
Nutshell leverages state-of-the-art, open-source machine learning & deep learning technologies in order to go from the original video to its short summed-up version. This allows us to provide the user with a concise, accurate and reliable summary.
The basic flow that Nutshell follows to accomplish its goals is as follows:
Step 1. Convert the uploaded video into audio.
Step 2. Transcribe the extracted audio.
Step 3. Run a summarising algorithm on the received transcription.
As is evident, Deepgram comes into play for the second and perhaps the most crucial step in the process, that is, to convert the lecture's audio into text.
To see if it works, we (my friend and I) decided to submit this video to Nutshell. It's a roughly 9 minute long YouTube video explaining the concept of HTTP.
Following was the retrieved summary:
When we mention the Http, that means we need to talk about how the web works, at least having a general idea. And if two computers want to communicate an exchange data, name lay the client and the server usually in form of a request response cycle, those two computers must speak both of them the Http communication protocol. Now before talking about the how and the why, you need to know three important things about the Http protocol. When the connection establishes the client sends a request called an Http message. And because the Http is a connection protocol, the client disconnects from the server waiting for the response. The information in the sections vary dependent on the http message, whether it is a request or a response. First, let's look at request http message. The header specify some information in rules, for example, the host, which is the address of the server to which we are sending the request, which is w w w dot my website dot corn. Let's talk now about a response http message. Also, our clients can send multiple http requests to the server. We've seen that the request response cycle works on the web via http messages.