My Hopper 3s updated to H312.Updated both of my Hopper3 receivers to H412 and my Joey3 to J512. Have not seen any changes so far. Everything still works great.
My Hopper 3s updated to H312.
HDCP fixes??? Be still my beating heart.Small fixes in this one for HDCP errors and formatting SD Channels
I hope they actually do get them fixedHDCP fixes??? Be still my beating heart.
As luck would have it, we could test it tonight.....I hope they actually do get them fixed
I do not have either issue on both my Hopper 3s that has the H312 update.Updated my H3 to H312 and started experiencing a couple bugs.
1) Watching Ch 106 (TVLand) and hitting Guide button brings up the guide, but it jumps to channel 9861.
2) Terrible lip sync problem on Ch 166 (CMT).
I've restarted and rebooted a couple times but both of these issues remain. They did not exist prior to the update.
Thanks for the response, Charles. The lip sync issue seemed to have corrected itself (may have just been a coincidence it started after the update). However, the Guide display still jumps to 9681 when on Ch 106 and selecting Guide. Weird.I do not have either issue on both my Hopper 3s that has the H312 update.
Did you try a pull the cord reset for your H3? How about trying a guide update in the Tools menu.Thanks for the response, Charles. The lip sync issue seemed to have corrected itself (may have just been a coincidence it started after the update). However, the Guide display still jumps to 9681 when on Ch 106 and selecting Guide. Weird.
Nope! lmao now I still get the error but gives me the option to reduce my resolution.I hope they actually do get them fixed
Temporary (hopefully) work around for guide lock is to press Guide, Options, 5 (all unsubscribed), Options, 4 (all subscribed), Back, Guide. Guide is now normal for a while.Updated my H3 to H312 and started experiencing a couple bugs.
1) Watching Ch 106 (TVLand) and hitting Guide button brings up the guide, but it jumps to channel 9681.
2) Terrible lip sync problem on Ch 166 (CMT).
I've restarted and rebooted a couple times but both of these issues remain. They did not exist prior to the update.