U502 has blown up OTA...again.

[JSheridan]

So that blows the R191 theory out the window.

Something is making certain receivers drop the OTA channels with this new software. I hope the software engineers can figure it out.

 

[Almighty1]

So that blows the R191 theory out the window.

Something is making certain receivers drop the OTA channels with this new software. I hope the software engineers can figure it out.

Maybe it's R19x

 

[Jon J]

My receiver is an R194xxxxxxx. OTA recordings unwatchable.

 

[stardust3]

Browsing on the dish retailer portal, this is a topic that was brought up. Hopefully a fix is in the near future.

 

[stardust3]

Anyone have an internet connected h3 with ota? Looking for someone not have disappearing ota locals in the guide but corrupted ota recordings.

Working with dish on the retailer portal, they need a receiver # to help diagnose the issue. If interested pm me, do not post receiver # publicly.

 

[KAB]

Anyone have an internet connected h3 with ota? Looking for someone not have disappearing ota locals in the guide but corrupted ota recordings.

Working with dish on the retailer portal, they need a receiver # to help diagnose the issue. If interested pm me, do not post receiver # publicly.

I am not losing OTAs overnight. Recordings are bad.

 

[dennispap]

On my hws it just doesn't record ota. It will show it in the timers list, and in the scheduled list, but it wont record. After the fact, if you go into the scheduled list and back up, it will show timer started at 9pm. timer stopped 10pm. But it shows recording started not applicable recording stopped not applicable. ??

 

[pattykay]

That looks like the kind of result you would get if you set an auto tune timer instead of a DVR (recording) timer.

 

[dennispap]

That looks like the kind of result you would get if you set an auto tune timer instead of a DVR (recording) timer.

No it was a record timer. It shows record once on the top line.
It just doesn't record ota.

 

[bchandler02]

Came here to look for help and found this - also having this issue. My H3 has been great since installed, with the original single tuner OTA adapter. A few weeks ago it got really bad - OTA HD recordings are unwatchable. Oddly enough just tried an OTA recording of SD and it's fine.
Went and looked at my software - 502 on 8/30/17, that explains it.
Also noticed that last night's episode of Mighty Trains didn't record either.

Dish needs to get their crap together with stuff like this. It's basic functions, and if they think I'm going to pay full price for half ass hardware or software, they're in for a shock. They should know that by now.

Where's the response from Dish here on this?

 

[KAB]

What kind of response are you wanting???
It's a known bug. It will get fixed.

 

[Partysox]

What kind of response are you wanting???
It's a known bug. It will get fixed.

Or not

 

[Hall]

It's a known bug. It will get fixed.

Did someone at Dish tell you this ? Being known and getting fixed are two vastly different things....

 

[GPM]

Late to the party here, but with the same problem. I don't usually watch the OTA channels, got the module due to the limited tuners with the HWS and since moving to the H3s I haven't paid much attention. Tried to watch a recording the other night and noticed the audio and video drop outs. Thought maybe there was a storm when it recorded and didn't think much of it. Watched another recording today and same thing. Both recordings were from old timers copied from the HWS and were on OTA channels. I changed the Audio output to my soundbar to turn off Dolby Digital and it was at least watchable. My receiver is R194...

I just went through 100+ timers and switched all OTA timers to Sat timers.

 

[bchandler02]

What kind of response are you wanting???
It's a known bug. It will get fixed.

Did someone at Dish tell you this ? Being known and getting fixed are two vastly different things....

That's my point. Where has Dish acknowledged this? They have a history of leaving defects in software for extended periods.

Dish has had this problem before. That means that 1) it should be something they watch for, and 2) they probably know the fix and could get it out quick.

In my industry, when my team releases software with major defects, we roll it back and go back to a stable release until we can fix it. We don't leave our customers with a broken product on a core functionality of the product, and no ETA for it to be fixed.

 

[Jon J]

I would love to have U500 or U501 back. Cannot understand why working code would be changed.

 

[Hall]

In my industry, when my team releases software with major defects, we roll it back and go back to a stable release until we can fix it. We don't leave our customers with a broken product on a core functionality of the product, and no ETA for it to be fixed.

But.... it's just TV....

 

[Hall]

I would rarely encounter this but one of the local TV stations was at our youngest daughter's school filming classes doing the pledge of allegiance (yes, our school does this !) and they are being broadcast this week. I've set timers to record the 5am, 5:30am, 6am broadcasts, just in case they play them early or late and for whatever reason, I selected an OTA channel to record. Anyway, they are affected by this bug. I had watched a Frontline episode that I recorded on the 12th and thought maybe there was issues that caused macroblocking and didn't give it a 2nd thought. Then I watched the first news recording from OTA and it was affected too and I didn't think it was a coincidence as much now....

 

[pattykay]

I would love to have U500 or U501 back. Cannot understand why working code would be changed.

I would love to have a 501 back.

 

[bnewt]

That's my point. Where has Dish acknowledged this? They have a history of leaving defects in software for extended periods.

Dish has had this problem before. That means that 1) it should be something they watch for, and 2) they probably know the fix and could get it out quick.

In my industry, when my team releases software with major defects, we roll it back and go back to a stable release until we can fix it. We don't leave our customers with a broken product on a core functionality of the product, and no ETA for it to be fixed.

But your business is run properly..........striving for customer satisfaction that could increase sales. Dish doesn't care about the customer. If the bottom line isn't what they want, they just raise the price, regardless of how many customers they have lost or will loose.