Frankly, this sounds quite different from the issues I was experiencing in STL prior to the fix. And I think others in this town had similar experiences. For me, the dropout issue started with the Fox and ABC locals on my 622 and 722, but migrated to NBC and CBS with a later attempt of a fix via a software upgrade. That's where it has remained until this week's cure. When the issue migrated to CBS & NBC, it only moved to the 722. In other words, my 622 has been fine for several months. I don't own a 612, so I cannot comment.
Also, when I had dropouts, I would have (without exageration) more than 100 per hour and the Dolby 5.1 pilot would flash like a beacon.
So while I don't doubt Phrelin is having a real issue, the symptoms are similar but not identical.
Oh, my 722 problem started just like yours. ABC and Fox were a nightmare. But then I started getting the less frequent dropouts on CBS and NBC with no dolby off/on before I sent my unit into Echostar Engineering. Everything continued with the replacement unit. The software fix for me (in the San Francisco Bay Area) eliminated the big problem with ABC and Fox. But when you all in STL developed the big problems with NBC and CBS I ended up with the less frequent, no dolby impact, dropout on all four.
Whatever they did in STL sounds like it was somewhere between them receiving the station's signal and you receiving the signal at your box, not a problem your box. And if, indeed, there was a change in compression utilities on the ground at the uplink facilities, I want that fix in the Bay Area.
The fact that from the beginning I have been getting the "minor" dropout same problem on my 612 which hasn't had any recent software updates pretty much convinces me that this is on the ground in the DMA. The appearance of new reports in new HD DMA's of the kinds of problems we experience now reinforces my mindset that there's a problem on the ground.
Infrequently, I do get other types of audio dropout on cable channels and got one on Friday's Bill Maher on HBO, which is unusual for a premium but has happened before. Once I had to re-record a movie on HBO, but I have to assume that was a problem outside my box as the second recording was perfect.
My 612 has many more audio/video problems which I know are box related - but I use it in such a way that I can live with it for now. After they get the 722k and the 922 up and screwing up, then maybe they can turn back to improving all those 612's they've foisted on folks. (Yeah, that just the cynic in me.)
And I'm getting really irked as I received no response to my last two emails sent to the same people who were asking me all kinds of questions and had me sending them my box, etc. (Ironically, the cc to Tech Support which was only to keep that division in the loop resulted in the standard form gee-what's-this-new-complaint email back asking for my account info when every @#$%&* email I sent includes all the previous emails and if the tech had read all the way down to the bottom he/she would have seen all the info was there.)
I want Echostar/Dish to do in our area whatever it was they did in St. Louis. I'm troubled by the fact that Ron in Southern California and folks in NYC and the folks in the Rockies living near Echostar's labs never had this problem and that Echostar spent all that time and money on the box software and then had to fix the STL disaster without changing the box software. All logic says there is a problem with inconsistency between the DMA's on the ground.