2013-12-14, 07:34 PM
Yes the exe opens up with 7zip. I overwrite ax files on the fly without restarting services too.
Martin
Martin
2013-12-14, 07:34 PM
Yes the exe opens up with 7zip. I overwrite ax files on the fly without restarting services too.
Martin
2013-12-14, 07:43 PM
It does look like these changes to both NPVRTSMon.ax and NPVRTSWriter.ax were the only updates to those files since 3.1.1, and they shouldn't interact with any other changes elsewhere. So there should be no downside to backrev'ing either or both while keeping the other 3.1.1R1 files.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2013-12-14, 07:47 PM
Cool, then when I get back to town I'll first try the registry tweak, then overwriting the old .ax filters from the 3.1.1 install.
Thanks loads for all the pointers, I'd be lost without them.
2013-12-15, 04:33 PM
Are you running a 64 for 32 bit version of Windows? XP/Vista/Win7/Win8?
2013-12-15, 04:36 PM
32 bit XP SP3, all current security updates applied, thanks.
2013-12-15, 04:43 PM
Hi sub, the key bits of my problem are up in post #16. In a nutshell, analog Timing.info seems OK but digital Timing.info ends up with 0 msec for every entry, causing NPVR to throw a div/0 exception when I try to skip forward.
Apparently I'm the only one with this problem. I plan to try the registry tweak you added for johnsonx42 to see if that improves my skips; if not then overwrite the straight v3.1.1 versions of the .ax filters (currently running the R1 rollup versions).
2013-12-15, 04:50 PM
Can you see if this patch fixes it?
2013-12-15, 05:01 PM
sub Wrote:Can you see if this patch fixes it? Will do, thanks! Should I simply overwrite this filter with no other changes, or should I attempt the registry tweak as well as this patch? I won't be able to try it for another 6-8 hours, after I get back to town.
2013-12-15, 05:14 PM
Just overwrite the file.
2013-12-15, 06:32 PM
sub Wrote:Can you see if this patch fixes it? Was able to test this remotely, somewhat. Overwrote NPVRTSMon.ax, recorded some ATSC from the same channel as before. Got the following Timing.info: Code: 0,0 I then added the timing registry tweak, re-started the recording service, and recorded a couple minutes of the same show. Got the following Timing.info: Code: 0,0 I can't really test the Skip function remotely. What do you guys think? Seems odd that my system can't use timeGetTime() at all. |
|