Recordings going into "Manual Recording" folder

[smeghead]

Hi All

I updated GBPVR to 95.11 and, at the same time, I installed the Christmas skin. Since then I have noticed that some of my scheduled recordings are placed into a "Manual Recording" folder. In GBPVR they appear to have "failed" to record. See attached pics and you'll see what I mean.

This does not happen for all recordings, most are OK. It also isn't channel specific as I've had the same named programme on the same channel (for those in the UK it's Coronation Street on Wednesday and then Friday night) one was OK the other put into the Manual Recording folder. Neither programme had another scheduled recording immediatelly before / after it.

Also, I do not use CDK Scheduler.

BTW, I haven't posted earlier as I've been away for the week and just catching up.

Is this a known issue?

[reven]

yeah i just noticed that too, i figured they failed for some strange reason. this was prior to 0.95.14 (errr what ever the latest version is)

not sure if the problem is fixed in that release thou.

[smeghead]

I remembered that in my postprocessing.bat file, as well as running comskip, I "echo" out the 2 parameters to a postprocessing.log file. The entries are:
"C:\GBPVR\My Recordings\Manual Recordings\Lizzie McGuire_20051204092500.mpg" recorded on channel 724

So GBPVR believes that they are "manual recordings".

Does anyone know why the manual recordings folder is not shown in GBPVR?

reven: do you use the Christmas skin?

Out of interest I have also included below my postprocessing.log entries for Coronation Street on Wednesday and Friday
"C:\GBPVR\My Recordings\Manual Recordings\Coronation Street_20051130193000.mpg" recorded on channel 103
"C:\GBPVR\My Recordings\Coronation Street\Coronation Street_20051202_19302000.mpg" recorded on channel 103

I do this because I noticed that the filename was a different format. Notice in the latter, 8pm is represented as "2000" but in the first it is "00". There is also an underscore between the date and time in the latter.
This may be relevant I don't know.

Thanks again

[sub]

I think I have found the cause of this. This has been possible with in all v0.95 builds.