Having yet another Windows box in the house to maintain isn't something I really want, and I wonder how much of the $250 goes to Microsoft, how much they'll be trying to spy on me, when they'll drop support and cram a subscription model down my throat, etc. Running Windows will run both halves of CW_EPG, so that's a plus if you haven't got a machine already. But I don't need another instance of CW_EPG...one is plenty...Win10-pro 64-bit system that can use Kodi, VLC, the Silicondust View/PVR app, etc., for superb playback of CW_EPG recordings...
More research suggests that the HDHR solution will work without the $35/year subscription from SiliconDust. No use buying two sets of guide data. And the Pi 3 looks like about $60, all-in. I think I'm going this direction. I'll try to document my progress for OTA Raspberry Pi 3, HDHomeRun, and CW_EPG. Should the documentation be in this, or a separate thread?Is there an obvious live TV watching non-subscription app for the Pi solution?
As long as you're willing to give up MyHD, you can run W10-64 on an HTPC. I've been doing so ever since before the first W10 RTM. It's completely transparent for HDHR use (and nearly so for FusionHDTV). In fact, the Silicondust software has been available in 64-bit for quite a while.
Yes. Kodi has an HDHR plugin for that purpose.How much do you guys know about Kodi? I ... asked ... if it can be used to watch live TV on a unused tuner.
Bruce, this is misleading. As I pointed out in your logs, the "old" CW_EPG had the same problem with that HDHR unit, which evidently suffers a hardware issue that has probably grown worse over time. My guess is that it has a flaky power supply (a well-known occasional HDHR problem). Have you yet tried swapping out that wall wart with one of the known-good others that you already have? Until you've tried that we'll not know for certain whether or not my guess is correct.....Currently confused, the Silicondust software consistently finds the W7 workstation's tuners, where the new CW EPG can't.
Why'n'ell don't you just record '60 Minutes' with an hour of post padding set in CW_EPG? That would then catch any sports-caused overrun.Hullava lot of work just to get 60 Minutes when sports makes it run overtime. :frown:
I already did that with the old version, and all was stable until the update these past three years.Why'n'ell don't you just record '60 Minutes' with an hour of post padding set in CW_EPG? That would then catch any sports-caused overrun.
I just confirmed that same behavior here. Thanks for the bug report. I guess nobody else ever deletes his log (I don't).What about not being able to erase the log?. I hit clear log, but the old data returns.
No rush here, Boss.How about Saturday when I have more time?
That may have been related to the other HDHR Connect's issues if it was then on the same LAN.....I do remember when I first hooked up the 'newer' unit and ran the scan for tuners in Options,
the buzy icon just spinned and spuned for the longest time, before letting go, this was after we got 4.3.0 going on this machine.
Version 4.3 simply deleted the log file. I didn't like that and implemented a scheme in 4.4.0 to maintain one level of .bak file in case of a rash deletion decision. But, being a Delphi neophyte, I misunderstood the workings of a system routine and failed to confirm my backup function (which I never need, right? ). It's all fixed in Version 4.4.2. Meanwhile, you'll have to delete/rename CW_EPG.log (in the CW_EPG data folder, usually under C:\ProgramData) yourselves.The XP has no problem clearing the log pane.