0 Byte recordings != fail???

[psycik]

I thought I'd update in here, since it seems more related that the other discussion.

Here is running this morning, and then I was finally able to get a signal - this is back onthe 1.0.16 version. Its like the device isn't started properly, then one it has been activated, then it's fine....but that first start takes a long time.

Any way here is a fairly large set of logs were you should be able to see me trying, and then it finally works. Hope you can see something in here useful...

Code:

2007-10-28 09:11:45.062    VERBOSE    locked=1    present=1     strength=61     quality=100

Here is the first line I actually get a signal...

[psycik]

bump in case you miseed update

[sub]

The cause isnt clear to me in the logs, be I've made a change that should hopefully help.

I'll added the following setting in the next release

<BDASubmitTuningRequestAlways>true</BDASubmitTuningRequestAlways>

This tells the app to ignore the fact the device might already be on the requested frequency when a recording starts or live tv channel changes, and tells it to submit a new tuning request anyway.

[ACTCMS]

I've started getting this problem over the last week or so - nothing in my records showing any major changes to setup... could just be that I've started scheduling more recordings?
I've got 'BDASubmitTuningRequestTwiceOnRecord' and 'SecondChanceRecording' both set to true.
I had three recordings scheduled (using EWA) for today - no overlaps - three different channels - first one recorded fine - other two are zero length. Although I get locked 0, I get present 1 and values for both strength and quality, so not quite the same as psycik... so I decided to post the logs just in case it might help... fun starts at 2007-11-05 09:55:00.156

I set up two recordings this evening and both recorded fine.

Alex

[psycik]

Funny, no help, but you didn't seem to get the "the recording file looks really small so I'll kick off the recording process again"

[ACTCMS]

Funny, no help, but you didn't seem to get the "the recording file looks really small so I'll kick off the recording process again"

I noticed that too... but when I first looked at the problem a few days ago I did see a log which showed a restart due to the file being zero length - the second attempt still produced a zero length file though. I checked config.xml before I posted and it was still set.

I'm trying to think of a test setup which might find a pattern... but in the meantime I'm going to try a bit of straw-clutching and start recording to a different volume.

Alex