Another experiment I should try this weekend, or maybe Crash will get a chance earlier: When you do TV setup, the list of which tuners are assigned to what lineup and channels are all stored in the guide DB. The GUIDs identifying the tuners are actually returned by the tuners themselves when queried through SSDP, so they should be consistent between Windows installs for the same physical tuner. What happens if you copy the already CableCARD configured guide DB from 8.1 to 10, and update the registry key saying which guide db version is current? Edit: Just realized one possible flaw in this: The guide DB is encrypted. The password to get an administrative connection to the ObjectStore db works out to a different value on each machine calculated from a client ID. This indicates to me maybe the encryption is also install dependent. I have a feeling I'm going to be doing some experimentation to see if I can add tuners programmatically.
In 14393 DVB wmc v8.8, I didnt know that DVB is in charge of the guide, I copied MCepg from 10586 to 14393 and blew up WMC.
I got dragged into work, sorry for the delay. I have 2 msmpeg2vdec.dll, just to be clear, Do I need to rename both? "C:\Windows\System32\msmpeg2vdec.dll" "C:\Windows\syswow64\msmpeg2vdec.dll" I renamed them both, Will try WMC live tv now
So I renamed them both using the Chainsaw in 10586 Opened up WMC LiveTV Non protected channels play fine. Drm channels give Copying Prohibited Error.... The broadcaster prohibits this content from being copied. You can only play this content on the same computer on which it was recorded. So I go back in to System32 and rename the file to what it should be, go back to WMC and DRM channels play
Next would be to try to identify more of the protected path. First step would probably be to use the truncated wmdrmsdk.dll from 14393. Eliminating the wmdrm dlls from 10586 had no effect on playing a DRM channel, maybe it might have an effect on setting up the tv signal. I think somebody might have checked this already.
I don't know if this is useful, but while playing a DRM channel ehshell.exe has a bunch of interactions with \programdata\microsoft\playready\mspr.hds and \programdata\microsoft\windows\drm\drmstore.hds. Also a lot of checks with cryptography registry entries. These don't happen while playing a non DRM channel. I wonder if adding those directories to the files being backed up on a working WMC could then be transferred to 14393 and make a difference.
The mspr.hds and drmstore.hds are keyed to the windows install. If you try to copy them it will break the DRM on the destination. (assuming it worked to begin with). If you delete them (at least the mspr.hds, not sure on the other), it will create a new one, and you will lose access to any previously existing encrypted recordings. More interestingly...... If you do some hardware change that makes Windows detect it is running on a "new machine", i.e. new memory channel, motherboard swap, toggling hyperthreading in BIOS, playready will break because of mspr.hds being from the "wrong" machine. Renaming it will allow you to record protected content again. If you then revert whatever hardware change you did, it won't like the new mspr.hds file. But you can rename to swap them back and watch your old recordings again.
Okay, I got a new PC with win10, downloaded the recent WMC build, followed the readme that came with it and installed my DCR2650 drivers and such, I am trying to go into live TV setup, it says Tuner not Found. Tried the reboot and sleep trick and didnt work... Getting frustrated with all the trouble of getting WMC to run on a new Win10 system.
But if its the same machine with no changes just an updated Windows build it should still work. Do protected recordings still play after updating to 14393? I think crash2009 said they did.
I never made any protected recordings prior to going to 14393, I did the upgrade then did a reset-don't save the files. It appeared to me this was the only way to get stable.
Thanks. But I don't understand if you are talking about the files renamed to .old or about the files replaced with 14393
Plagued with same problems last couple of weeks. No tuners, no TV-Guide. Built a w8.1+WMC on same machine, configured WMC, backed this up by BackupRestoreSettings.cmd out of T-S Package. Restored under w10 14393.xx. Keeps running since...
What I find very comfortable is using DVBLink software in the middle. Then WMC doesn't care about what type or brand tuner you have. DVBLink handles that part (and supports a broad range of tuners). You can use sattelite, DVB-C, DVB-T all at once.....
Dvblink is a must have, no matter if you use it with a WMC as client, as backend engine or not. The only glitch is on getting the EIT EPG listing, isn't onpar wit Mediaportal or other programs on that task. but EPG grabber is enough to fix it brilliantly. And given isn't conflicting with ServerWMC the combinations using both of the becomes almost unlimited..
Has anyone experienced serious crashing with 8.8? I get total lockup to the point that even the reset button becomes unresponsive. I'm getting it daily. It happens when I start playing a recording, so I'm assuming it's some kind of codec issue. There's never any crash at any other time - only when trying to watch something - during the white spinner . And it doesn't happen every time I try to watch something, probably 1 time in 5. I've seen bibbleq's post 6527 and others referring to sleep issues, but in my case the PCs are both fully awake. In fact they're sleeping and resuming better than ever. I've got this issue on two very different machines with very different tuners, both running 1607: one was completely rebuilt and 8.8 installed, for the other I uninstalled the previous version (12 I think) and then installed 8.8. I'm in the UK and as such haven't (and never) installed PlayReady: I'm using 2 Freeview tuners on one machine, and 2 Freeview and 1 Freesat on the other, and I pretty much only use HD channels. As an aside, thanks to T-S and others for their work - I'm certainly more than grateful for the efforts in keeping MCE alive. (And I have looked back 20+ pages and searched the thread before writing this! As others observe there's a lot of activity here, which I regard as a Very Good Thing.)
I think you are mixing glitches introduced by 1607 with problems of the WMC package itself. I have no evident problems with WMC, but, for example the IR receiver embedded in my tuner stick doesn't work anymore on W10 or Server 2016. The newest drivers fails tho expose it, the older ones are crashing the machine when the IR.exe is closed/unloaded. The mileage may vary depending the drivers, and would be better to test them with a different program, say Mediaportal, to understand what problem belongs to the drivers and what belongs to WMC itself. P.S. don't forget to replace the stock codec (msmpeg2vdec.dll) with the one taken from 10586, at least on my machine it crashes consistently the WMC.
You know, if you still have a Windows.old folder from the upgrade, it backed up all removed files, so those DRM files could stll be there...... It's pretty much a copy of everything removed