Not just you, it sounds like it was recorded over Skype and the connection was in-and-out. I understand the need to use something like Skype to have a discussion between people in different places, but don't see why each audio stream couldn't be recorded locally....
For this one we tried using Google Hangouts on Air with server recording, which muxes everyone automatically but can depend on internet connection bandwidth. Previously we used Skype and had each person record it locally, but ultimately we lost 10% of podcasts recorded due to save errors (if one person cuts, the whole thing is essentially lost, which happened 3-4 times since we started) and editing took a lot longer with the different streams. We're looking into how to improve our podcast recording, and Hangouts on Air was a recommended solution, although I still need to get to grips with the settings, as it seems the audio only records worse audio than the video/studio option.
Strange, you would think if they already have the systems prepared to mux everything together that they could just cache the recordings locally before sending them to the server with a certain amount of buffer - that would give you the best of both worlds, not sure why the recording still has to occur at the server level.
My advice would be to do both a local recording and a muxed server side recording. That way even if you lose one of the high quality recordings, you still have the lower quality one that can be spliced in ass appropriate.
Also having a server side recording helps in editing as it could be used to set the timing of the individual recording tracks.
As Ian mentioned, we tried out Google Hangouts this time in an effort to speed up the editing process. It's a work in progress though so we need to tweak a few things.
When you say poor audio though, would you say it was Ian, or me, or both?
I think it was both, but Ian's was somewhat worse. I use WebEx at work and it seems to work pretty well - the cheapest plan includes meeting recordings and isn't outrageously expensive.
I'm pretty sure I have a lot better bandwidth than Ian is why I was asking. We want to do more of them that's why we're trying to make it a bit easier to produce. Thanks for the feedback!
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
12 Comments
Back to Article
Gich - Thursday, May 14, 2015 - link
Just me or does audio... sucks?maecenas - Thursday, May 14, 2015 - link
Not just you, it sounds like it was recorded over Skype and the connection was in-and-out. I understand the need to use something like Skype to have a discussion between people in different places, but don't see why each audio stream couldn't be recorded locally....Ian Cutress - Thursday, May 14, 2015 - link
For this one we tried using Google Hangouts on Air with server recording, which muxes everyone automatically but can depend on internet connection bandwidth. Previously we used Skype and had each person record it locally, but ultimately we lost 10% of podcasts recorded due to save errors (if one person cuts, the whole thing is essentially lost, which happened 3-4 times since we started) and editing took a lot longer with the different streams. We're looking into how to improve our podcast recording, and Hangouts on Air was a recommended solution, although I still need to get to grips with the settings, as it seems the audio only records worse audio than the video/studio option.Any thoughts and suggestions are appreciated!
Ian Cutress - Thursday, May 14, 2015 - link
*the "audio only" option records worse audio (~35 kbps) than the "video" or "studio" options.maecenas - Thursday, May 14, 2015 - link
Strange, you would think if they already have the systems prepared to mux everything together that they could just cache the recordings locally before sending them to the server with a certain amount of buffer - that would give you the best of both worlds, not sure why the recording still has to occur at the server level.Kevin G - Thursday, May 14, 2015 - link
My advice would be to do both a local recording and a muxed server side recording. That way even if you lose one of the high quality recordings, you still have the lower quality one that can be spliced in ass appropriate.Also having a server side recording helps in editing as it could be used to set the timing of the individual recording tracks.
SoC-IT2ME - Thursday, May 14, 2015 - link
Poor audio again?...after the abomination which was the last podcast's audio quality.Please fix this in the next podcast.
Brett Howse - Friday, May 15, 2015 - link
As Ian mentioned, we tried out Google Hangouts this time in an effort to speed up the editing process. It's a work in progress though so we need to tweak a few things.When you say poor audio though, would you say it was Ian, or me, or both?
maecenas - Saturday, May 16, 2015 - link
I think it was both, but Ian's was somewhat worse. I use WebEx at work and it seems to work pretty well - the cheapest plan includes meeting recordings and isn't outrageously expensive.SoC-IT2ME - Sunday, May 17, 2015 - link
I listened to the podcast last night and I have to say it was a good show. Brett, your presentation on the whole was great to listen to, keep it up.Quality wise it was more Ian than yours that was a bit low Q. The compression can be heard with ease.
SoC-IT2ME - Sunday, May 17, 2015 - link
Also Please keep the podcasts coming. At least 2 per month would be awesome.Brett Howse - Sunday, May 17, 2015 - link
I'm pretty sure I have a lot better bandwidth than Ian is why I was asking. We want to do more of them that's why we're trying to make it a bit easier to produce. Thanks for the feedback!