<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: FBN Launches: Write-ups&#8230;</title>
	<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/</link>
	<description>Unvarnished news &#038; opinion on cable news</description>
	<pubDate>Sat, 28 Nov 2009 11:27:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Terance</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55309</link>
		<pubDate>Tue, 16 Oct 2007 11:01:54 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55309</guid>
					<description>Ok, ImNotBlue.. thanks!</description>
		<content:encoded><![CDATA[	<p>Ok, ImNotBlue.. thanks!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ImNotBlue</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55294</link>
		<pubDate>Tue, 16 Oct 2007 10:36:52 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55294</guid>
					<description>Terance: I know what you’re saying… and I just keep saying that just because they happened at the same time, it doesn’t mean they’re necessarily connected!  No spinning… just not jumping on the “blame FBN before all the facts are in” bandwagon.  Why are you so insistent on blaming them for the problem, almost gleeful that there might be an issue, and not considering or possibly believing that it could have been a problem somewhere else.

No, I wasn’t watching FBN… to tell the truth, I have no idea if it’s on my cable system (although since I’m just outside of NYC, I can’t imagine it wouldn’t be).  But that’s not really the point.  I’m going on the audio problem you’ve described, and the documents provided by TVN.  I don’t need to hear the problems for myself, necessarily, a good description of them can be just as informative.

So now that we have more information, here’s what I’m thinking.  If the same problem happened, simultaneously on more than one carrier, but not on ALL carriers, the problem points to an issue with their transmission department… not specifically the network.  Where I work, that is more or less my department.  We get our programs (live) from Culver City, California… and then we (me/I) do what we’ve got to do (insert commercials, some graphics, adjust levels, etc) and then it is transmitted out to the various carriers across the country.  So if something happens on my end… a problem with my equipment… it isn’t technically the fault of the network, it’s the transmission dept.

Because apparently some carriers were okay, while others were bad, the problem is probably as simple as a misconfigured audio decoder/transmitter for the particular stations.  Now if it turns out that there was a simultaneous problem across ALL carriers… well then the problem could still have come from the transmission department… or from the FBN studios.

The low audio problem you were describing earlier is likely less connected to FBN at all… and more relative to your particular provider.  There is no way in the transmission department for them to adjust the audio of one particular provider, over the audio of another.  This problem (IMO) was most likely caused by someone on the provider side, having a poorly adjusted receiver or transmitter, sending the information out to subscribers… especially because it seems to be an isolated problem to your particular carrier.

Perhaps I’m a little more sensitive to this because I’ve dealt with these types of problems for quite a while now… making some mistakes myself, and seeing the variety of mistakes others have made.  I’m not saying it’s impossible for FBN to be responsible for these problems (not that problems on the first day, do a whole station make)… I’m just it may not be as easy as it… sounds.  (That was a little pun there.)</description>
		<content:encoded><![CDATA[	<p>Terance: I know what you’re saying… and I just keep saying that just because they happened at the same time, it doesn’t mean they’re necessarily connected!  No spinning… just not jumping on the “blame FBN before all the facts are in” bandwagon.  Why are you so insistent on blaming them for the problem, almost gleeful that there might be an issue, and not considering or possibly believing that it could have been a problem somewhere else.</p>
	<p>No, I wasn’t watching FBN… to tell the truth, I have no idea if it’s on my cable system (although since I’m just outside of NYC, I can’t imagine it wouldn’t be).  But that’s not really the point.  I’m going on the audio problem you’ve described, and the documents provided by TVN.  I don’t need to hear the problems for myself, necessarily, a good description of them can be just as informative.</p>
	<p>So now that we have more information, here’s what I’m thinking.  If the same problem happened, simultaneously on more than one carrier, but not on ALL carriers, the problem points to an issue with their transmission department… not specifically the network.  Where I work, that is more or less my department.  We get our programs (live) from Culver City, California… and then we (me/I) do what we’ve got to do (insert commercials, some graphics, adjust levels, etc) and then it is transmitted out to the various carriers across the country.  So if something happens on my end… a problem with my equipment… it isn’t technically the fault of the network, it’s the transmission dept.</p>
	<p>Because apparently some carriers were okay, while others were bad, the problem is probably as simple as a misconfigured audio decoder/transmitter for the particular stations.  Now if it turns out that there was a simultaneous problem across ALL carriers… well then the problem could still have come from the transmission department… or from the FBN studios.</p>
	<p>The low audio problem you were describing earlier is likely less connected to FBN at all… and more relative to your particular provider.  There is no way in the transmission department for them to adjust the audio of one particular provider, over the audio of another.  This problem (IMO) was most likely caused by someone on the provider side, having a poorly adjusted receiver or transmitter, sending the information out to subscribers… especially because it seems to be an isolated problem to your particular carrier.</p>
	<p>Perhaps I’m a little more sensitive to this because I’ve dealt with these types of problems for quite a while now… making some mistakes myself, and seeing the variety of mistakes others have made.  I’m not saying it’s impossible for FBN to be responsible for these problems (not that problems on the first day, do a whole station make)… I’m just it may not be as easy as it… sounds.  (That was a little pun there.)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Terance</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55265</link>
		<pubDate>Tue, 16 Oct 2007 06:30:29 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55265</guid>
					<description>ImNotBlue, all I'm saying is for it to happen at the same time makes it connected.. btw, why is spinning an audio issue so important to you? And I just *wondered* if you were actually watching FBN at the time.. further since I'm fair as usual, I'll include TVN's newest emails. (btw, disregard the Directv person who says audio was fine.. :&amp;gt;)

Finally would you now like to tell me Verizon's FIOS and NJ Comcast' audio issues coupled with TWC's are on their end too, and not FBN's?!    

&amp;gt;More from emailers:
— &quot;Tell the Fox Business Network spokesperson, Verizon's FIOS TV lost audio from FBN at the same time Time Warner did.&quot;
— &quot;What about the NJ Comcast audio issues during the same time?&quot;
— &quot;The audio for Happy Hour was fine on DirecTV.&quot;</description>
		<content:encoded><![CDATA[	<p>ImNotBlue, all I&#8217;m saying is for it to happen at the same time makes it connected.. btw, why is spinning an audio issue so important to you? And I just *wondered* if you were actually watching FBN at the time.. further since I&#8217;m fair as usual, I&#8217;ll include TVN&#8217;s newest emails. (btw, disregard the Directv person who says audio was fine.. :&gt;)</p>
	<p>Finally would you now like to tell me Verizon&#8217;s FIOS and NJ Comcast&#8217; audio issues coupled with TWC&#8217;s are on their end too, and not FBN&#8217;s?!    </p>
	<p>&gt;More from emailers:<br />
— &#8220;Tell the Fox Business Network spokesperson, Verizon&#8217;s FIOS TV lost audio from FBN at the same time Time Warner did.&#8221;<br />
— &#8220;What about the NJ Comcast audio issues during the same time?&#8221;<br />
— &#8220;The audio for Happy Hour was fine on DirecTV.&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ImNotBlue</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55219</link>
		<pubDate>Mon, 15 Oct 2007 21:37:05 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55219</guid>
					<description>Terance: No, I wasn't watching.  I didn't say I was... in fact, I didn't say anything of the sort.

You are wrong... the problems to NOT necessarily point to it being from the point of origin.  Low audio and complete audio drop out are two different things!  Especially because the audio &quot;came back&quot; at some point... while your audio remained consistent low... it points to it NOT being from FBN.

And what I would like is for all the FBN (and FNC) haters not to manufacture problems or controversies where there are none, just to feed their anti-FNC obsessions!  I may not work there, but I know enough about the industry in which I work that I can speak intelligently about the topic at hand.</description>
		<content:encoded><![CDATA[	<p>Terance: No, I wasn&#8217;t watching.  I didn&#8217;t say I was&#8230; in fact, I didn&#8217;t say anything of the sort.</p>
	<p>You are wrong&#8230; the problems to NOT necessarily point to it being from the point of origin.  Low audio and complete audio drop out are two different things!  Especially because the audio &#8220;came back&#8221; at some point&#8230; while your audio remained consistent low&#8230; it points to it NOT being from FBN.</p>
	<p>And what I would like is for all the FBN (and FNC) haters not to manufacture problems or controversies where there are none, just to feed their anti-FNC obsessions!  I may not work there, but I know enough about the industry in which I work that I can speak intelligently about the topic at hand.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Terance</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55214</link>
		<pubDate>Mon, 15 Oct 2007 21:11:09 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55214</guid>
					<description>I could care less about FBN's glitches.. I just thought it was peculiar that TWC NY viewers had sound issues and I did too.. even though I'm on satellite. With that said, it points to something on FBN's end and I'd like their defenders to stop making excuses. Well, unless of course ya WORK THERE and know the scoop! See, its all about accountability with me, nothing more. </description>
		<content:encoded><![CDATA[	<p>I could care less about FBN&#8217;s glitches.. I just thought it was peculiar that TWC NY viewers had sound issues and I did too.. even though I&#8217;m on satellite. With that said, it points to something on FBN&#8217;s end and I&#8217;d like their defenders to stop making excuses. Well, unless of course ya WORK THERE and know the scoop! See, its all about accountability with me, nothing more.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ChannelXRFR</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55210</link>
		<pubDate>Mon, 15 Oct 2007 20:56:03 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55210</guid>
					<description>Wake me up when the entertainment begins!!!</description>
		<content:encoded><![CDATA[	<p>Wake me up when the entertainment begins!!!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Haile Welde</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55200</link>
		<pubDate>Mon, 15 Oct 2007 20:11:07 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55200</guid>
					<description>DirecTV introduced around 50 new HD channels today, and so it's probable the problem was on their end. But no big deal, glitches always happen in the beginning of anything. 

I agree with Ira, every new channel's had glitches it's had to work out, because of the enormity of the technical apparatus that goes into a channel and cable carrier's operation.</description>
		<content:encoded><![CDATA[	<p>DirecTV introduced around 50 new HD channels today, and so it&#8217;s probable the problem was on their end. But no big deal, glitches always happen in the beginning of anything. </p>
	<p>I agree with Ira, every new channel&#8217;s had glitches it&#8217;s had to work out, because of the enormity of the technical apparatus that goes into a channel and cable carrier&#8217;s operation.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ira</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55198</link>
		<pubDate>Mon, 15 Oct 2007 19:58:17 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55198</guid>
					<description>Terance:  Yesterday I was watching the Raiders - Chargers game on CBS HD and voilla; the sound went completely dead for about 5 minutes even though the normal CBS feed had sound.

It even happens to the experienced networks so don't be so hard on FBN!!


</description>
		<content:encoded><![CDATA[	<p>Terance:  Yesterday I was watching the Raiders - Chargers game on CBS HD and voilla; the sound went completely dead for about 5 minutes even though the normal CBS feed had sound.</p>
	<p>It even happens to the experienced networks so don&#8217;t be so hard on FBN!!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Terance</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55189</link>
		<pubDate>Mon, 15 Oct 2007 19:31:01 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55189</guid>
					<description>It wouldn't be the first time! Btw were YOU watching Happy Hour between 5-6pm? </description>
		<content:encoded><![CDATA[	<p>It wouldn&#8217;t be the first time! Btw were YOU watching Happy Hour between 5-6pm?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ImNotBlue</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55176</link>
		<pubDate>Mon, 15 Oct 2007 19:15:05 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55176</guid>
					<description>Terance was talking about this post:

The Somewhat Silent Happy Hour In NYC

The 5pmET FBN show, Happy Hour has intermittent audio, at least for the New York City cable audience. The problem started at 5:09pmET when the audio went out, but the show went on. The sound came back around 5:27, but went out again around 5:30, and just returned at 5:38. A Fox Business Network spokesperson tells TVNewser the problem is on Time Warner's end.
_____________

However, low sound and no sound are two very different things.  And it is possible for both to happen simultaneously, and yet not be FBN's fault.  So unless you heard the same drop outs that TVN is talking about, it may be a separate issue.

I think you're jumping to conclusions to immediately assume they must be related.</description>
		<content:encoded><![CDATA[	<p>Terance was talking about this post:</p>
	<p>The Somewhat Silent Happy Hour In NYC</p>
	<p>The 5pmET FBN show, Happy Hour has intermittent audio, at least for the New York City cable audience. The problem started at 5:09pmET when the audio went out, but the show went on. The sound came back around 5:27, but went out again around 5:30, and just returned at 5:38. A Fox Business Network spokesperson tells TVNewser the problem is on Time Warner&#8217;s end.<br />
_____________</p>
	<p>However, low sound and no sound are two very different things.  And it is possible for both to happen simultaneously, and yet not be FBN&#8217;s fault.  So unless you heard the same drop outs that TVN is talking about, it may be a separate issue.</p>
	<p>I think you&#8217;re jumping to conclusions to immediately assume they must be related.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Terance</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55154</link>
		<pubDate>Mon, 15 Oct 2007 17:49:55 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55154</guid>
					<description>I read on TVN the sound went off on Happy Hour.. and Fox blames TWC/NY. Ok, I believe ya.. only one problem, I'm on Directv and the sound has been extremely low most of the show.  Can I except Fox will say this is on Directv's end and this is just some major coincidence? Just tell the truth, sheesh.</description>
		<content:encoded><![CDATA[	<p>I read on TVN the sound went off on Happy Hour.. and Fox blames TWC/NY. Ok, I believe ya.. only one problem, I&#8217;m on Directv and the sound has been extremely low most of the show.  Can I except Fox will say this is on Directv&#8217;s end and this is just some major coincidence? Just tell the truth, sheesh.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Me</title>
		<link>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55152</link>
		<pubDate>Mon, 15 Oct 2007 17:35:35 +0100</pubDate>
		<guid>http://insidecable.blogsome.com/2007/10/15/fbn-launches-write-ups/#comment-55152</guid>
					<description>read further and you'll see that fbn wants to entertain as well.  how long until the playboy bunnies show up on cavutos show?</description>
		<content:encoded><![CDATA[	<p>read further and you&#8217;ll see that fbn wants to entertain as well.  how long until the playboy bunnies show up on cavutos show?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
