error in recording-dump.xml

[Koenie]

The prostpadding times are not reflected correctly in recordings-dump.xml and also not correctly imported when reimporting.

When exporting the postpadding field contains the same data as the prepadding field. When importing all postpadding fields in the database are zero. I have seen this with the 1.1.5 version, no idea whether this has always been like this or not.

[sub]

Right you are. I'll make sure this is fixed for the next release.

I have seen this with the 1.1.5 version, no idea whether this has always been like this or not.

Up until 1.1.5 the recording-dump.xml only contained "ready" recordings, so it wasnt applicable back then.

[Koenie]

Unbelievable it took you a full 14 minutes, that are 840 seconds to reply!!!:confused:

Just how do you manage this with everybody on the forum? My boss would be extremely happy when I managed this.

edit: So I got lucky after my system crash I could just pick up my backed-up recording-dump.xml and restore virtually everything!

[martint123]

So I got lucky after my system crash I could just pick up my backed-up recording-dump.xml and restore virtually everything!

I've started emailing it to one of my gmail accounts daily as it is such a life saver.

[Koenie]

I did not go this far, just on my home back-up NAS did the trick too.

[imilne]

Hi sub,

Did you ever get a chance to do anything about this, because I seem to be seeing the same problem with 1.3.11.

eg, an entry of:
<prePadding>5</prePadding>
<postPadding>10</postPadding>

imported from recording-dump.xml will end up in gbpvr's recurring list (or an export) showing:
<prePadding>10</prePadding>
<postPadding>0</postPadding>

Also, when attempting to manually edit the entries within gbpvr I find I can also do so for the first three or four. Any further entries on the recurring list don't appear when I highlight them and select Update. You can see the window "trying" to appear (it's 90% transparent) but any further key presses make it disappear again.

Thanks

[sub]

Sorry, no I didnt. Padding is ignored. I'll fix it in a future release.

[imilne]

Sorry, no I didnt. Padding is ignored. I'll fix it in a future release.

Ok, no worries. I worked around it in the short term by editing the values in gbpvr.db3 directly.

[OrakelJos]

Sorry, no I didnt. Padding is ignored. I'll fix it in a future release.

I just had to do a fresh install of 1.4.7 after a crash of my update from 1.3.11. The problem is not (yet?) solved because after importing of my recordings dump all the 33 recurring items have wrong pre- and postpaddings.

[sub]

Correct - padding is ignored. I'll fix it in a future relese.