recording service not running at recording time

[mvallevand]

You shouldn't have known, but I did tell you to zip it in my first response.

I am thinking your laptop was sleeping or hibernating between here and here

2024-01-13 08:31:42.106 [DEBUG][10] Starting thumbnail extraction for C:\Users\Public\Videos\This Old House\Season 45\This.Old.House.S45E09.Lexington.Phased.Out.ts
2024-01-13 08:51:48.542 [DEBUG][10] Running: C:\Program Files\NextPVR\Other\ffmpeg.exe -re -y -i "C:\Users\Public\Videos\This Old House\Season

because NextPVR didn't tell the system not to sleep until here

2024-01-13 08:52:48.610 [DEBUG][10] Active...staying awake

and that is why the HDHR disconnected in between.

Some "wake" triggered this message

2024-01-13 09:00:31.241 [DEBUG][10] Marking recording (871) as 'Recording service not running at recording time'

What is unique about that is the recording was actually running.

2024-01-13 09:00:31.701 [ERROR][10] Unexpected orphaned recording found (871). Stopping it...


Do you have "Avoid duplicate recordings where possible" you keep recording and deleting the same shows. If you do might have some recordings caused by earlier conflicts, you shouldn't need to have the groundhog day re-recordings. You can email me your database npvr.db3 if you'd like.


Martin

[arlingtoner]

Why did you reschedule This.Old.House.S45E09.Lexington.Phased.Out.ts at 07:05 since it was recorded overnight?  If you see the message  "Alternative Airing - after failed original",  the file is actually still good.  When you played the earlier overnight version at 8am was it bad quality so you deleted it?

Edit: rechecking your annotated note "The recording was successful (I've watched it) but something in the Web App made me think it wasn't, perhaps a reschedule" I see you deleted it but but it doesn't explain rescheduling it.

Look like you have another 3rd version being recorded right now.

Martin

If I recall correctly, I awoke and wondered if the early morning recording had succeeded while I slept. I took the message "Alternative Airing - after failed original" as a "no." Consequently, I was surprised to find what appeared to be a good recording in the target directory. I quickly viewed it and found it to be good and deleted it because I had viewed it (I don't collect recordings) and because I wanted to make sure that the way was clear for the 8:30 recording. I had no idea about what would happen if the 8:30 recording wanted to create the same directory and file names as already existed. (As a programmer, I don't trust other programmers to code/test end cases as well as they do main stream cases :-)

I do not recall scheduling a 7:05 recording, and I can't think of a reason why I would.

From one of your comments, one of my takeaways is that I misinterpreted the "Alternative Airing..." message. It was simply stating that the recording at that time was an alternative airing, automatically scheduled for me (thank you) for something that had failed, not that the rerecording itself had failed.

As for an nth version being recorded - the more the merrier :-) I'm in a state where I do not trust that what I want recorded will be recorded, so the more recordings I can do, the more information I might have about what succeeds and what fails. If I record files that don't contribute to the line of inquiry, it is easy to delete them.

[mvallevand]

No, at 7:05 you scheduled the recording of Lexington.Phased.Out for 8:30, the one that recorded overnight which you watched and deleted at 8:00. The same thing happened yesterday with the same show as happened today

2024-01-12 14:30:55.013 [DEBUG][10] Marking recording (863) as 'Recording service not running at recording time'
2024-01-12 14:31:55.161 [ERROR][10] Unexpected orphaned recording found (863). Stopping it...

This is why I think there is a need to check the database.

Martin

[arlingtoner]

You shouldn't have known, but I did tell you to zip it in my first response.

I am thinking your laptop was sleeping or hibernating between here and here

2024-01-13 08:31:42.106 [DEBUG][10] Starting thumbnail extraction for C:\Users\Public\Videos\This Old House\Season 45\This.Old.House.S45E09.Lexington.Phased.Out.ts
2024-01-13 08:51:48.542 [DEBUG][10] Running: C:\Program Files\NextPVR\Other\ffmpeg.exe -re -y -i "C:\Users\Public\Videos\This Old House\Season

because NextPVR didn't tell the system not to sleep until here

2024-01-13 08:52:48.610 [DEBUG][10] Active...staying awake

and that is why the HDHR disconnected in between.

Some "wake" triggered this message

2024-01-13 09:00:31.241 [DEBUG][10] Marking recording (871) as 'Recording service not running at recording time'

What is unique about that is the recording was actually running.

2024-01-13 09:00:31.701 [ERROR][10] Unexpected orphaned recording found (871). Stopping it...


Do you have "Avoid duplicate recordings where possible"  you keep recording and deleting the same shows.  If you do might have some recordings caused by earlier conflicts, you shouldn't need to have the groundhog day re-recordings.  You can email me your database npvr.db3 if you'd like.


Martin

> ...I did tell you to zip it in my first response.

Quite true. My being "smart" by assuming that it only was concerned about reducing the length of attachments so they were "short" and that my text file was short already seems to have been misguided. Hopefully, my need to come to this forum will be infrequent enough that I'll have to relearn this again, sigh.

>  I am thinking your laptop was sleeping or hibernating between here and here

It certainly could have been. Microsoft's way of deciding if a device is inactive, and therefore can sleep or hibernate or whatever, differs from mine when I design operating systems. Also, I expect that I have a more active idea of what can be done by a low power situation. Consequently, I don't have a good feel for what the laptop could have been doing when asleep. Not enough to continue the recording? Or at least not fast enough to awake to end the recording successfully?

My takeaway from this is that I need to ensure that the system doing the recording is fully awake during the time of the recording. I cannot depend on recording events waking it up to successfully carry on the recording.

Let me know if it looks like I'm wrong.

Fortunately, PowerToys has a "keep awake" that I think will do what I need. I'll try it out on my next recordings.

[arlingtoner]

No, at 7:05 you scheduled the recording of Lexington.Phased.Out for 8:30, the one that recorded overnight which you watched and deleted at 8:00.  The same thing happened yesterday with the same show as happened today

2024-01-12 14:30:55.013 [DEBUG][10] Marking recording (863) as 'Recording service not running at recording time'
2024-01-12 14:31:55.161 [ERROR][10] Unexpected orphaned recording found (863). Stopping it...

This is why I think there is a need to check the database.

Martin

Which database? For what?

[mvallevand]

npvr.db3 I want to see if this issue that BrettB described https://forums.nextpvr.com/showthread.ph...#pid572376 is there.

Martin

[arlingtoner]

Where do I find it and how do I get you access to it or send a copy to you?

[mvallevand]

Sorry https://github.com/sub3/NextPVR/wiki/components so C:\Users\Public\NPVR-data\npvr.db3 and emailing it to me would be fine.

Martin