Recording made but marked as failed

[StevHodge]

I persistently get the following problem:

A recording is marked as failed, but in fact is there. Ie the recording service has started on time (and it shows up if you look at the status when the machine is actually recording), but the user interface doesn't seem to know it. I either have to manually import the program, or treat it is as part of the video library. This doesn't always happen - perhaps one time in two

I had the problem with version 99.7 and it is still there with 1.016. Sub said he could see no reason last time round. This is the same whether I run PVRX2 or GBPVR

Could some of you experts have a look at my logs and see if you can see what is wrong. They relate to a recording on 5th November at 18.30 of a programme called Strictly Come Dancing - Take two on BBC2.

I don't know if it could be related but quite often my machine won't come out of stand-by to start recording at all. In this case I get a failure which really is a failure. I am 'working around' this at present by not letting it go into stand-by at all, which is not very green I am afraid

I am running Media Centre Edition with the latest roll up installed (No 2)

[sub]

2007-11-05 19:05:00.390 VERBOSE [5] RecordingStatus is now RecordingStatus.RECORDING_COMPETED
2007-11-05 19:05:00.390 VERBOSE [5] RecordingFactory.save()

I'm not really sure. It certainly looks like it marked the recording as 'ready' and successfully save it to the database. I'm guessing you dont have a reproducible set of steps?

[StevHodge]

Sub,

No I am afraid I can't reproduce the steps. Is there any way I can tweak the logging so as to see what happens??

Note that whatever happens seems to happen at the start of the recording, as the program never shows up as 'recording' in the user interface during the recording time

[StevHodge]

It may be that it only behaves like this for the first recording after a 'cold start' of the machine. Am checking, will revert

[gEd]

what are you doing in your postprocessing.bat? are you running comskip, addepisode or renamerecordings? If so, I recall helping someone to fix this problem by adding a sleep command before the file rename utility.

[StevHodge]

Not running postprocessing.bat at all. Not due to cold start either. Suspect it may be some oddity in the dirctory for the recording in question. I deleted it and all the recordings and it seems OK for new recordings, for the moment