We built Welder for ourselves as we are a small product team that was forced to go remote and wanted to produce content.
We used Zoom, but the quality was.. Well, S*t.
It’s a super easy way to record full quality recordings remotely as each participant is doing local recording which is progressively uploaded to our servers so as soon as the call ends, it’s ready for editing.
We’ve validated the product in 2 weeks by doing LP and running YT ads. Built MVP in 1 month and found out no one used it as we did a mistake by not validating if Electron app is ok for people to download.
Lessons learned, Welder is now browsers based. We decided to stay bootstrap and right now we are trying to find a pivot from a tool that “Allows you to record an interview in HQ remotely” to a tool for a team like us to produce meaningful content with ease from start to end.
I would love to hear your feedback either about the tool or about your content creation process. As we are doing extensive research on the topic of how startups and product teams produce content.
P.S. We have now quite a lot of experience with running online video service in production for some time, so if you have any questions regarding this topic, let us know we will be more than happy to answer.
It confuses me that you used a video with that much high-pitched background noise in the audio to showcase your tool - in the end, both version seem a bit low-quality because of the noisy audio.
It's true! This was done with an early prototype of the Welder so the quality is not the best. We should've reshot it already, but we love the vibe of it, haha.
> I was wondering where this product was, and/or why some of the podcasts I listen to don't use something like this.
These are called "multi-enders", and lots of podcasts do them. There are many[1] tools for this which are focused specifically on podcasters.
Additionally, it's straightforward to do it manually as well. (Tip: Have participants on all ends do a "1-2-3 <CLAP>" to make it easy to align the audio during production. Do this at the beginning and end to account for digital clock drift.)
Most of the higher production value podcasts I listen to with remote hosts/guests do this, albeit manually (ie record locally with something like Audacity, sync on a click/clap, recorded live call as a backup). This feels like a nice improvement to streamline an otherwise cumbersome process.
We store unuploaded chunks of the video in IndexDB in a browser. Btw if plan to do something similar beware of the fact that storing a lot of blob references in IndexDB can cause some wired issues in Chrome a some blobs can get corrupted. Our workaround is to store it as byte arrays.
Video is saved as a binary blob in some kind of storage. In our case that would be IndexedDB. But since the data is uploaded in parallel with the call there is only few hundred MB used at any give moment.
Generally browsers will let you store a few GB of data (depending on the user free space) if your really wanted to but it's not recommended since they can delete it any time.
Congrats on the release and the excellent product! I work on a Remote Desktop app and one of my customers used Remote Desktop + your tool to collaborate live with his partner.
Would you be able to talk a little more about your Webrtc stack? Do you use SFUs in your stack?
Thank you! We use Twilio for our WebRTC infrastructure with VP8 simulcast setup so we do use SFU but only through Twilio. We were considering how to get rid of Twilio and quite extensively researching what would it mean to run our own WebRTC infra as Twilio costs are pretty high (sometimes up to 1/4 of our revenue). But operating multiple servers around the word to act as SFUs or creating them on demand in e.g. GCP and paying the cloud tax in form of extremely expensive egress costs doesn’t seem to be the right solution either. Other service providers have very similar pricing, that's why we will stay with Twilio for now.
Thank you for the info! Incase it helps, we’ve been running our own WebRTC infrastructure (TURN servers only at the moment) for the last 5 years. It’s globally distributed, fault tolerant and allows us to mitigate the high costs. We’re doing 10s of TB of traffic at a fraction of the cost. Would be happy to discuss our infra incase it helps.
That would be super helpful to us. Can you please hit me at marek@getwelder.com? We could schedule a call or just text chat about it if that's ok for you.
Audio is recorded in HQ too, thanks for the feedback, seems like it's not clear enough.
About the phone on linux - it will work if there is any solution out there that allows you to use your phone as a webcam on linux, Welder will pick that up.
It's actually quite simple. In a addition to a web call we record a separate high quality tracks for both audio and video locally.
The challenge was doing all of this in browser since the APIs are not really consistent + there are a lot of weird bugs and issues with both MediaRecorder API and IndexedDB.
We spend quite a bit of time setting up logging for client app. Since most of these weird issues are very hard to reproduce. (For example Chrome randomly purging binary blobs after storing them in IndexedDB)
We built Welder for ourselves as we are a small product team that was forced to go remote and wanted to produce content.
We used Zoom, but the quality was.. Well, S*t.
It’s a super easy way to record full quality recordings remotely as each participant is doing local recording which is progressively uploaded to our servers so as soon as the call ends, it’s ready for editing.
We’ve validated the product in 2 weeks by doing LP and running YT ads. Built MVP in 1 month and found out no one used it as we did a mistake by not validating if Electron app is ok for people to download.
Lessons learned, Welder is now browsers based. We decided to stay bootstrap and right now we are trying to find a pivot from a tool that “Allows you to record an interview in HQ remotely” to a tool for a team like us to produce meaningful content with ease from start to end.
I would love to hear your feedback either about the tool or about your content creation process. As we are doing extensive research on the topic of how startups and product teams produce content.
P.S. We have now quite a lot of experience with running online video service in production for some time, so if you have any questions regarding this topic, let us know we will be more than happy to answer.