NextEnd V2 Pre-Release Announcement

[jcole998]

Other than formatting, why does NextEnd.log show legitimate data? Should it NOT have logged anything because of my manual launch? If there was only one instance of NextEnd.exe, did it log data to both the .log and the .txt files? NextEnd.log shows 369 lines where TestLog.txt shows 2839.

Anyway, I'll try this for the Saturday race and keep you posted.

Thanks for the help.

[mvallevand]

The text file output is not the log that is just stuff I have write to the console to help me debug it and there is always a lot more console output. NextEnd can't distinguish that you ran it manually and it has nothing to do with the number of instances, since multiple sports events and monitors are allowed, just not the same event multiple times. However if the event is not sports there is no logging.

I suggest recording another sports event before Saturday to make sure parallelprocessing.bat is working.

Martin

[jcole998]

Acknowledged. Thanks you.

[jcole998]

Tried another NBA game last night, the Spurs/Warriors game at 9pm. No new entries in the NextEnd.log file.

Can some additional logging be added to NextPVR to ascertain why ParallelProcessing.bat is not getting started?

[mvallevand]

Probably the best thing to do is rename parallelprocessing.bat to something like test.bat and then in a new parallelprocessing.bat run

c:\user\public\npvr\scripts\test.bat %* >> c:\user\public\npvr\parallel.txt

We should see your echo and any error message, even on a non sports recording

Martin

[jcole998]

OK, Martin. I set up the two .bat files as suggested. In the attached .zip file are two .txt files:
1 - ParallelTest-NPVR.txt
2 - ParallelTest-CommandPrompt.txt

As the file names suggest, one was created when NextPVR was to told to begin recording an MLB game in progress at about 16:15 today. The other was created when I launched the ParallelProcessing.bat file from the command prompt while the game was still in progress. I don't understand why NextEnd does not start from NextPVR.

Anything else I can try?

[jcole998]

Well... It seems the solution to my problem was how NextEnd was being started from ParallelProcessing.bat. The following command works every time:

start "NextEnd" cmd /k "%PROGRAMFILES(X86)%\NPVR\NextEnd.exe" --resume --oid %3

Amen...

[mvallevand]

As discussed in another thread https://forums.nextpvr.com/showthread.ph...post514944 I don't like that syntax for parallel processing. I believe I have found a workaround to the NextEnd batch files which I have added to the wiki that might work on your system. My Creator's Update Win 10 test server didn't work without it.

Basically what I suggest is adding a one second timeout to each batch file to allow NextEnd to startup before returning control to NextPVR

ie.

timeout 1

Slower systems might need more.

Martin

[jcole998]

Sorry, Martin, but that didn't help. I used:

start "" /b "%PROGRAMFILES(X86)%\NPVR\NextEnd.exe" --resume --oid %3
ping 192.0.2.2 -n 1 -w 2000 > nul

Do I need more?

[Graham]

Sorry, Martin, but that didn't help. I used:

start "" /b "%PROGRAMFILES(X86)%\NPVR\NextEnd.exe" --resume --oid %3
ping 192.0.2.2 -n 1 -w 2000 > nul

Do I need more?

Try ping first and then start