Show page on Twin Cities Plus
When audio is released for our podcast it should sound like a fluid conversation between two people which lasts ten to twenty minutes. If only Tim and I were so glib. In truth the recording sessions are usually at least thirty minutes and have to be edited down to get rid of parts where we’re not speaking or gathering our thoughts. I’m particularly guilty of hearing a question then waiting while I slowly form an answer in my head.
The next most important thing to edit out is when we misspeak. A podcast wouldn’t be much fun to listen to if the participants said the same thing two or three times to word it just right. Well, we totally do that then I edit out the unusable parts leaving the listener with a single iteration of each sentence.
Lastly, Tim and I can talk at length about this sort of thing, obviously, and sometime we say more than necessary. So I try to cut out the unnecessary parts to leave only an interesting show. My philosophy about podcasts and literature is that it should be like a skirt: long enough to cover everything and short enough to be interesting.
Recording our podcast should also sound like Tim and I are sitting next to one another for a casual conversation. In fact we are several miles apart with completely different recording setups. We connect through Teamspeak 3 for a reliable voice link on a server I host but each side of our conversation is recorded separately. Since we each keep a track of our own voice there are two separate tracks with one voice each. These have to be synchronized then cut up. This part takes the longest even though Garageband makes it pretty simple. This took a couple hours but there is still some editing to be done before the episode is released.
Ad spot for 2 Cyborgs and a Microphone
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, are not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address email@example.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim claim property or assets based on their post.