2006-07-17, 08:56 PM
I didnât' find anything about this behaviors.
My 97.13 installation has NativeUtilities and GBPVRBackendCommon modified.
The first issue
Yesterday night recording went stopped early and comskip didn't process the recorded file.
Today I checked the file by watching it in GBPVR and all was perfect.
Then I decided to make comskip process the file so I dragged it over comskip.exe prog. When work is done I tried to watch it again but GBPVR showed ERROR on it in the list of available files.
The reason was that gbpvr.db3 the link to the file was lost.
Not a big issue since after the link has been re-established error disappeared but just to raise the problemâ¦
The second issue
I always used my two Hauppauge HVR-1300 cards only as DVB-T tuner.
Today just for fun Iâve tried to set them up as analog TV receivers.
Set up as Roslyn cards were OK but not as Hauppauge HVR-1300 (analog). Qite weird since they seem share the same configuration.
At the end I got working three digital (two HVR-1300 and one HVR-1100) and two analog tuners.
I set three recordings to start shortly. Two of them were on the analog tuners. The first recording started on DVB-T tuner (HVR-1100) the second on analog1 tuner and the third was missed. GBPVR reported three recordings were running while Recording Status reported only two active recordings.
I tried to stop the recordings in GBPVR TV guide. The first (HVR-1100) stopped properly, the second didnât stopped (as reported by TV guide) until I stopped the third.
Attached are some logs I kept two hours later (sorry)
My 97.13 installation has NativeUtilities and GBPVRBackendCommon modified.
The first issue
Yesterday night recording went stopped early and comskip didn't process the recorded file.
Today I checked the file by watching it in GBPVR and all was perfect.
Then I decided to make comskip process the file so I dragged it over comskip.exe prog. When work is done I tried to watch it again but GBPVR showed ERROR on it in the list of available files.
The reason was that gbpvr.db3 the link to the file was lost.
Not a big issue since after the link has been re-established error disappeared but just to raise the problemâ¦
The second issue
I always used my two Hauppauge HVR-1300 cards only as DVB-T tuner.
Today just for fun Iâve tried to set them up as analog TV receivers.
Set up as Roslyn cards were OK but not as Hauppauge HVR-1300 (analog). Qite weird since they seem share the same configuration.
At the end I got working three digital (two HVR-1300 and one HVR-1100) and two analog tuners.
I set three recordings to start shortly. Two of them were on the analog tuners. The first recording started on DVB-T tuner (HVR-1100) the second on analog1 tuner and the third was missed. GBPVR reported three recordings were running while Recording Status reported only two active recordings.
I tried to stop the recordings in GBPVR TV guide. The first (HVR-1100) stopped properly, the second didnât stopped (as reported by TV guide) until I stopped the third.
Attached are some logs I kept two hours later (sorry)
[SIZE="1"][COLOR="Navy"]
1st
Silverstone LC20 case | ASUS M2V | AMD Athlon 64 3200+ AM2| RAM 4GB DDR2 800 | HD 160GB IDE + (SATAII 300GB) | Hauppauge: 3x HVR-1300 - 1x HVR-1100 | 2 x Hauppauge MVP | 3 x AtlantisLand PL200 | WinXP IT SP3 | MCE 2005 Remote | GB-PVR v1.4.7 | Cyberlink Mux | 2 x clients Intel D945GCLF2 | Win FLP SP3 [/COLOR]
_____________________
[COLOR="Navy"]2nd
Intel D945GCLF2 | RAM 2GB DDR2 | HD 500GB SATAII) | Hauppauge Nova T500 | GB-PVR v1.3.11 | ATI Mux | Microsoft XP + SP3 + hotfix kb969238 and this [/COLOR][/SIZE]
1st
Silverstone LC20 case | ASUS M2V | AMD Athlon 64 3200+ AM2| RAM 4GB DDR2 800 | HD 160GB IDE + (SATAII 300GB) | Hauppauge: 3x HVR-1300 - 1x HVR-1100 | 2 x Hauppauge MVP | 3 x AtlantisLand PL200 | WinXP IT SP3 | MCE 2005 Remote | GB-PVR v1.4.7 | Cyberlink Mux | 2 x clients Intel D945GCLF2 | Win FLP SP3 [/COLOR]
_____________________
[COLOR="Navy"]2nd
Intel D945GCLF2 | RAM 2GB DDR2 | HD 500GB SATAII) | Hauppauge Nova T500 | GB-PVR v1.3.11 | ATI Mux | Microsoft XP + SP3 + hotfix kb969238 and this [/COLOR][/SIZE]