Last week in my town Charter switched to all digital, killing my QAM and Analog channels.
I switched to ATSC OTA channels because that's all I wanted to watch anyway and I'm not about to start paying $40 a month to get the channels I was already getting for free.
While reconfiguring I updated to the latest NextPVR version. Now, I can tune in the channels successfully with NextPVR and have the service mapped successfully through XBMC, but for some reason I cannot record. No quick recording or scheduled recordings work. I receive no error messages. I've attached what I think are the appropriate logs. I am no expert, they may contain something telling. Anyone got any ideas?
My card is an AVerMedia H826 Hybrid TV BDA Tuner
Some notes:
NextPVR allows me to watch another channel even though it acts like it's recording.
I checked to make sure my recording directory exists and the folder has full permissions.
System date and time matches npvr
I'm testing all of this directly in the npvr UI, I am aware of XBMCs current shortcomings with scheduling recordings
Record Log: http://pastebin.com/En8ZG4Mt
NPVR Log: http://pastebin.com/aK8KpAuY
After installing Windows 8.1 my HTPC has been refusing to sleep on its own - It would from the remote.
Finally discovered that during the update Windows had set up and joined a Homegroup and was busy broadcasting to the Lan (Lan is set up as a Workgroup). This was enough to stop timed sleep from starting.
Went to Homegroup settings and left the homegroup then disabled the 2 Homegroup services (and also the Windows Media Network sharing service while I was about it). Finally Computer now does to sleep after 30 mins as set.
Also had to reinstall the unattended sleep timeout reg key again.
If you are using Gotham for Windows, I took 1.8.4 from the Opdenkamp and applied sub's Timeshift frodo 12.3 changes and it seems to work ok. This has a proper xbmc.log logging
These should overwrite the file(s) in %ProgramFiles\XBMC\addons\pvr.nextpvr and need to be reapplied when you update the nightly.
sub I also tried to fix genre support but for some reason genre is not returned to xbmc like it is to the browser the difference seems to be the range request
Comcast has scrambled everything now so I want to use my 2250 to receive over the air hd but in devices there is no atsc listing. My card shows as qam 4 times and analogue 2 times and I don't see a way to switch the tuner to atsc.
I'm trying to access NPVR from a Raspberry Pi. I keep getting a "connection lost" error. Checking 'web.log' shows that 'session.initiate' succeeds but 'session.login' fails. If I leave the username and password blank, I cannot log into the web server's config screen. Once I create a username and password, I can log in to the config screen, but I continue to get the XBMC error. There does not seem to be any way to specify a username and password in XBMC client. What can I do to track down this problem further?
I have 2 recording drives set up in the server config; let's call them H and W.
I have set up several shows to specifically record on H or W.
So far that's working fine.
What I was hoping to do was set up a client with only the W drive in the recording settings tab, and only those shows that were on the W(ifes) drive would be seen by her. Those shows on the H(usbands) drive would not be available to her.
Unfortunately she still sees ALL of the recordings, both the H and W drive.
ElihuRozen Wrote:I use the 4-tuner with SageDCT and NetworkRecorder. I'm using it now with 3.1.1 on Windows 8.1 64-bit without Media Center on a new machine. Previously, I used it on Windows 7 32-bit with various earlier versions of NPVR. So, it does work with NPVR. I am using Verizon, if that matters.
This isn't ready for prime time, but when you feel in a mood to experiment you could try:
- Backup your npvr.db3 so you can restore it after the test
- Edit config.xml to include <EnableDRISupport>true</EnableDRISupport> in the <General> section of config.xml
- drop the attached dll in with your NextPVR binaries.
- start the app, check if you see your device on the Settings->Devices screen, try scanning for channels, and maybe watching tv.
- after the test, you'll want set <EnableDRISupport> to false, and to restore your npvr.db3 backup, to put things back to how they were.
I've got an nDroid support puzzle - I've an idea of what's going on but no idea what would cause it.
I've a handler in the main service for locating / loading 3rd-party assemblies...
Code:
AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(ResolveAssemblyEventHandler);
...it should normally only fire when looking for things like the SQLite dll etc. but in this case it's firing when trying to locate native .NET System assemblies.
...I'm guessing from the "Culture=nl-NL" part of the args passed in to the handler that it's looking for locale-specific versions of the System dlls but I've never seen that before and can't think what might be causing it.
Hi, I'm a newb, just joined to get help with this...
I have used nextpvr succesfully on a couple of previous builds, with xbmc. Right now, I've just set up a "new" machine, Win XP, xbmc, and I just loaded a pair of AverMedia A16C-D cards that worked fine in another machine. After a bit of faffing about, I got the drivers installed - 3.6.0.7. and according to device manager all is ok. (Though: under properties they are only shown as Avermedia audio capture devices).
Anyway, downloaded new version of npvr, and that went ok and so did the net frame 4 thing, that shows as installed.
The problem is, scanning in npvr finds nothing, though both devices are listed. I'm not at all sure it's npvr's fault as this is a new system build... can anyone throw any light?
BTW - I did try the thing about disabling firewal, no difference.
