DVB "failures" - creating second file, but no DB Link

[psycik]

This includes the multirecord patch as well??

hmm, not sure if I want to turn that back on yet until we figure out what to do with the mdapi stuff....

[sub]

Ok. Someone else might try it.

It basically not creating a new file now in this situtaion, but instead just continuing to create the original file.

[sub]

Here is a patch that allows multi-record on free to air channels, but doesnt allow it for encrypted channels.

[psycik]

Ok, have put down both of those, and just scheduled a bunch of recordings of the mdapi. Hopefully they'll all work..

I'll try and test some multi record as well.

[psycik]

hmm, not sure if that last patch is doing anything (the backendCommon one), just started a recording off cartoon network, and then started one of the box. My recording source mentions both recordings....

[sub]

If you can post your pvxr2.exe.log showing both recordings being scheduled, I'll be able to check if/why multirecord was used.

[psycik]

Here are all the logs.
I started "Little Einstiens" then "The Xfiles"

[psycik]

Actually you wont see the "Einsteins" that was in another log before I restarted, since I saw your first patch put that down, started off some mdapi recordings...then saw your second patch.

Here is the start of the "Einsteins" recording.

Code:

2008-12-15 09:50:42.828    VERBOSE    [1]    Looking for capture source to record: Little Einsteins
2008-12-15 09:50:42.828    VERBOSE    [1]    Possible capture device: DEVICE:TechnoTrend Budget C-1500 DVB-C:1
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'TCL-C1501' (DEVICE:TechnoTrend Budget C-1500 DVB-C:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@2.1
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@3
2008-12-15 09:50:42.828    VERBOSE    [1]    canRecord@exit (possible)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'PVR150-TCL' (DEVICE:Hauppauge PVR150:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'HVR3003-S2' (DEVICE:Hauppauge HVR-3000:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'PVR500FM' (DEVICE:Hauppauge PVR500 with FM tuner:2)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'PVR500' (DEVICE:Hauppauge PVR500:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'HVR3000-T' (DEVICE:Hauppauge HVR-3000:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    Checking 'HVR3000-S' (DEVICE:Hauppauge HVR-3000:1)
2008-12-15 09:50:42.828    VERBOSE    [1]    RecordingFactory.save()
2008-12-15 09:50:42.890    VERBOSE    [1]    Save(): Inserted new scheduled recording
2008-12-15 09:50:42.890    VERBOSE    [1]    Requesting recording service schedule reload
2008-12-15 09:50:42.890    VERBOSE    [1]    RefreshPendingRecordings()
2008-12-15 09:50:42.890    VERBOSE    [1]    RecordingFactory.loadSchedule()
2008-12-15 09:50:42.890    VERBOSE    [1]    getValue cached value: /settings/AutoRemoveMissingRecordings : false
2008-12-15 09:50:42.890    VERBOSE    [1]    getValue cached value: /settings/CheckForRenamedRecordings : true
2008-12-15 09:50:42.953    VERBOSE    [1]    getValue cached value: /settings/CheckForRenamedRecordings : true
2008-12-15 09:50:42.953    VERBOSE    [1]    getValue cached value: /settings/CheckForRenamedRecordings : true
2008-12-15 09:50:43.031    VERBOSE    [1]    RefreshPendingRecordings()@2
2008-12-15 09:50:43.031    VERBOSE    [1]    RefreshPendingRecordings() complete

[sub]

Can you tell me if they were a real overlap? ie, not just padding.

There is a separate bug relating to padding, that can cause this issue with trying to recording multi-records on a tuner on a different frequency. I'm working on this and should have a patch for this a little later this morning.

[psycik]

hmm ok,might has just been padding. I think einsteins was recording its padding when I started x files... I'll schedule some else later today... I have been getting the messages to say "Cancel old recording or no changes" when scheduling, which I guess it the checking multi record so that's seems to be working well.