CableCARD tuners are absolutely real tuners in the usual sense. The reason they all have a network interface is because CableLabs demanded the communication between the tuner and the PC be using the OCUR scheme thru IP for the DRM scheme. Hook an antenna to the InfiniTV and use the web interface to tune to 55MHz (2), 61MHz (3), 67MHz (4), 77MHz (5) or 83MHz (6), and you'll see you can actually stream OTA with it. Cable just doubles the data rate using QAM256 instead of QAM16 (ATSC) for most channels, and has a remapping of the channel numbers to the frequencies sent periodically in the OOB channel along with the info about which CableCARDs are allowed to view what for the DRM.
Well the usual sense of tuner is to select a definite range of the the radio spectrum, which is 6/7/8Mhz depending the country and the frequency range. I guess something similar was done also with the analogue cable signal, but I'm not sure the digital cable is built on the old analogue infrastructure. Anyway I'm surely not an expert of that specific area. Here the cable TV is totally unknown, no matter if analogue or digital. kilo Hz?
Sorry, meant MHz, you're right. The tuner UI lists it as kHz but you have to enter the numbers as 55000, 61000, etc. The digital cable and analog cable use the same frequencies for 2-125 (meaning NTSC 2 through 125 is the same frequencies as QAM 2.*-125.*, not the cablecard number remapping). 126-158 (in practice 126-135) weren't part of the analog range.
Had a dig back into the thread but not finding much on this - Anyone else having PC lockup / crash issues when using MCE after sleep? I can watch TV just fine (UK DVB-T2 quad tuner) but after sleep any channel that is tuned locks up the PC. No BSOD, no crashed tasks just full on unresponsive till you press & hold power button I've tried v12 install, v8.8.1 install, re-tuning between each & a full PC reset. Troubles only started after the RS1 aniversary update
That sounds like a Service Deadlock situation, might have to experiment with setting one/some of the WMC services to "delayed start". ETA ~ Wait, those sevices are Manual Start, triggered by scheduled tasks. Ignore what I just said.
I think your problem is mostly driver related rather than WMC related, sometimes the newer isn't the better, try an older one
i have 3 or 4 of them, they worked great upto windows10. (i was only really using 1, but was tempted to setup 2 more) anyone want one? $10 obo +shipping? lol.
I'd agree but I've had 1 year in Win8 and 1 year in Win10 RTM without issue with the same tuner & drivers (no resume sleep issue). It's a pain that if full on locks as there is no crash dump to dig through.
After a reboot my Hauppauge ministick works only after a replug, if used with the same drivers I've used on Server 2012 R2 (same level as win 8.1) w/o a problem. I reverted the driver to an older W7 version and the problem disappeared. In short, is not the the OS alone or the driver alone that matters, but their combination. A minimal change on a timing on either side can make an huge practical difference.
My Win7-InfiniTV4 system is my main "Production System". No experiments have been or ever will be done to that one. I purchased a HDHR-3CC for experimentation in Win10. In your case, with Win7 hosting your InfiniTV, and broadcasting over the network using the Ceton Driver Feature-Network Tuners, it would be unlikely that DVBLogic would be given a fair chance to work. Not only is the host OS configured for Network Tuners, so is the InfiniTV card itself. It is very likely if you reset the card, the card will be broken, as experienced by myself a couple times, and also by glugglug. Part 1 I have less than 1 day experience with DVBLogic so my impression might not be 100% correct. The way I see it DVB Server is installed on the host and would copy the setup of the host and then stream it to the Virtual Tuners of the client. DVB Client is installed on the client machine; Virtual Tuners are installed into Device manager. The client uses WMC to setup the Virtual Tuners and display the live TV streams on the client. I have DVBLogic installed on 14393 (with the broken DRM) did not test clients for obvious reasons. If DRM won't play on the host, it wont on the client either. This was installed on 14393 as a test, to find out if 14393 could see a Virtual Tuner. The questions we have now, and I am about to test it on 10586 (with working DRM) Part 2 The test will reveal the answers to the following questions. Is DVBLogic Server able to: Play Protected Content Stream Protected Content AND Is DVBLogic Client able to: Receive Protected Content Play Protected Content
New OS Step 1, Give it a name and join the workgroup. Turn on file and printer sharing. All apps need to be re-installed to open their respective ports in the firewall. You expect too much from M$....It will be 9 months before they figure out how to do an upgrade correctly. Reset to fresh.
I believe all the ATI TV Wonder DCT's that were ever made rolled off the production line in 2007, if that helps pin down whether they work with S-Card or M-Card? More importantly, is the power socket universal or proprietory? That would be important in getting the thing to work with a non-US replacement PSU