NextPVR Forums

Full Version: minor npvr bugs that maybe ought to be fixed before it's out of beta
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
This is a list of small-ish bugs that have been reported in the past but have escaped being fixed (though at least in one case it's not for lack of effort by sub). These are the sorts of things that are fine in beta software, but ought to be dealt with as npvr appears to be approaching a non-beta 2.0 release and a final name.

1. Resume position bug - first skip after resuming playback jumps back to 12:48. I *think* this only affects .ts files with Timing.Info.

2. Wrong date displayed when Ready Recordings are sorted by Date Descending - the displayed date is the date of the earliest recording in the group, but it should be the latest recording (which is what the text label says).

3. Recurring Recording in progress during EPG update gets duplicated - the duplicate recording begins as soon as the recording schedule is reloaded.

4. Auto-deleted recording removed from database, but not physically deleted if it is being watched at the time of deletion; this results in orphaned recording files taking up extra space on the drive. (I'm not certain this has been reported before)

5. @currentTime not available during video or recording playback (ok, maybe this isn't so much a bug as an omission, but it ought to be available)

I could swear there were a couple more, but that's all I can think of for now.
johnsonx42 Wrote:2. Wrong date displayed when Ready Recordings are sorted by Date Descending - the displayed date is the date of the earliest recording in the group, but it should be the latest recording (which is what the text label says).
This is fixed in the next release.

Quote:3. Recurring Recording in progress during EPG update gets duplicated - the duplicate recording begins as soon as the recording schedule is reloaded.
Do you have any more details on this?

Quote:4. Auto-deleted recording removed from database, but not physically deleted if it is being watched at the time of deletion; this results in orphaned recording files taking up extra space on the drive. (I'm not certain this has been reported before)
This was intentional. GBPVR had the same behaviour.

What would you have wanted it to do in this scenario?
#2: cool
#3: I originally posted about it here, with logs: http://forums.nextpvr.com/showthread.php...duplicated It still behaves the same way
#4: it should attempt the file deletion first; if it fails because the file is held open (presumably because it's being watched), then it shouldn't remove the entry from the database either. just removing the entry from the database without deleting the file makes matters worse; far better to do nothing if the file is locked.
I just realized I do also have a current example of #3:
The sunday morning episode of Poker After Dark runs from 3:02am to 4:02am. The EPG update runs at 4:00am. So first it starts the recording:
Code:
2010-12-12 03:02:00.149    [DEBUG][7]    About to start recording (37731): F:\Recordings\Poker After Dark\Poker After Dark_20101212_03020402.ts
....building graph, tuning, blah blah blah....
2010-12-12 03:02:01.258    [DEBUG][7]    Started recording (37731:F:\Recordings\Poker After Dark\Poker After Dark_20101212_03020402.ts)
then just before the recording ends, it begins the EPG update, and 30 seconds later the recording ends:
Code:
2010-12-12 04:01:29.373    [DEBUG][8]    About to update EPG
2010-12-12 04:01:29.373    [DEBUG][8]    Updating EPG...
2010-12-12 04:02:00.155    [DEBUG][7]    Stopping recording (37731). Past end time of recording.
2010-12-12 04:02:00.155    [INFO][7]    DigitalRecorder.StopStream() handle: 136
but then during the epg update, it matches the same episode again, and schedules a whole new recording:
Code:
2010-12-12 04:02:52.041    [INFO][8]    UpdateRecurringRecording(75, 'Poker After Dark'):
<Rules>
  <EPGTitle>Poker After Dark</EPGTitle>
  <ChannelOID>6947</ChannelOID>
  <ChannelName>NBC-4LA</ChannelName>
  <StartTime>2010-09-07T09:05:00.0000000Z</StartTime>
  <EndTime>2010-09-07T10:04:00.0000000Z</EndTime>
  <PrePadding>0</PrePadding>
  <PostPadding>0</PostPadding>
  <Quality>0</Quality>
  <Keep>3</Keep>
</Rules>

2010-12-12 04:02:52.123    [DEBUG][8]    LoadListingsMatchingTitle(channel=6947,title=Poker After Dark)
2010-12-12 04:02:52.129    [DEBUG][8]     - Potential episode at: 12/12/2010 3:02:00 AM
2010-12-12 04:02:52.129    [DEBUG][8]       ...check IsValid()
2010-12-12 04:02:52.129    [DEBUG][8]       ...scheduling episode
and then finally, when it reloads the recording schedule it loads the new recording, then sees it's too late and marks the new recording failed:
Code:
2010-12-12 04:03:14.977    [DEBUG][7]    Reloading recording schedule
2010-12-12 04:03:15.016    [DEBUG][7]    Requesting wake up for 'RecordingOID38020' at 12/12/2010 3:00 AM
...the rest of the wakeup list...
2010-12-12 04:03:15.042    [DEBUG][7]    Marking recording (38020) as 'Recording service not running at recording time'
this happens to be a special case where the recording is in progress when the epg update starts, but ends before the epg update completes. if the recording hasn't ended by the time the recording schedule reloads, it will dutifully start recording the same show again.
oh, here's a more normal case, I didn't realize this one was here. Planet Earth starts at 4:00am, and then starts again at 4:01:50 after the EPG update finishes.
johnsonx42 Wrote:1. Resume position bug - first skip after resuming playback jumps back to 12:48. I *think* this only affects .ts files with Timing.Info.

I'm experiencing this issue on almost every recording I try to resume. It only seems to happen on .ts recordings but i haven't had time to investigate. I hope it gets fixed soon as it's pretty annoying when it happens. I also get some skips that are extremely laggy (ie. 15-20secs before it does anything) and i've had the odd couple lock completely - again, only seems to happen with .ts and changing the decoder doesn't make any difference.
I'd like to add fixing the initial video aspect ratio for playback of .mpg on WinXp using VMR7 and VMR9. This patch fixed it for overlay.

http://forums.nextpvr.com/showthread.php...post394930

Thanks.
Any news on no.5 - displaying @currentTime ?

I tried updating video.xml with
Code:
<Element name="Timeline" location="10,93.05" size="80,8.5">
        <RoundedRect location="0.2,0.2" size="99.6,100" fillColor="BaseColor2" borderColor="Accent2_Vertical_FadeOut" radius="2.32" borderWidth="0.15"/>
        <RoundedRect location="0.2,0.2" size="99.6,100" fillColor="Base1_Vertical_FadeOut" borderColor="Transparent" radius="2.32" borderWidth="0.15"/>
        <Text text="@position" location="4,23.18" size="15,33.99" font="Title3Minimum"  borderColor="Border2" outlineWidth="1" align="Left" valign="Center"/>
        <Text text="@duration" location="81,23.18" size="15,33.99" font="Title3Minimum"  borderColor="Border2" outlineWidth="1" align="Right" valign="Center"/>    
        <Image name="timelineBar" source="@timelineGraphic" location="15.45,24" size="69.1,24.81" />
        <Rect location="15.45,24" size="69.1,24.81" fillColor="Base1_Vertical_FadeOut" borderColor="Border2" borderWidth="0.07"/>
        <Rect location="15.45,24" size="34.6,24.81" fillColor="Base1_Menu_Horizontal_FadeIn" borderColor="Transparent" borderWidth="0"/>
        <Rect location="50,24" size="34.6,24.81" fillColor="Base1_Menu_Horizontal_FadeOut" borderColor="Transparent" borderWidth="0"/>

[I]        <Text text="@dateTime" location="0,0" size="100,100" font="DefaultMinimum" align="Center" valign="Center"/>[/I]
    </element>

which results in the text "@dateTime" being displayed on the timeline

and this....
Code:
<Element name="MetaData" location="0,57.17" size="100,43.6">
        <Rect location="0,37.08" size="100,62" fillColor="BaseColor2"/>
        <Rect location="0,37.08" size="28.68,0.57" fillColor="Accent1_Horizontal_FadeIn"/>
        <Rect location="28.65,37.08" size="71.35,0.57" fillColor="Accent1_Horizontal_FadeOut"/>            
        
        <Text text="@title" location="17,38.63" size="81.45,10" font="Title1"  borderColor="Border2" outlineWidth="1" align="Left"/>
[I]        <text text="@currentTime" location="0,35" size="96,100" font="Yellow" align="Right"/>[/I]
        <Text text="@description" location="17,48.63" size="81.45,33.99" font="DefaultSmall"  borderColor="Border2" outlineWidth="1" align="Left" wrap="true"/>
        <Image source="@coverArt" location="1.55,0" size="13.91,74" fixedAspectRatio="true"/>
    </Element>

which results in an exception.

Any ideas?
Just a few days ago I'm pretty sure I saw sub say he's added support for that in the next release.