View Full Version : Audio (Dolby AC3) problems on FOX?
zorinlynx 10-16-09, 08:34 AM In the last few weeks I've been having problems watching FOX because the audio keeps stuttering constantly. None of the other networks have this problem.
It happens during Fringe, but I know it's not just Fringe because it happens during ads too. I also know it's not just my station, as a torrent I downloaded of the show afterwards has the SAME problem and it was captured from FOX25 in Boston! I'm watching over the air, not cable or satellite.
Is anyone else having issues? It only happens if I listen to the show in 5.1 surround through my receiver; the TV audio plays just fine. Also, if I switch my receiver to "Virtual", instead of DD, it plays fine even though it's still playing the same bitstream.
This is incredibly frustrating as I really enjoy Fringe and hate having to switch to TV audio to enjoy it. I'm thinking it might be an issue with the receiver, but if so, why do none of the other networks exhibit the problem? "Flash Forward" on ABC plays perfectly. Also, when the audio from the receiver mutes and stutters, I can still hear it playing at a very low volume between the bursts of normal volume audio. something is causing the receiver to nearly mute the sound near constantly.
The receiver is a Denon AVR-S1802 connected to the television via toslink.
That sounds like the audio problems I've been having with Fox on D*. The first 45 minutes of Hell's Kitchen last week were very nearly unwatchable because it was so bad. Then it pretty much cleared up. That was the worst instance, by far, but it has been happening for the last two weeks or so.
petergaryr 10-16-09, 06:07 PM Wonder why it is happening in some places, but not others. No problems here in Jacksonville using D* through a Denon 2808 receiver.
zorinlynx 10-16-09, 07:48 PM That sounds like the audio problems I've been having with Fox on D*. The first 45 minutes of Hell's Kitchen last week were very nearly unwatchable because it was so bad. Then it pretty much cleared up. That was the worst instance, by far, but it has been happening for the last two weeks or so.
Does anyone have a contact at FOX we could complain to about this? A contact who actually has a clue? I doubt the typical call-in lines or email addresses will reach the right people.
We need to reach a geek who actually runs the show...
Wonder why it is happening in some places, but not others. No problems here in Jacksonville using D* through a Denon 2808 receiver.
same station and no problems
zorinlynx 10-17-09, 01:45 PM Wonder why it is happening in some places, but not others. No problems here in Jacksonville using D* through a Denon 2808 receiver.
I'm starting to suspect that the bitstream is "damaged" in some way that affects some receivers, but not others.
Even when the audio is cut out I can still hear it at a very low level, which suggests the receiver's "safety mute" has been engaged, to protect the speakers from corrupted AC3 packets.
So something is making the receiver think the packets are corrupted when they're not. Bleah.
Same thing here with DTV through a Onkyo TX-SR805 via HDMI on FOX 28 in Columbus Ohio. I watch little on fox, so I just noticed it watching the ALCS last night and tonight. I tried turning off Dolby Digital on the DTV receiver, no luck. If anyone finds anything that works, I hope they post it here. It really sucks, this is the only time of year I can get into baseball.
-John
zorinlynx 10-19-09, 10:53 AM More details: Only network audio from FOX is affected. Ads played locally (by WSVN-DT 7.1) are not affected and sound fine. So the problem is definitely on the FOX end.
Note that I'm having problems OTA, with an antenna, NOT cable or DirecTV. This is further evidence that the issues are directly caused by FOX and not any other provider.
I sent a comment to FOX explaining the problem, but I kind of doubt it'll get to the right place. That's the pessimist in me speaking. If any of you are having issues, please send complaints as well.
i notied the audio cut one twice briefly while watching last weeks fringe. i dont watch fox other than that so i don't know if it happened other than that.
i work in the tv industry, so i can tell you the first place to call is your local fox station. ask to talk to the master control department or the engineer in charge. ask them if they have had any audio problems with their network feed. if so, they can tell you how to get in contact with the national fox company. but i doubt complaining will get you anywhere; if they are having national problems i'm sure they are working on it.
westward ho 10-29-09, 09:45 AM I live in San Diego and have been having the metallic buzzing and skipping sound problems. I had the same problems when I lived in Madison, WI where Fox told me it was my local affiliate's issue. Then they told me it was DirecTV's fault. When I said I had recently switched from cable because they told me it was my cable company's fault, they stammered over their words and went back to blaming the affiliate.
Well, now I'm in San Diego and am having the exact same issues. Last night was particularly bad - from the 7th inning of the baseball game all the way through the late local news. I switched to SD and although the sound wasn't as brutal, it was crackling and the voices were off by 2 seconds.
I wrote Fox network a pointed email today and copied my Fox affiliate. I am going to call my affiliate today to see if I can get contact info for the appropriate person/group at the network. 4 years is way too long to not have the problem addressed and fixed. Fox obviously does not hold their viewers in high regard. I'm mad as hell and they can kiss my arse.
mjones73 10-29-09, 10:02 AM I was having the same audio stuttering on Directv watching Fox45 WBFF HD out of Baltimore during the game last night, it was particular bad around the 7th inning as you noted.
westward ho 10-29-09, 08:10 PM Called the Fox affiliate in San Diego today and asked for the master control department. The receptionist would not connect me, saying they don't accept calls in that department but if I gave my number they would call back today. They, of course, never called.
sneals2000 10-30-09, 10:52 AM Called the Fox affiliate in San Diego today and asked for the master control department. The receptionist would not connect me, saying they don't accept calls in that department but if I gave my number they would call back today. They, of course, never called.
The receptionist was, IMHO, totally correct not to connect you. A live MCR is not a place that calls from the general public should be routed to.
Equally, promising a non-existent call-back is also very poor for viewer relations.
I'd suggest the station engineer would be the person to try to communicate with - either via phone or probably e-mail?
What I see in New York (WNYW-TV) is a complete stream freeze. Still picture and no audio. Then it just picks up in a few seconds. I don't see an audio-only problem. This is via Comcast cable, but I've never seen it before this year's baseball telecasts. I don't watch a lot of FOX programs otherwise, and I've never seen this on other local broadcasts.
This just in: It happens on football, too.
goshockers 11-19-09, 02:27 PM I had this Audio Stuttering and out of Synch problem ALL day and night on Fox (Sunday Nov 15th)
Directv San Diego 69/5
zorinlynx 01-20-10, 01:55 PM Seems this issue is not fixed. I'm still getting audio problems, now when watching "24". This happened on both Sunday and Monday nights.
Is anyone else having issues? I keep wanting to suspect my receiver, but given that FOX is the *ONLY* network that has any problems, and all other AC3 sources play fine, I have to rule my receiver out as being the problem.
coyoteaz 01-20-10, 03:18 PM Fox is also the only one using 448kbit for 5.1 in your area. All other stations appear to be using 384kbit for their audio.
hmm, well i dont watch fox too often, but i havent noticed anything in my area. you said you're watching OTA, maybe its just a signal problem...
zorinlynx 01-21-10, 11:28 PM Fox is also the only one using 448kbit for 5.1 in your area. All other stations appear to be using 384kbit for their audio.
Hmm, could older receivers not be compatible with 448kbit AC3? I have a circa 2000 Denon AVR-1802. The thing is like I mentioned a while back, it decodes the stream fine if placed in 5 speaker stereo mode. So it's a mystery.
I really hope I don't have to upgrade my receiver over this. Grr. Is 448kbit AC3 even allowed in the standard?
coyoteaz 01-22-10, 01:58 AM Any DD-compatible receiver should be able to decode up to 640kbit. My circa-1998 Pioneer receiver works fine with 448kbit from Fox (and 640kbit from elsewhere), so I doubt it's an age thing. 448kbit is acceptable under the ATSC A/53 standard, and is used by Fox as well as many station groups using fancy audio processors. Some cable channels use it as well - TNT HD comes to mind.
Hmm, could older receivers not be compatible with 448kbit AC3? I have a circa 2000 Denon AVR-1802.
...
I really hope I don't have to upgrade my receiver over this. Grr. Is 448kbit AC3 even allowed in the standard?
No need to growl. Every AC-3 decoder ever made can decode up to 640 kbps (which is the maximum data rate in the AC-3 ssytem.) I think the first consumer box to put out 640 kbps AC-3 was the Xbox in 2001. Yes, 448 kbps is in the DTV standard. ATSC broadcasts can go up to 448 kbps, matching the data rate of (SD) DVDs.
Whatever your problem is, it has nothing to do with the decoder's ability to handle a 448 kbps signal.
zorinlynx 01-22-10, 01:19 PM No need to growl. Every AC-3 decoder ever made can decode up to 640 kbps (which is the maximum data rate in the AC-3 ssytem.) I think the first consumer box to put out 640 kbps AC-3 was the Xbox in 2001. Yes, 448 kbps is in the DTV standard. ATSC broadcasts can go up to 448 kbps, matching the data rate of (SD) DVDs.
Whatever your problem is, it has nothing to do with the decoder's ability to handle a 448 kbps signal.
I'm not growling at anyone here, I'm growling at the problem. it's just frustrating, especially since very few people seem to have this problem. (If it were widespread, FOX would have fixed it by now.)
Every other piece of software I analyze the stream with shows it as being valid. Having to drop to Pro Logic to watch my stuff (using analog cables from the TV) is almost a crime when I have a decent sound system!
texasbrit 01-22-10, 06:10 PM I'm not growling at anyone here, I'm growling at the problem. it's just frustrating, especially since very few people seem to have this problem. (If it were widespread, FOX would have fixed it by now.)
Every other piece of software I analyze the stream with shows it as being valid. Having to drop to Pro Logic to watch my stuff (using analog cables from the TV) is almost a crime when I have a decent sound system!
It is very widespread. One estimate I saw (from a Fox station engineer) was that one third of all Fox affiliates were having this problem. Most of the reports are from DirecTV or Dish customers where the Fox signal goes through an MPEG-2 to MPEG-4 conversion, and the problems in the digital audio signal cause the encoders to "hiccup" hence the brrrp sound. This is happening in the DirecTV or Dish Local Receive Facility. I assume that the signal you receive at your receiver might look like a good signal with the brrrp sound as part of the audio stream.
In a few extreme cases people with cable and OTA have reported some of these problems also.
I have seen posts saying the problem is something to do with the Motorola splicer at the Fox affiliate that merges network and local HD material. I have also seen posts from Fox station engineers saying that in investigating the problem they have found several issues in their audio processing chain.
tfelmly 01-27-10, 11:13 AM TWC HD box feeding Kenwood VR510 through Monster toslink cable.
All DD 5.1 channels fine EXCEPT for Fox out of Cleveland. Local inserts are fine, but as soon as the network feed comes back I get the horrible stuttering audio. Makes it totally unwatchable.
Contacting the local channel (WJW) is pointless. They don't publish email addresses or phone numbers.
Too bad since 24 and Fringe are among my favorite shows. I have to switch my HD box to PCM and simulated surround.
I'm working with local TWC support to see if their engineering staff can contact the local station.
Todd
bjdouros 02-01-10, 04:01 PM If I can summarize my efforts on this topic:
Using a Denon AVR-1802 receiver I have the same problem with Comcast in Chicago. In all there are about 10 HD channels (including FOX) where Dolby Digital 5.1 cuts in and out. Switching from Digital Optical to Digital Coaxial does not fix the problem either. I’ve even tried to run an HDMI cable from my Motorola Comcast box into the TV and then a Digital Optical back to the Denon, still no luck. And yes, standard ProLogic and 5 channel work fine.
I’ve been researching this for over a year and have concluded that this problem occurs with multiple Services Providers (DirectTV, Comcast, Sky, etc..) and with multiple receivers (Denon, Onkyo, Kenwood, etc..). From what I have been able to gather the problem is actually a fault in the DSP chip used to decode the DD5.1 sound. If I’m not mistaken all of the receivers I have read with this problem all use a variant of the same Crystal DSP chip.
I would be curious to know if any hi-fi experts could shed some light on my theory regarding the DSP chip. If this is the case I would imagine we are all SOL and might as well junk our units. No point in crying to the Networks or Service Providers, they wont listen anyways….
tfelmly 02-01-10, 04:14 PM I wonder what is going on with the digital stream to do this just on certain channels? NBC, CBS, HBO, and numerous other HD channels all sound fine. Just a handful have this problem.
bjdouros 02-01-10, 04:24 PM I'm not sure but I can't imagine the problem could persist across multiple Service Providers with non affiliated channels using various stereo receivers. The only link I can find is the DSP chip. I don’t remember my full list of channels that are experiencing this problem but I do know: FOX HD, FX HD, AMC HD, NatGeo HD, and Versus HD all have this problem where I’m at (Comcast in Chicago). Also one other thing to note is that when I watch local sports on FOX HD the sound is fine, no problems.
zorinlynx 02-01-10, 04:39 PM From what I have been able to gather the problem is actually a fault in the DSP chip used to decode the DD5.1 sound. If I’m not mistaken all of the receivers I have read with this problem all use a variant of the same Crystal DSP chip.
I have the Denon AVR-1802 as well, so at least this brings some commonality to the problem. However, I wonder how valid your theory about the flaw being in the DSP chip is.
I have had this receiver since 2000 and have played countless AC3 streams from countless sources through it with nary a problem. And now all of a sudden in the past year, I start having issues, and only with FOX?
I think the problem is in whatever software or DSP FOX is using to encode its AC3 streams. The AC3 streams are probably not to spec, but most receivers ignore the problems and play the sound anyway. Our Denons probably have a mute circuit to protect the speakers from noises caused by faulty streams, and the circuit is being triggered by FOX's stream.
Ten years of *flawless* AC3 performance suggests this to be the case. We need to find a way to get FOX's attention on this. Some bad firmware or software out there is causing this, and since it affects so few people, we may indeed be SOL unless we can scream loudly enough.
bjdouros 02-01-10, 05:04 PM I think the problem is in whatever software or DSP FOX is using to encode its AC3 streams
My problem is not just with FOX. I really only watch 24 and local sports on FOX. Which is even weirder because I don’t have the sound problems with local sports, just 24.
I have the same problem with about 10 other channels though: FOX HD, FX HD, AMC HD, NatGeo HD, and Versus HD are the main ones I watch with the problem. I do agree that this is odd considering I also have had my Denon for almost 10 years with no sound issues to speak of. I am a huge movie fan and love my sound system!! I first noticed this problem a year ago with AMC HD watching Mad Men. I called Comcast and have had technicians out numerous times with no avail. Every time they say it is a receiver issue. Recently Comcast has been adding more and more HD channels and I am seeing it now more and more. Still no issues playing AC-3 with a DVD/Blu-Ray player.
I have the Denon AVR-1802 as well, so at least this brings some commonality to the problem. However, I wonder how valid your theory about the flaw being in the DSP chip is.
I have had this receiver since 2000 and have played countless AC3 streams from countless sources through it with nary a problem. And now all of a sudden in the past year, I start having issues, and only with FOX?
I think the problem is in whatever software or DSP FOX is using to encode its AC3 streams. The AC3 streams are probably not to spec, but most receivers ignore the problems and play the sound anyway. Our Denons probably have a mute circuit to protect the speakers from noises caused by faulty streams, and the circuit is being triggered by FOX's stream.
Ten years of *flawless* AC3 performance suggests this to be the case. We need to find a way to get FOX's attention on this. Some bad firmware or software out there is causing this, and since it affects so few people, we may indeed be SOL unless we can scream loudly enough.
Flaw may be the wrong term. Incompatibility is probably a better way to think about what's happening.
tfelmly 02-01-10, 06:18 PM Same here. Kenwood is about 6 years old and never had an issue before. AMCHD also has the problem on TWC as well.
bdfox18doe 02-01-10, 06:46 PM Flaw may be the wrong term. Incompatibility is probably a better way to think about what's happening.
Yep,IMHO, possibly likely due to the new Motorola encoders FOX has been installing.
Have passed this thread on to a few folks.
I had the same issue with some YammyHaw receivers in 1997 with the first HD station I worked on. Turned out to be a bug in the Dolby encoder software, that was quickly fixed once known.
zorinlynx 02-02-10, 09:42 AM Yep,IMHO, possibly likely due to the new Motorola encoders FOX has been installing.
Have passed this thread on to a few folks.
I had the same issue with some YammyHaw receivers in 1997 with the first HD station I worked on. Turned out to be a bug in the Dolby encoder software, that was quickly fixed once known.
Keep us posted on what you hear? If the problem isn't fixed I'd at least like to hear an explanation.
What's funny is I can afford a new receiver; it just goes against principle to buy a new receiver just because the networks are incompetent. Even if some encoder bug only affects 2% of their viewers, they should be willing to fix this. It's been the better part of a year now since this mess started.
bdfox18doe 02-03-10, 08:23 AM Keep us posted on what you hear? If the problem isn't fixed I'd at least like to hear an explanation.
... because the networks are incompetent.
Such comments usually don't help your case. Perhaps you would be willling to go and show them what they are doing wrong? I am sure they would welcome the help! :)
zorinlynx 02-03-10, 08:13 PM Such comments usually don't help your case. Perhaps you would be willling to go and show them what they are doing wrong? I am sure they would welcome the help! :)
I'm not basing this only on audio issues. Over the past few years I've seen such things as:
- 4:3 content stretched to 16:9 when upscaled
- 16:9 content letterboxed and pillarboxed (this still happens a lot)
- Switching to pillarboxed low-quality video to show lottery numbers on the screen
- Logo bugs in an awkward 4:3 safe area instead of in the corner where they *used to be* when HD broadcasting first started...
...and other such issues. These things happen often enough that I start to wonder about the people running things. Admittedly they have gotten better in the past few years, though.
While I'm sure you personally are competent, there are still many problems that need fixing.
bdfox18doe 02-03-10, 09:13 PM there are still many problems that need fixing.
Oh, you have no idea..you should deal with HD on a daily basis the way some of us do..sometimes the fixes just aren't that easy! :eek:
texasbrit 02-03-10, 11:37 PM None of the things you mention are caused by incompetence on anyone's part. -
- 4:3 content stretched to 16:9 when upscaled
That's deliberate policy on some channels. derisively called "stretchovision"
- 16:9 content letterboxed and pillarboxed (this still happens a lot)
If the SD version of the channel is transmitting 16:9 material it letterboxes it. If the HD version of the channel is broadcasting the SD version upscaled then it gets pillarboxed. So 16:9 content on the HD channel can easily be letterboxed and pillarboxed.
- Switching to pillarboxed low-quality video to show lottery numbers on the screen
Perfectly normal, if the channel does not have the equipment necessary to deliver this in HD
- Logo bugs in an awkward 4:3 safe area instead of in the corner where they *used to be* when HD broadcasting first started...
Deliberate policy on network channels. They want the logo to be viewable by people with converter boxes delivering a 4:3 picture
I'm not basing this only on audio issues. Over the past few years I've seen such things as:
- 4:3 content stretched to 16:9 when upscaled
- 16:9 content letterboxed and pillarboxed (this still happens a lot)
- Switching to pillarboxed low-quality video to show lottery numbers on the screen
- Logo bugs in an awkward 4:3 safe area instead of in the corner where they *used to be* when HD broadcasting first started...
You have no idea what you are talking about.
You have no idea what you are talking about.Ken, he knows exactly what he is talking about, just has no idea of the reasons. He has seen those things, as have all of us. It is hard to handle the ignorant questioner. We can hope he gains knowledge.
That tale on levels of knowledge, incomplete:
Those who don't know and don't know that they don't know, teach them
Those who don't know and know that they don't know, teach them
Those who don't know and think that they know, run from them
Those who know and know that they know, learn from them
zorinlynx 02-04-10, 03:22 PM None of the things you mention are caused by incompetence on anyone's part. -
- 4:3 content stretched to 16:9 when upscaled
That's deliberate policy on some channels. derisively called "stretchovision"
- 16:9 content letterboxed and pillarboxed (this still happens a lot)
If the SD version of the channel is transmitting 16:9 material it letterboxes it. If the HD version of the channel is broadcasting the SD version upscaled then it gets pillarboxed. So 16:9 content on the HD channel can easily be letterboxed and pillarboxed.
- Switching to pillarboxed low-quality video to show lottery numbers on the screen
Perfectly normal, if the channel does not have the equipment necessary to deliver this in HD
- Logo bugs in an awkward 4:3 safe area instead of in the corner where they *used to be* when HD broadcasting first started...
Deliberate policy on network channels. They want the logo to be viewable by people with converter boxes delivering a 4:3 picture
Thanks for clearing up the reasons behind a lot of these issues. It makes more sense now, even if I think some of the practices are still annoying. They could easily show us the lottery numbers during the next break, for instance.
I guess it's not as bad as it used to be; I remember when UPN would occasionally show entire episodes of "Enterprise" at low resolution, letterboxed and pillarboxed. It was maddening; I haven't seen screwups on that level in a long time, though.
But back to being on topic, I hope this audio issue can be fixed.
bdfox18doe 02-04-10, 07:06 PM I hope this audio issue can be fixed.
Oh, I'm fairly confident that at some point the cause will be found.
tfelmly 02-08-10, 08:14 PM They may have found the problem in Cleveland. As of tonight (Feb. 8) WJW Fox's DD sounds great from DirecTV. Yesterday it was stuttering like crazy.
Strike that --- 30 minutes into House it started up again. Probably when they went to local spots.
So close!
tfelmly 02-09-10, 11:02 PM I emailed a tech at Kenwood about this and he said:
"We believe the surround signal is being sent at 192kHz (not a valid copyrighted Dolby signal)."
bdfox18doe 02-10-10, 11:12 AM I emailed a tech at Kenwood about this and he said:
"We believe the surround signal is being sent at 192kHz (not a valid copyrighted Dolby signal)."
Then he probably needs to read up on the Dolby specs.
Eric Seaberg 02-10-10, 04:41 PM Just as a little more info., most networks distribute their audio either discrete 5.1 or via Dolby E, which is VERY stable. Once that signal gets to your local affiliate, they decode the Dolby E stream, hopefully keeping all attached metadata, and add LOCAL audio. At that point, before it leaves their house, it's converted to Dolby Digital AC3.
If there were problems with the network feed, the local would certainly hear it as they MUST decode the Dolby E stream in their facility prior to re-encoding to AC3.
Just as a little more info., most networks distribute their audio either discrete 5.1 or via Dolby E, which is VERY stable. Once that signal gets to your local affiliate, they decode the Dolby E stream, hopefully keeping all attached metadata, and add LOCAL audio. At that point, before it leaves their house, it's converted to Dolby Digital AC3.
If there were problems with the network feed, the local would certainly hear it as they MUST decode the Dolby E stream in their facility prior to re-encoding to AC3.
Not at FOX. The encoded AC3 stream is sent from the network and passed through at the local level.
bdfox18doe 02-10-10, 08:45 PM Just as a little more info., most networks distribute their audio either discrete 5.1 or via Dolby E, 3.
CBS uses Dolby E for 5.1 and PCM for stereo. ABC and NBC use phase aligned discrete pairs for 5.1, and PCM for stereo. FOX uses bit stream splicing with the network audio being pre-encoded 5.1 @ 448k.
Eric Seaberg 02-11-10, 07:40 PM Not at FOX. The encoded AC3 stream is sent from the network and passed through at the local level.
Are you serious? Then how do they insert local audio? You can't unpack/repack AC3 without terrible artifacts!!
Are you serious? Then how do they insert local audio? You can't unpack/repack AC3 without terrible artifacts!!
We don't do anything to the network audio. We only splice back and forth between the local and network streams at the appropriate times.
Eric Seaberg 02-11-10, 08:01 PM We don't do anything to the network audio. We only splice back and forth between the local and network streams at the appropriate times.
So you splice in another AC3 stream? It's certainly random, isn't it, since you're not locked to video frames as Dolby E. That does explain a lot.
As a 'program provider', I sure wish all the networks would figure out a consistent delivery method that would insure me, as a paying customer, the same quality output as what I put on the tape. We are supplying program with PCM stereo on 1/2 and Dolby E in 6-channel mode on 3/4 on HDCam. We do 6-channel because we also deliver XDCam to some stations and since it can only do 16-bit audio, we step-down the Dolbys.
bdfox18doe 02-11-10, 08:28 PM So you splice in another AC3 stream? It's certainly random, isn't it, since you're not locked to video frames as Dolby E. That does explain a lot..
The splice is done at the MPEG level using the ASI stream. Basically, in simplistic terms..it's a 'transport stream" clean (kinda) switch.
Kinda dated, but here are two good explanations:
http://www.mpeg.org/MPEG/splicing-FAQ.html
http://broadcastengineering.com/infrastructure/broadcasting_splicing_mpeg/
Eric Seaberg 02-11-10, 10:24 PM Thanks Bob and spwace... it just doesn't seem as clean to me as what Dolby E is spec'd to do. I'm just surprised that since the technology exists with Dolby to make it easy for everyone, especially with metadata and dialnorm, why is it taking so long to implement?
I, at least, do applaud ABC and NBC for keeping it discrete, but that means any dialnorm info I add is totally lost, and there are a LOT more places for my 5.1 mix to shift heavy Ls or C or whatever. If CBS does use Dolby E, do they retain the originator's metadata? I had heard at a 5.1 symposium at NAB that one of them, could be CBS, strips all metadata and sets dialnorm for -31.
Why have all these great tools for post-production and delivery if the networks don't read it or care about it?
(Interesting articles, Bob. Thanks, but it certainly seems like there's potential to lose sync between audio and video by splicing, yes? At least an audio frame.)
coyoteaz 02-12-10, 02:13 AM Splicing effectively gives them 100% HD+5.1 coverage, discounting the markets where Fox is only available on an analog LP or digital subchannel. There are plenty of ABC, CBS, and NBC affiliates not doing HD, and far more who can't do DD5.1. If the station can somehow manage to put 720p into the local side of the splicer, they can get perfect Fox network HD and 5.1 out to their viewers, even if their local stuff looks like a 20 year old VHS tape.
videojanitor 02-12-10, 01:42 PM Why have all these great tools for post-production and delivery if the networks don't read it or care about it?
There is at least one aspect to FOX's delivery method that is quite appealing to me -- the local station cannot alter the network audio. There are several affiliates of "other" networks in my area that are unlistenable due to the HEAVY amount of compression they are applying. Dynamic range is reduced to zero, and all background sound is sucked up the same level as dialog. Unlistenable. With FOX's method, the affiliate is out of the loop, providing the untouched network audio to the home. I like that.
tfelmly 02-14-10, 06:47 PM I'm about ready to drop more money and replace my Kenwood AVR to fix this problem. :mad:
Are new AVR receivers immune to this issue? I'm looking at an Onkyo SR607 FWIW.
firemaneric 02-14-10, 08:52 PM i am having the problem on my SR607. i watched the Nascar race today on Foxand the problem kept happening. I have been watching the Olympics since then on NBC without the problem happening.
tfelmly 02-14-10, 09:28 PM I watched parts of the NASCAR race but didn't have any audio problems. I'm on DirecTV FWIW. I think you posted over on Afterdawn.com too.
zorinlynx 02-14-10, 09:31 PM I wonder if they changed anything at FOX? I've been watching FOX Sunday night without any glitches or problems tonight.
Anyone else?
tfelmly 02-14-10, 09:44 PM I just went to check out FOX during American Dad and yes the sound is clear.
Hope they fixed it!
BTW - I posted a MP3 clip with a sample of the sound I am getting from Fox and other HD networks.
Can you take a listen here:
http://www.dbstalk.com/showthread.php?p=2357102#post2357102
Is the same thing you are hearing?
zorinlynx 02-14-10, 10:17 PM I just went to check out FOX during American Dad and yes the sound is clear.
Hope they fixed it!
BTW - I posted a MP3 clip with a sample of the sound I am getting from Fox and other HD networks.
Can you take a listen here:
http://www.dbstalk.com/showthread.php?p=2357102#post2357102
Is the same thing you are hearing?
Nope, my problem sounds different. The audio mutes for a few seconds at a time. In fact, it's mostly muted, with only occasional blips of sound coming through. If I hold my ear next to the speaker, I can hear the sound playing normally at an extremely low volume when it's muted. This means the receiver is correctly decoding, just muting because it thinks there's a problem with the bitstream.
It seemed clear tonight, but only time will tell. I hope to watch "24" tomorrow in real 5.1 for the first time since the season started!
I'm starting to wonder if the problem is due to flakey firmware in some piece of equipment deployed by several networks. It seems to have started with FOX and has now spread to several other networks. The bad stream seems to be messing up with DBS networks' equipment as well. It's pervasive and I hope they can find the issue soon.
tfelmly 02-14-10, 10:43 PM I bet it's the same issue, just that our AVRs process the 'problem' differently. Could be processing speed and mine is able to recover faster?
24 will be the big test tomorrow though. I thought it was fixed last week since the first 30 minutes of house was clear but it started to stutter on me again.
Eric Seaberg 02-15-10, 10:59 AM There is at least one aspect to FOX's delivery method that is quite appealing to me -- the local station cannot alter the network audio. There are several affiliates of "other" networks in my area that are unlistenable due to the HEAVY amount of compression they are applying. Dynamic range is reduced to zero, and all background sound is sucked up the same level as dialog. Unlistenable. With FOX's method, the affiliate is out of the loop, providing the untouched network audio to the home. I like that.
OK, I'll agree with that IF they pass my original metadata converting the Dolby E to AC3 at FOX HQ.
tfelmly 02-15-10, 08:04 PM Fox sounding good so far as of 8:05 pm Monday :)
zorinlynx 02-15-10, 08:07 PM Fox sounding good so far as of 8:05 pm Monday :)
Same here; I don't watch House but I put it on to see if problems were gone and they are!
Here's hoping for the best. 53 minutes to 24...
tfelmly 02-15-10, 09:13 PM All good on 24!
THANK YOU FOX for finally giving us clear Dolby Digital sound!
Now can your engineers please talk with the dozen or so other channels with this same problem and give them some hints on how to fix their sound??
jeymann 10-30-10, 09:30 PM We live in So. Cal. and get Fox on Time Warner Cable. For months the musical soundtrack sounds like it is slipping. It is unbearable during most ads; anything involving music. Regular, verbal transmission sounds fine. The problem is only on Fox and is true for all their shows and ads.
|
|