NextEnd v5 trial release

[mvallevand]

Odd configuration B doesn't even know to use the plugins folder for dll's so I am confused. Do you change directories in your batch file?

Martin

[VCR58]

... When you did the install did you make sure that all the dlls where installed?

If you post your new logs I might be able to give you a command line to test.

Martin

I made sure all the dlls were installed by re-copying them. Was too lazy to look for them. Probably one of those was missing instead.
Adding hostfxr.dll was for when I had Netcore installed.

I'll delete the hostfxr.dll from the plugins folder and see if it works tonight.

[VCR58]

Recorded the game tonight and Nextend worked fine without the dll in the Plugin folder. So, I guess my issue was a missing dll in the Program Files\NPVR folder.

However the recording was terrible. I'll post a different thread for this.

Thanks

[mvallevand]

At least you didn't have to listen to Baby Shark. Pretty sure the NextEnd issue was the missing dll.

Since there is extra crap that I use for development that is going unnecessarily to your nrecord.log I suggest you redirect NextEnd commands to > NUL

Martin

[VCR58]

At least you didn't have to listen to Baby Shark.  Pretty sure the NextEnd issue was the missing dll.

Since there is extra crap that I use for development that is going unnecessarily to your nrecord.log I suggest you redirect  NextEnd  commands to > NUL

Martin

Lol. I still got to hear the Baby Shark.

[BrettB]

I'm trying to get the NextEnd monitor functionality working with v5 on my Windows server to extend non-sports shows after sports on Sunday night.

This is what I've got in my PostStartup.bat file:

Code:

REM First, kill any NextEnd.exe process that might still be running from before the NextPVR Recording Service was restarted.
taskkill /IM NextEnd.exe /f

REM Next, run the NextEnd monitor process in the background to monitor the status of sports events before scheduled recordings
REM start /b "" "C:\Program Files (x86)\NPVR\NextEnd.exe" --monitor --jit --group Favorites
start /b "" "C:\users\public\NPVR-data\plugins\NextEnd\NextEnd.exe" --monitor --jit >NUL

With that file active, NextEnd Monitor process does start, but the NextPVR Recording service thread for actually doing recordings doesn't fully start up. When sub looked at my system, he said that it appears the PostStartup.bat file isn't completing so that thread hangs. But with the "start /b" it seems to me like it should be "completing". And when I add another line after that, it gets executed.h

I'm attaching a set of logs showing a startup with the script in place. You'll notice that it does not include the messages about scheduling wake ups for all of the pending recordings. Which is what I'm using to determine that it's not working right.
  logs-20191027-1807.zip (Size: 78.09 KB / Downloads: 2) If you look in the nrecord.log.3 file (from before I installed the .netCore Runtime so NextEnd wasn't running), you'll that recording thread continuing and the wakeups being scheduled.

[mvallevand]

Which option did you use for installing?

Martin

[BrettB]

Which option did you use for installing?

Martin

I installed the .net Core runtime, so option A.

[mvallevand]

Running NextPVRService and from the command line it works as expected but as a Windows service or task I see the same thing. Basically start /b or cmd /c commands will not work, maybe because of sub's hooks on stdout or maybe a dotnet thing, or even Windows changes in interactive services.

You probably need to create a hidden task for the monitor until sub can see if turning off logging allows spawning separate tasks. It actually is quite easy if you want to give it a try.

Martin

[BrettB]

Running NextPVRService and from the command line it works as expected but as a Windows service or task I see the same thing.  Basically start /b or cmd /c commands will not work, maybe because of sub's hooks on stdout or maybe a dotnet thing, or even Windows changes in interactive services.

You probably need to create a hidden task for the monitor until sub can see if turning off logging allows spawning separate tasks.  It actually is quite easy if you want to give it a try.

I think that you meant "NextPVRServer from the command line" rather than "NextPVRService and from the command line"? However, in my current case, I am doing it from a command window just using the command "NextPVRServer.exe" not from a service or a task. I'm now trying to do it on my production server which still has Windows 7 64-bit. But the first time (when sub looked at it), I was on my test server which is Windows 10 64-bit. I doubt those make a difference.

What do I need to do to set it up as a hidden task?