0 Byte recordings != fail???

[psycik]

Hi sometimes get some recordings that don't work....i.e. they are 0 byte, but still listed as successful.

Had one last night, and have isolated it in the logs..

I can't see anything in there though pointing to an error.

It's the blind date for 5:30 to 60 am that has supposedly gone though but has made a 0 byte file..

[sub]

2007-10-25 05:30:29.485 VERBOSE locked=0 present=0 strength=0 quality=0

It looks like the device failed to lock onto a signal, so no data was every delivered to be written to disk.

You could see if adding the following in config.xml helps:

<BDASubmitTuningRequestTwiceOnRecord>true</BDASubmitTuningRequestTwiceOnRecord>

[psycik]

Bugger, already there, and already turned on....

Before going to bed last night the wife mentioned it on one of her recordings, and I went to the same channel, and couldn't get it to start....but then tried another channel that works fairly well, that came up....then i was able to "jump" to the channel i previously had problems with and it worked.

Maybe I need a
<BDASubmitTuningRequestHowManyTimeShouldITryToRecordForPsycikOnRecord>8</BDASubmitTuningRequestHowManyTimeShouldITryToRecordForPsycikOnRecord>

[sub]

You might already this one, but also set:

<SecondChanceRecording>true</SecondChanceRecording>

If it notice the recording isnt growing after 20 seconds, then it'll attempt to restart it.

[psycik]

yes also set.

Actually in my logs you can see that happen at 5:30:27 but then no messages at all until it "stops" the non existent recording at 6:05.

Should we expect to see some tuning messages? hmm guess not, looked at some older logs....I thought I remembered messages coming out every so often with the tuning status.

[psycik]

Funnily enough I've just gone to the tv giude and ctrl-p on the same channel and it worked first time - and not using live preview, this would be the same action as start a recording correct??

Dunno why, sometimes works sometimes not...I wonder if my silly config tag may not be so silly, and if I could have a way of having more chances???

[stustunz]

is this from sat?

sorry keep forgetting you have cable should read before typing

[psycik]

Any potential updates for this issue. I seem to have at least one per day of recordings that are 'successful', but have no file size... I just wonder if there might be a possibility of 'n' retries rather than just the 2...

[sub]

Sorry for the slow update. I unexpectedly had to leave town for the last day.

Is there any pattern to it? ie first recording after automatically returning from hibernation or similar?

If we cant find any further pattern, then remind be during the next pre-releases and I'll add an 'n' retries capability.

[psycik]

Sorry for the slow update. I unexpectedly had to leave town for the last day.

Is there any pattern to it? ie first recording after automatically returning from hibernation or similar?

If we cant find any further pattern, then remind be during the next pre-releases and I'll add an 'n' retries capability.

Don't know about a pattern.

I would have said that it was the first after some delay (I dont use hibernation). My wife Tapes (like the old school term ) Sunset tan off E!, and that runs two episode back to back, normally the first doesn't work and the second does. But the other one that fails a bit is blind date each morning at 5 am, nothing around it and it's a single. The third one is mythbusters of discovery that fails quite a bit. Funnily enough both sunset tan episodes recorded this morning back to back...

But its been pretty idle for recordings today and set a couple of random recordings (start on, let it go for a bit, cancel it, start something else, etc) and they've all been going....ahhh, finally got it to "fail". So cancelled that, deleted te 0 byte recording, and started it again...now it's working...(file size growing).


So there doesn't seem to really be a pattern. Will post the logs....and BTW I did all the scheduling/cancelling from EWA not from PVRX2. But that shouldn't really make a difference, I imagine it's the same api calls now.