Report on 003

[Corey]

Install went smoothly, easily configured.

No major bugs found, this release is great

I'd like to get some feedback from Sub or other testers though on the following:

Ever since the first release when I update the EPG for the first time after a new install I have to edit my channel numbers. I think this is an issue with XMLTV, not GB-PVR. I only have to do this once though, then whenever I update the EPG again the channels numbers I set up previously work.

For example:

Channel name: 10 QVC
source channel: 1 (I edit this to 10)

Channel name: 11 GOAC011
source channel: 2 (I edit this to 11)

This is hardly a bug or an error, I was just curious if everybody is having to edit the channel numbers.

Great job Sub, not even I could find an error on this release



Sub, I should leave you a note saying that the recording error I got was my fault. I was playing around with GB-PVR launching an external app.

I wanted to see if the program was not exited normally, if GB-PVR would return to the main menu automaticly by killing the external app from the task manager (It did, great job).

I think I may have killed your recording service by mistake, causing the error, actually I am almost sure I did. #### those beta testers

So nothing should be wrong with the recording service, forcing people to reboot after installation. Unless they go around ending processes in the task manager that they shouldn't be

Great release, I'll do some more error hunting tomorrow morning when I get home from work (without killing your processes this time).

[sub]

Unfortunately there is no 'upgrade' process yet. In effect, the software and in particular the database is being replaced with each release. This database does contain the channel numbers, and as such is currently being lost with each new release of the software.

I'll eventually work out a scheme to perform upgrades, I just havn't got to it yet.

[colin]

I did experience last night when i scheduled a recording that it started and stopped immediately. Now the machine was under heary load so there could have been a combination of events going on. The scheduler process is active so i'm guessing it was either a user error or a problem invoking wintvcap.

I'll try this again this evening with a reboot of the machine and see what happens, then i'll do a fresh install and try it again.

As for the channels, I have not spent anytime yet with that section. Thats on my todo list. I also want to mess with the webservices bit. Unfortunatey my laptop and desktop are refusing to talk to each other so I'll have to figure out another way of testing that,

Cheers,

[sub]

I think WinTVCap generates a log file. It might be worth having a quick search of the hard drive to see if you can find it. It may provide invaluable clues.

You might want to hold off on the Web part until the next release. In the current release its only partially implemented.

[colin]

Forgot about the wintvcap log file.:p I'll check this when i get home.

Cheers,

[sub]

Cheers. Colin, do you work with Sun boxes? I just happened to be looking at the web server log files when you last posted. I saw Sun/Mozzila shoot by. In my day job, I do development on Sun boxes to earn a crust

[colin]

Yip i work all day on Sun boxes,

cheers,

[colin]

from wintvcap.log i have

3404 Welcome to WinTvCap ...The current date and time are: Wed Nov 19 17:11:11 2003
3404 InitInstance: CoInitializeEx(COINIT_MULTITHREADED) -- OK
3404 WndProc: Shell_NotifyIcon(NIM_ADD) -- FAIL
3404 InitInstance: CreateWindow() -- OK
3404 InitParams: iniFile "C:\KVCD\wintvcap\WinTvCap.ini" -- FOUND
3404 InitParams: RegOpenKey(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Globespan\Parameters\ivac15\Driver) -- OK
3404 InitParams: Valid arguments: -c<channel>, -p<preset> -startr:<filename>, -board:<number>, -limit:<seconds> -extra:<seconds>
3404 InitParams: Valid arguments: -minutes:<minutes> -delay:<seconds>, -digiG -quality<alias for -profile:>, -seconds<alias for -limit:>
3404 InitParams: Valid arguments: -audio:[SECTION], -profile:[SECTION], -prefilter:[SECTION], -procamp:[SECTION]
3404 InitParams: Your lpCmdLine is "-c22 -board:1 -seconds:1080 -profileVD -startr:C:\gbpvr\Capture\JustShootMe_492.mpg"
3404 InitParams: Argument -board:1 -- OK
3404 InitParams: Found -c or -p argument "22" -- OK
3404 InitParams: Found -startr: argument "C:\gbpvr\Capture\JustShootMe_492.mpg" -- OK
3404 InitParams: Argument -limit:1080 -- OK
3404 InitParams: Argument -delay:0 -- OK
3404 InitParams: Argument -c22 -- OK
3404 InitParams: iniFile [LOGGING] -- FOUND

The -limit looks wrong for a 30 minute show?

The end of the log is

3404 DoStartGraph: AddToRot() -- OK
3404 DoStartGraph: SetTimer(1080) -- OK
3404 DoStartGraph: pMediaControl->Run() at Wed Nov 19 17:11:13 2003 -- OK
3404 Tweak7115: pMediaControl->QueryInterface(IFilterGraph) -- OK
3404 Tweak7115: filterGraph->FindFilterByName("Capture&quot -- OK
3404 Tweak7115: captureFilter->QueryInterface(IAMVacCtrlProp) -- OK
3404 DoStartGraph: Tweak7115 -- OK
3404 DoTimerTick: Shell_NotifyIcon(NIM_MODIFY) -- FAIL
3404 DoTimerTick: Shell_NotifyIcon(NIM_MODIFY) -- FAIL

Running this from the command line does not work. Yet this launched from the windows scheduler does?

any ideas?

[sub]

I'll take a look at how I calculated the seconds after work. Doesn't look right.

Can you also have search from GBPVR*.log on you machine. The file I think is called something like GBPVRRecordingService.log but I'm not 100% about that name. This file may also give an indication of a failure. It is overwritten each time the recording service is started, so any useful info may be gone by now.

If you manually run WinTVCap with the arguments "c22 -board:1 -seconds:1080 -profileVD -startr:C:\gbpvr\Capture\JustShootMe_492.mpg" does it work? If you can manually start recording with these parameters, then GB-PVR should be able to record.

If it doesn't work manually, try stripping off the -board and -profile options and see if that works.

[colin]

The error in the log file (C:\WINDOWS\System32) is:

19/11/2003 17:09:46.828 INFO [5] GB-PVR Recording Service starting
19/11/2003 17:09:47.140 VERBOSE [5] SourceConfigurationContainer.LoadAll()
19/11/2003 17:09:47.968 ERROR [5] Error int SourceConfigurationContainer::LoadAll(): Could not find a part of the path "c:\temp\config.xml".
19/11/2003 17:09:48.328 ERROR [5] Stack:
at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials)
at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlTextReader.CreateScanner()
at System.Xml.XmlTextReader.Init()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlValidatingReader.ReadWithCollectTextToken()
at System.Xml.XmlValidatingReader.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at ay..ctor()
at ay.a()
at p.a()

I'm not sure where it is picking up c:\temp - this directory does not exist?

cheers,