New Dual Tuner OTA Adapter
- Thread starter gpflepsen
- Start date
- Latest activity Latest activity:
- Replies 325
- Views 57K
I think I'll take the "over"
Smart move.
No such thing as a "deadline" with Dish. Well, some parts of Dish foolishly give dates for things but the other departments involved pay them no attention, obviously.But is it May of this year? You know DISH , they like to keep those deadlines not well defined.
Sent from my HTC6535LVW using Tapatalk
Will there be some kind of announcement from Dish when they flip the "on" switch?
Sent from my iPhone using SatelliteGuys
Sent from my iPhone using SatelliteGuys
I'll bet the notification takes the form of the forums filling up with failures of the dual tuners. Can anyone remember DISH getting software right the first time?
After owning the new OTA dongle for a couple weeks, I can say there is no doubt in my mind it was manufactured by Hauppauge. Not only do they have the same form factor, but the tuner sensitivity is the same (and not as good as the previous model Dish used from Pace International). It also tends to run hot like the Hauppauge-branded dongle. The Hauppauge branded dongle is also dual tuner.
Overall, it pulls in most of the channels I should be receiving, but it isn't getting all of them. I'm disappointed that Dish chose to use Hauppauge as the manufacturer, but I'm glad we will (hopefully) have dual tuner functionality soon.
Overall, it pulls in most of the channels I should be receiving, but it isn't getting all of them. I'm disappointed that Dish chose to use Hauppauge as the manufacturer, but I'm glad we will (hopefully) have dual tuner functionality soon.
Dish probably doesn't sell or need enough of these to justify a standalone manufacturing run. If they're just private-labeling a Hauppauge dongle, they simply pull 'x' units from their production run and badge them as Dish.
I don't doubt it. If they are stock models, though, why won't my Wally detect the Hauppauge branded one?
Sent from my iPhone using the SatelliteGuys app!
I'd guess the Dish versions probably also include different on-board drivers/firmware specific to the Dish receivers.
They probably have a different USB device ID programmed into the Dish Network labeled ones. Someone with one should be able to plug it into a PC and verify this.
Same as the Hauppauge Model 01595, but doesn't appear to work under Linux because it has a different Device ID:
https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-dualHD
When I checked my Dish OTA adapter in Kubuntu Linux:
Bus 002 Device 002: ID 2040:826f Hauppauge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0x826f
bcdDevice 1.00
iManufacturer 3 HCW
iProduct 1 955D
iSerial 2 0######01
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 55
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
I've got a PC running Windows 7 Professional; I'll also plug it in tonight and see what happens
Sent from my iPhone using SatelliteGuys
Sent from my iPhone using SatelliteGuys
Multiple answers above ^^ explaining how.
I don't know the manufacturing process but it's not unreasonable to think that they can 'program' (1000) devices with the Dish-specific ID, produce them, then go back to their own models.
Well, I connected the OTA adapter to my PC running Windows 7 Professional. It recognized it and immediately started searching online for drivers for "955D." A quick Google search pulls up Hauppauge 950Q and 955Q dongles which look identical to this "955D" (assuming that means 955 'DISH'). So, I downloaded the drivers for 950Q and 955Q, but it didn't recognize the hardware.
There we have it, folks. Hauppauge is indeed the manufacturer and it appears to be identical to the 955Q.
There we have it, folks. Hauppauge is indeed the manufacturer and it appears to be identical to the 955Q.
You might be able to force the 955Q driver to be used with the 955D.
Sent from my HTC 10 using Tapatalk
Sent from my HTC 10 using Tapatalk
Similar threads
