NextEnd V2 Pre-Release Announcement

[mvallevand]

The wiki doesn't use the (X86) variable since I wanted something 32/64 bit compatible but yours should work.

The way I tested it was to check my poststartup.bat and run

start "" /b "%PROGRAMFILES%\NPVR\NextEnd.exe" --monitor
timeout 1

Then I stopped the recording server and ran it manually

NRecord RUN

Without the timeout NextEnd was not logging. Note, it seems others are reporting start /b problems on Win 10 1703, not related to NextEnd.

Try ping first and then start

No that won't work the problem is after the start /b not before.

Martin

[jcole998]

Hello, Martin.

I've been trying all different kinds of commands to start NextEnd from ParallelProcessing.bat and I stumbled upon the following:

I tried the following starts:

1) start /b "" "%PROGRAMFILES(X86)%\NPVR\NextEnd.exe" --monitor
2) start "NextEnd-ParaProc" /d "%PROGRAMFILES(X86)%\NPVR" /b NextEnd.exe --resume --oid %3 --monitor
3) start "" /b "%PROGRAMFILES(X86)%\NPVR\NextEnd.exe" --resume --oid %3

Starts 1 & 2 completed with log entries shown in NextEnd-Monitor.log in the attached zip files.

Start 3 also completed but made no entries in either NextEnd log. This was the original start command that was never returning. I'm puzzled.

Is their some switch in NextEnd that is disallowing the --oid parameter?

[mvallevand]

#3 will only log if the oid is a monitored sport . #2 is invalid but --monitor overrides --oid,

Martin

[jcole998]

OK, more trials produced some results. The next line is echoed from the ParallelProcessing.bat:

ParallelProcessing.bat started with ["I:\NextPVR-Capture\MLB Baseball_20170531_13001600-1.ts"][586][31473][21]["MLB Baseball"]

I used the following command in ParallelProcessing.bat:

start "NextEnd-ParaProc" /d "%PROGRAMFILES(X86)%\NPVR" /b NextEnd.exe --resume --oid %3

To produce the following NextEnd.log file:

[...startup]
2017-05-31 13:14:50.236 [DEBUG][1] NextEnd, Version=2.0.6274.30072, Culture=neutral, PublicKeyToken=null
2017-05-31 13:14:50.244 [INFO][1] About to connect to remote recording service
2017-05-31 13:14:50.249 [DEBUG][1] RecordingServiceProxy@exit
2017-05-31 13:14:50.256 [DEBUG][1] About to look for plugin directories in: C:\Users\Public\NPVR\Plugins\
2017-05-31 13:14:50.257 [DEBUG][1] Skipping non-existant plugin directory: C:\Program Files (x86)\NPVR\Plugins\
2017-05-31 13:14:50.257 [DEBUG][1] Command Line --resume --oid 31473
2017-05-31 13:14:50.257 [DEBUG][1] NextPVR extending = False
2017-05-31 13:14:50.257 [DEBUG][1] Preparing this event
2017-05-31 13:14:50.258 [DEBUG][1] MLB Baseball Regional Coverage 2017-05-31 13:00:00
2017-05-31 13:14:50.263 [DEBUG][1] Teams error for livePVR MLB Baseball Regional Coverage 5/31/2017 5:00:00 PM
2017-05-31 13:14:50.263 [DEBUG][1] Monitor status = none

Does this look OK? I always see the word "error" as a red flag.

Recording port was released 60-seconds after cancelling the recording. I think this is all good.

Just a suggestion but it would be helpful if something was logged for each invocation of NextEnd.

Many thanks, Martin.

[mvallevand]

That looks ok, the reason for the error is the MLB game you had scheduled didn't follow the normal rule to include the teams in the sub title instead it just has "Regional Coverage" so the server wouldn't now what game to monitor. Here are the upcoming MLB games that can't be monitored it shows more clearly http://tvlistings.zap2it.com/tv/mlb-base...aid=zap2it

If I enabled logging for everything there would typically not be enough generations to investigate real problems. So if you have a race Saturday afternoon with problems that you don't notice until Sunday you would have needed to grab the logs before the next three recordings. That being said earlier this week I did add a debug mode of logging for each event which will be included in the next update.

Martin

[jcole998]

If I enabled logging for everything there would typically not be enough generations to investigate real problems. So if you have a race Saturday afternoon with problems that you don't notice until Sunday you would have needed to grab the logs before the next three recordings.

Martin

Thanks, Martin. Except for the statement above, I understand how games are selected. I do not understand what you're driving at with statement I've quoted. Enough generations...real problems? Before next three recordings? Is this something I should pay attention to? Can you be more explicit?

My apologies if I seem somewhat dense.:o

[mvallevand]

Assuming you record a race Saturday afternoon that you want to watch later on Sunday afternoon that would be the first generation, NextPVR API has four generations of logs Logging everything If you recorded something else Saturday night, SNL and then Meet the Press and Face the Nation Sunday morning you would lose that important log for four useless logs.

Martin

[jcole998]

Thanks, Martin. I understand generations in context. It is something to be aware of. Learning the jargon is an ongoing effort.

[jcole998]

The NASCAR Dover race ran way late and NextEnd covered it perfectly.

It would seem that NextEnd log generations are driven by events rather than file size. I always preferred the NextPVR approach or rolling over to the next generation when a configurable file size is exceeded. I'm hoping you might agree.

Many thanks, Martin.

[mvallevand]

Glad the main problem is resolved. The logging API starts a new log when the program is executed (ie with each recording) just like NextPVR and it probably would rollover with extreme extending. I could write my own logging logic but the current model meets my support needs.

Martin