<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: High bandwidth/quality phone codecs and aural cues in radio programs</title>
	<atom:link href="http://www.notes.xythian.net/2006/02/24/high-bandwidthquality-phone-codecs-and-aural-cues-in-radio-programs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.notes.xythian.net/2006/02/24/high-bandwidthquality-phone-codecs-and-aural-cues-in-radio-programs/</link>
	<description>Links, technical notes, whatnot.</description>
	<pubDate>Fri, 05 Sep 2008 19:44:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Lars</title>
		<link>http://www.notes.xythian.net/2006/02/24/high-bandwidthquality-phone-codecs-and-aural-cues-in-radio-programs/#comment-1844</link>
		<dc:creator>Lars</dc:creator>
		<pubDate>Fri, 24 Feb 2006 23:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.notes.xythian.net/2006/02/24/high-bandwidthquality-phone-codecs-and-aural-cues-in-radio-programs/#comment-1844</guid>
		<description>I'm sure they could apply a sound effect to designate the speaker as caller if that was deemed desireable.  It would be pretty easy to add some low level white noise without cutting the quality too heavily.  

I don't see this issue as a problem.  Hosts are easy to recognize by how they talk.   I could characterize it as way moreauthoritive and confident than a guest or caller.  Also the host usually talks the most unless they are moderating, which is a clue who is in charge in itself.
Distinguishing between in-studio guests and and guests dialing isn't much of an issue.  Listening to a scheduled guest call in at better quality is a all around win and I think by the pacing of the converstion I could infer if they are in studio or not.  Converstions aren't usually as quick because the people talking don't get the benefit of body language and there is also the latency to deal with which will make the conversation not as crisp as an in person dialogue.  
A random public caller generally won't be given sufficient airtime to confuse me into thinking he/she is running the program or in studio.  A random public caller rarely is engaged in conversation or debate these days.  Just allowed to lay praise and a point, thats about it before the host hangs up.

Overall, I can't wait.  Good sound quality will make for better radio.  It's probably not going to improve the actual content much though.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure they could apply a sound effect to designate the speaker as caller if that was deemed desireable.  It would be pretty easy to add some low level white noise without cutting the quality too heavily.  </p>
<p>I don&#8217;t see this issue as a problem.  Hosts are easy to recognize by how they talk.   I could characterize it as way moreauthoritive and confident than a guest or caller.  Also the host usually talks the most unless they are moderating, which is a clue who is in charge in itself.<br />
Distinguishing between in-studio guests and and guests dialing isn&#8217;t much of an issue.  Listening to a scheduled guest call in at better quality is a all around win and I think by the pacing of the converstion I could infer if they are in studio or not.  Converstions aren&#8217;t usually as quick because the people talking don&#8217;t get the benefit of body language and there is also the latency to deal with which will make the conversation not as crisp as an in person dialogue.<br />
A random public caller generally won&#8217;t be given sufficient airtime to confuse me into thinking he/she is running the program or in studio.  A random public caller rarely is engaged in conversation or debate these days.  Just allowed to lay praise and a point, thats about it before the host hangs up.</p>
<p>Overall, I can&#8217;t wait.  Good sound quality will make for better radio.  It&#8217;s probably not going to improve the actual content much though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
