1.3.7 not successful HVR1600

[JohnInSJ]

I tried to update from previous to 1.3.7, and it was not very successful. Unable to scan/map qam with the HVR1600 (pvrx2 crash with problem dialog)

I've (successfully) reverted to the previous version for now, don't have the time to troubleshoot, but if anyone has successfully update to the latest with an HVR1600 with clear-qam channel scanning working without crash, I'd love to hear about it.

[dennit]

I tried to update from previous to 1.3.7, and it was not very successful. Unable to scan/map qam with the HVR1600 (pvrx2 crash with problem dialog)

I've (successfully) reverted to the previous version for now, don't have the time to troubleshoot, but if anyone has successfully update to the latest with an HVR1600 with clear-qam channel scanning working without crash, I'd love to hear about it.

I can't make the upgrade yet either - I crash 5 seconds after trying to watch live with a psiparser.ax error. sub thinks my problem is related to the source, and as soon as I get a chance, I'm going to get him some data to look at (after I've spent some more time defining my problems)

However, I've got a 1600 connected for QAM. I did several scans under 1.3.7 and compared results to scans done under 1.2.13. I did get some crashes under 1.3.7, but when it didn't crash, the scan.cache files were nearly identical under both. The only difference I saw was that 1.3.7 had some 0:0 numbers for all channels where 1.2.13 had numbers. I suspect that the old scan.cache files would be perfectly usable under 1.3.7. You may want to try them.

I did see a post from Whurlston regarding differences in scan'cache that relate to multirecording, but I didn't get far enough into testing to see such diffs.

[sub]

I tried to update from previous to 1.3.7, and it was not very successful. Unable to scan/map qam with the HVR1600 (pvrx2 crash with problem dialog)

I've (successfully) reverted to the previous version for now, don't have the time to troubleshoot, but if anyone has successfully update to the latest with an HVR1600 with clear-qam channel scanning working without crash, I'd love to hear about it.

If you can do a scan, then zip and attach the config.exe.log and config.exe-native.log then I'll take a look for you.

[steveum]

I had some similar problems with 1.3.7 with my HVR-1600. After upgrading from previous version, the scan seemed to work fine with 1.3.7. My system hard drive failed, so I had to total rebuild my system. When I installed 1.3.7 as a fresh install, the QAM scan would never find any channels. I went back to 1.2.13. The scan worked fine again. I was also having problems with back to back QAM recordings with 1.3.7. These problems also went away by reverting to 1.2.13.

[imagn]

I was also having problems with back to back QAM recordings with 1.3.7. These problems also went away by reverting to 1.2.13.

I have also had problems with back to back recordings and am just wonndering what your issue was mine is that i sometimes get zero byte recordings, even though the tuner shows it is recording the show, this is intermittent and am not sure if it is specific to one or multiple channels. (mulitrecordings .ts files are how it is set up)

I have also had issues with scanning in 1.3.7 where 1) I wasnt able to get a scan to find any channels, it would just go through the scan really fast, and 2) when i got it to work it would crash

Item 1) was a driver problem and i cleared the drivers with the hauppauge clr util and then reinstalled

Item 2) I eventually got a scan to complete and am not sure why it failed as i was able to scan again without any issues

[sub]

I had some similar problems with 1.3.7 with my HVR-1600. After upgrading from previous version, the scan seemed to work fine with 1.3.7. My system hard drive failed, so I had to total rebuild my system. When I installed 1.3.7 as a fresh install, the QAM scan would never find any channels. I went back to 1.2.13.

If you can post 1.3.7 scan logs, I'm happy to look into it for you.

[steveum]

I have logs for the back to back recordings issue. They are attached to this thread I posted a while back.

http://forums.nextpvr.com/showthread.php?t=38841

I don't have any logs for the scan though. I am currently backed off to the previous release. I suspect if I upgrade, the scan will behave OK given that I only saw that issue when I installed 1.3.7 fresh (no upgrade). I am a little reluctant to upgrade right now. I was getting a lot of recordings on the wrong channel. I am hoping that issue can get resolved first.