1.5.33 beta available (15th October)

[Reddwarf]

I checked/unchecked this box and can ever reach the NEWA Web Page. This could explain my problem with the GB-PVR streaming via EWA...

Did you restart Nrecord after unticking web server?

[Barsk]

Oh!
What an impressive changelist from the guy that was snowed over with daytime job (Do you get snow in the NZ?)
I will especially enoy the improvements with Live TV on clients and PCH. And of course the ISO playback! And the audio stuttering issue... and the... Wow the list goes on!

Great work as always Sub, and very much appreciated! Awesome is the word!

Btw, I lack some sort of notification system that will let you know when a new release is out. I missed this one with two days...
Easisest maybe would be a closed sticky thread that one can subscribe to that Sub bumps when new releases are available. Just a thought. The NMT forums have one such for firmware releases.

[johnsonx42]

quick bump to put the 1.5.33 anouncement back on top

Also, I find 1.5.33 to be a MAJOR improvement over 1.5.31. 1.5.33 resolved several issues on my HTPC that I had assumed were non-NPVR related. First, and perhaps weirdest, I was getting a serious clock drift as much as 4 minutes ahead per day - it never occurred to me to pin this on NPVR, but after installing 1.5.33 and changing nothing else the clock now keeps perfect time again. Also, when skipping ahead or back in a recording, playback would often freeze for many seconds or even forever; I figured that was decoders or video driver, yet again installing 1.5.33 has completely eliminated that problem.

Finally, I (among others) had noted a rather high CPU utilization by NRecord.exe even when it was doing nothing at all, causing my fans to spin up a lot and other issues as well; now with 1.5.33 NRecord.exe idles at 0%.

It does occur to me that all 3 issues could have been related somehow. Either way, hooray for 1.5.33!

[Barsk]

Btw, I lack some sort of notification system that will let you know when a new release is out. I missed this one with two days...
Easisest maybe would be a closed sticky thread that one can subscribe to that Sub bumps when new releases are available. Just a thought. The NMT forums have one such for firmware releases.

It occurred to me that one can actually subscribe to the whole "NPVR Announcements" forum! That solves the notification issue totally.

[smiffypr]

I've just replaced .31 with .33, and the signal strength percentage which was shown on settings>status (not on device status from the tray icon though) has disappeared. I found it useful.

[smiffypr]

[QUOTE=ShiningDragon;I checked/unchecked this box and can ever reach the NEWA Web Page.[/QUOTE]

I found this too, I could get on without having to supply username and password. I found in the config-web.xml (in C:/Documents and settings/All Users/Application Data/NPVR) there is a parameter <autoLoginNetworks> which had a set of IP addresses which it would allow unrestricted access from. I changed the IP addresses to False so the line is now
<autoLoginNetworks>False</autoLoginNetworks>
restarted NPVR service, and I now have to login as before.

[#66]

Hmmm, I get NSIS error on my pvr pc when trying to install.

The same downloard works on 3 other pc without any problem.

[johnsonx42]

... I was getting a serious clock drift as much as 4 minutes ahead per day - it never occurred to me to pin this on NPVR, but after installing 1.5.33 and changing nothing else the clock now keeps perfect time again.

I guess I spoke too soon on that one, the clock drift is back. It didn't make sense that NPVR would have anything to do with that, but the clock honestly did keep perfect time for a couple of days after installing 1.5.33. I'm still much happier with 1.5.33 than I ever was with 1.5.31; too bad that doesn't seem to be true for everyone.

[Barsk]

Sounds odd that N-PVR could induce clock drift. My guess is that your clock crystal is bad and that is causing the drift. The time server sync have kept the clock in check for some time, but sometimes the time sync fails and I guess that is when your drift starts to kick in. I think that when there is too much difference between the clock setting and the time server, the time server refuses to set your clock, and that is when drift becomes permanent. Maybe the clock is powered by the battery on the motherboard and that needs to be replaced. I am just speculating though.

I remember my own watch behaving very odd when the battery was very low. With a new battery everything was perfect again.

[stustunz]

yip dead motherboard battery will be your problem