I wish to state up front that I really like Squadcast and I especially like their owners and staff – VERY good people. And my opinion is that Squadcast is currently the best available option for virtual recording sessions for podcasts. I use Squadcast regularly and pay for it monthly.
The purpose of this post is to SAVE YOU from major production headaches by teaching you how to avoid a nonsensical and annoying “feature” of Squadcast. And if this “feature” hasn’t yet bitten you in the butt you may not think this “feature” is a big deal, and you may also think I’m making a mountain out of a molehill, but when this “feature” DOES bite you in the butt you will fully understand how nonsensical it is.
OK, so…
Beware of Squadcast if a participant drops off the session because THE MOMENT THEY DROP OFF Squadcast STOPS RECORDING EVERYONE!!!
Really?!?!?!
What you HAVE to do EVERY TIME ANYONE drops off is:
- STOP the conversation dead in its tracks, even if the person who dropped off was just listening to the others talk
- WAIT until the dropped person reconnects
- PRESS RECORD AGAIN
Really?!?!?!
In my professional opinion I think this “feature” is terrible because Squadcast is a tool that RECORDS PEOPLE, so for it to STOP recording at ANY time is completely unacceptable.
Now, Squadcast will tell you that they record backups of all sessions so that the “missing audio” can be recovered, which is usually true, but the quality of that “recovered” audio is significantly worse than the normal Squadcast quality, and it may contain glitches because it is recorded AFTER the audio has travelled over the internet, plus Squadcast admits that it MAY be out of sync with the other tracks. Plus, you will have to do SIGNIFICANTLY more post-production work to piece together and sync-up various files, etc. Wonderful.
I hope Squadcast will fix this ASAP, but their management has given me several irrelevant/weird reasons why they are going to stick with their current practice of stopping recording when someone drops off. In their defense, I suspect fixing this “feature” is not simple or easy, so therefor Squadcast may be taking the easier/cheaper route of not correcting this, which is kind of understandable in a business sense, but very unfortunate for Squadcast users.
Again, I really like Squadcast and I especially like their owners and staff – VERY good people. And my opinion is that Squadcast is currently the best available option for virtual recording sessions. For now, I will continue to use and pay for Squadcast.
But this is pure madness.
What do you think?
Want to receive the Daily Goody in your email, daily or weekly? Subscribe free here.
And please keep in mind, the Daily Goody is only a tiny little tip, fact or lesson everyday. Please don’t expect any of these posts to be long, earth-shattering masterpieces that instantly answer every single question you can think of and completely transform you into a world class podcast engineer. “Little by little, a little becomes a lot.”
.
3 Responses
This must be fairly new as I’m sure I have dropped out of a Squadcast session after making sure the host and guest were talking and sounding okay.
I’ve had issues where the browser has cached the username and password and so if two people Use the same account details – me and the host – enter at the same time, one gets kicked off. This led to an interesting experience for a guest when the host and I appeared like the figures on a German clock, one in, one out – repeat.
We fixed it my using Chrome for the session owner and Firefox for the co-host. If the Host ran the session by herself, she used Chrome, if with me running, she used Firefox.
Fortunately, I haven’t run into this “feature” yet, but I agree with you, Chris. I have to stick with Squadcast for now because I paid for a full year up front, but I’m starting to regret that for several reasons. The competition is nipping at their heels, and with such “features” as this, they’ll soon be losing out, I fear.