Brrrrriiiiip, what and where

The Brriipp issue was so bad for me last night I could hardly watch the Fiesta bowl. First time it has been so much of a problem! I actually watched the game with the TV muted it was so bad. Again, Fox affiliate. Can't watch SD so did not check the SD feed but the HD feed was bad - D feed, not OTA.

 

The Fiesta bowl was particularly bad. I had to switch to OTA.

 

Here is another thread on this subject. (the audio drops)

http://www.dbstalk.com/showthread.php?t=167900

 

Didn't have the Brrrrriiiiip issue for months, but recorded Oprah today to watch the Leno interview and the Brrrrriiiiip issue was awful.

 

Since the DVR update this week my Brrrrrps are back along with audio dropouts. I use a HR22. Before the update I was just getting audio dropouts since Nov 2009.

 

I hope DirecTV uses money from the price increase to fix the Brrrrriiiiip issue, it was bad on NBC tonight during Heroes and the local news.

It's bad during Leno tonight too, it records on the other HD dvr, so both do it.

 

Despite some wanting this (and other like minded) threads to 'disappear', the problems continue, although from what (perhaps fortunately) in my local area, at a very low rate (virtually non-existent on locals, and low to very-low rate on the nationals).

However, in the past couple of days I've had several calls from my MDU folks that they've noticed a 'new' effect of audio dropouts accompanied by a very short/minor video 'brrrip' effect.

It's only evident perhaps once every 5-10 minutes, and appears over all the HD channels, including (interestingly enough) 'temporary' channels such as Rogers Sportsnet Blue Jays baseball games (verified today).

Just like last year (or the year before for that matter), it takes something like a baseball game, with folks watching (or listening) the programming very intensely to become aware of it. I think I had seen it once or twice 2-3 days ago, then I got a half-dozen calls about it yesterday and today.

Just when the audio drop-outs had, again, virtually disappeared, up comes something to bring it to the forefront.

 

Watching Warehouse 13 last night and there were several audio disruptions, some at very inopportune times.

Not that DIRECTV is ever going to do anything about, it's obviously good enough for them, and it's unlikely people on a contract are leaving because of it, so who cares?

 

The only thing thats obvious is they havent found a fix for it yet. Anything else is just pure conjecture on your part and actually a little offensive. If you really feel that way I don't understand why you would even bother staying a D* customer.

 

I have not heard a brrriiippp in months. Not one.

I do get the audio drop-outs. It seems like brriippp has been replaced by a hole punched in the audio stream where the brrriiip used to be.

Are you really reporting brriipp or just the audio drop-out?

D* may have already done something about the brrriiippps...like replace them with silence, so you see, they do care.

Really....if the new "holes" are a result of trying to fix brriips, then that shows that they are working on it. Not particularly effectively to date, but at least it may be getting some attention.

 

I'm only a D* customer for 6 months out of the year as they're the only service that has MLBEI-HD, the rest of the year the account is in suspension(no pay). My primary provider is Comcast, which doesn't have audio issues.

 

Drop-outs, I should have been clearer, sometimes it's whole words, which is frankly, unacceptable. My understanding is that the "brrrps" and the drop-outs are the same thing, it's just that they have tweaked the data stream so it drops out now instead of stutters, same core problem(bad MPEG2>MPEG4 encoding), it's just being handled differently. So yes, I guess you could say they're trying, but all they've really done is change the symptoms, not the problem.

 

My real point in asking was to direct you to the current, and more properly titled thread, because this one is old, and completely wrong in its title for the current problem. Look here: (it's even a sticky!).

http://www.dbstalk.com/showthread.php?t=182017

You can read there, and actually contribute to the data collection (it's not a thread to vent, it's a thread to report). There are also other audio drop-out threads if you look around a bit. This thread should be left to die, as it describes a non-existent problem, and will only end up confusing people.

I think the cause for both problems has a strong possibility of being related, as you seem to. Let's just do what we can to evaluate anything they might be trying and not confuse them by discussing a problem that isn't manifesting the same way any more. Just a suggestion.

No one wants this fixed more than I do. I'm just advocating for a focused approach and trying to avoid dysfunctional distractions.