What useage scenarios could impact a scheduled recording working

[mixedup]

will do (i.e. try this out) - thanks

BTW - You didn't have any ideas re how to track down the cause of the scenario whereby occasionaly after going "Live TV" the picture doesn't come up (i.e. I'm not sure whether this is a gb-pvr or tuner card issue)

[sub]

post the logs showing this and I'll see if I can spot anything.

[mixedup]

Hi sub,

Here are the error logs associated with the issue I mentioned of "viewing tv live" sometimes doesn't work and I get a black screen. I haven't put in place the Cyberlink mux you mentioned yet, rather wanted to shoot you these logs first. I basically went "Live TV" and then saw channel 10 within a couple of seconds OK. Then I went program guide and went to WATCH a show on channel 9, after which the picture never did come up on the screen (only black).

Logs attached.

Looking at the logs and comparing the successful case versus unsuccessful I note in the latter I saw the following log entries directly after I went to WATCH channel 9 (when the screen would have been black and I was waiting). Is this an issue?

24/10/2005 9:15:01 PM.153 VERBOSE [2] flushDatabaseConnections()
24/10/2005 9:15:01 PM.163 VERBOSE [2] RecordingFactory.loadSchedule()
24/10/2005 9:15:01 PM.163 VERBOSE [2] getValue cached value: /settings/AutoRemoveMissingRecordings : true
24/10/2005 9:15:01 PM.173 VERBOSE [2] getDatabaseConnection() creating new connection
24/10/2005 9:15:01 PM.193 VERBOSE [2] Received event code: 14
24/10/2005 9:15:30 PM.405 VERBOSE [2] RenewLease: 1

I did want 30 seconds or so and chanel 9 never did come up so I cancelled out.


Thanks again.

PS Will try the mux you suggested next.

[mixedup]

Have also (i.e. see my previous post just before this one too) put the Cyberlink mux in place per your suggestion. So far it seems to give me more reliable LIVE TV (no black screens yet after going to a live channel). Will test over the next few days.

BTW - With the mux checker I can see it's the right one, however in GBPVR config I selected BDA Multiplexer = Cyberlink (i.e. I'm assuming I'm choosing the Cyberlink mux I just installed/registered).

[sub]

In the logs it looks like your card failed to lock onto a signal.

[mixedup]

Thanks sub,

- in this case would this explain what I was seeing in gbpvr, i.e. everything looks ok but the recording file is a 6kb file?

- just so I can become more self-sufficient which log entries implied this?

- I'll try out some independant TV viewer software (maybe digital watch) to try to replicate then jump on a Twinham forum - this locking problem is not specifially related to the decoders or mux I use in gbpvr is it? i.e. if I try to replicate this behavior in another piece of software I wouldn't need to use the same decode or mux?


Thanks again

[sub]

- in this case would this explain what I was seeing in gbpvr, i.e. everything looks ok but the recording file is a 6kb file?

Yes, a DVR-MS file starts out at 6kb before it starts recording and information from the device.

- just so I can become more self-sufficient which log entries implied this

21:15:00.372 VERBOSE locked=0 present=0 strength=0 quality=0

this locking problem is not specifially related to the decoders or mux I use in gbpvr is it?

I wouldnt think so.

[mixedup]

Hi Sub,

Would you be able to give me a pointer to which API set and method I can use to write a small test app to set the tuner? This may be the best way for me to track down when/why the tuning request fails occasionally.

I can use Java JDK 1.5 or Visual Studio 2005 Beta 2 C#.

Given the BDA drivers are a microsoft thing (I think I read this) should I assume the easiest approach would be to somewhere get a copy of a BDA C# client class library which I can access from with a C# project.

I suppose I'm looking for a way to tune to a channel then, check the locking status, store results, and perform this periodically to see when things are going astray. Basically the same thing that you do per the below:

21:14:32.792 INFO Initializing DVB-T tuning request.
21:14:32.792 INFO tuning@1
21:14:32.872 INFO tuning@2
21:14:32.872 INFO tuning@3
21:14:32.872 INFO tuning@4
21:14:32.872 INFO tuning@5
21:14:32.902 INFO tuning@6
21:14:32.912 INFO tuning@7
21:14:32.912 INFO tuning@8
21:14:33.033 INFO tuning@8
21:14:33.033 VERBOSE getSetting(BDAMultiplexer)
21:14:34.084 VERBOSE About to auto detect correct tuner filter
21:14:34.084 VERBOSE Looking for associated filter
21:14:34.104 VERBOSE - TwinHan DVBT BDA Capture Filter
21:14:34.164 VERBOSE Successfully auto detected tuner filter: TwinHan DVBT BDA Capture Filter
21:14:34.194 VERBOSE ConnectPins: 'Output1' to 'MPEG-2 Stream'
21:14:34.214 VERBOSE getSetting(EPGProcessingMode)
21:14:34.214 VERBOSE Mapping Video PID 512
21:14:34.214 VERBOSE getSetting(PreferredAudioDecoder)
21:14:34.214 VERBOSE Mapping Audio PID 650
21:14:34.214 VERBOSE getSetting(EnableTeleText)
21:14:34.565 INFO pGB->Render(p2Pin) returned -2147467261
21:14:34.695 VERBOSE locked=0 present=0 strength=0 quality=0


Tahnks

[sub]

Would you be able to give me a pointer to which API set and method I can use to write a small test app to set the tuner? This may be the best way for me to track down when/why the tuning request fails occasionally.

I think the DirectX SDK includes some BDA samples. You'll most likely need to use C++, which is what I used.

BDA code is pretty verbose, and you'll probably find you need about 1000 lines minimum to do anything.

[mixedup]

Thanks sub,

Yes this sounds overkill for me in terms of just trying to fault find.

I had the occurence again this moring. It almost seems this is occuring after there has been a lot of network (internet) activity on my PC. I'm wondering whether high network activity? Any thoughts on this? (e.g. if gbpvr client to recording service traffic was hampered at one stage could this trigger something).

What I'm seeing occasionally it "seems" is:
* high internet use (e.g.downloads overnight)
* recording fails (logs show that tuner didn't LOCK on) and 0kb file (or 6kb file created)
* afterwards, recording won't play (as it didn't work)
* when using GB-PVR to set/modify the recording schedule I get ERRORs which point at GB-PVR not being able to contact the recording service

Any ideas?

I'll attach the logs from this morning


Thansk