***** Please see follow-up post *******
I recorded the NASCAR Daytona race last week. It ran way over the posted 6:30pm end time but I saw no evidence that NextEnd kept recording after that.
Does the add-on need an update for the new NASCAR season?
Logs attached for race that was recorded 17 Feb 2019 @ 2pm
Logs did not upload...Following error was displayed:
[ATTACHMENT NOT FOUND]
Never had this error before...Can you help?
jcole998 Wrote:Logs did not upload...Following error was displayed:
[ATTACHMENT NOT FOUND]
Never had this error before...Can you help?
Maybe upload you logs to OneDrive, Dropbox, etc. and post a link?
****** FOLLOW-ON POST FROM ABOVE ************
****** THIS IS MY 2ND ATTEMPT TO UPLOAD LOGS ********
****** LOGS CANNOT BE UPLOADED DUE TO >24MB CURRENT ATTACHMENTS! WHERE ARE ATTACHMENTS?
I recorded the NASCAR Daytona race last week. It ran way over the posted 6:30pm end time but I saw no evidence that NextEnd kept recording after that.
Does the add-on need an update for the new NASCAR season?
Logs attached for race that was recorded 17 Feb 2019 @ 2pm
Never had this error before...Can you help?
[ATTACHMENT NOT FOUND]
My log files are in a 1.5MB zip file. Well below limit. If I click on Manage Attachments during edit, current attachment size is showing more then 24MB but I haven't attached anything! Very puzzled...
jcole998 Wrote:My log files are in a 1.5MB zip file. Well below limit. If I click on Manage Attachments during edit, current attachment size is showing more then 24MB but I haven't attached anything! Very puzzled...
Click Forum Actions above ... Edit Profile ... bottom of the list to the left is Attachments ... You can delete old attachments here
jcole998 Wrote:My log files are in a 1.5MB zip file. Well below limit. If I click on Manage Attachments during edit, current attachment size is showing more then 24MB but I haven't attached anything! Very puzzled...
The 25MB attachment limit per user is for
all attachments on
all posts.
Sorry I missed this thread's relation to NextEnd. I will have to check to see where it stands. I see today's race worked
MONSTER ENERGY NASCAR CUP SERIES AT ATLANTA Race Complete
Martin
Quote:The 25MB attachment limit per user is for all attachments on all posts.
Never new this. Thanks, BrettB.
I have more questions and I'll ask them in the General forum.
I can confirm the Exfinity race was fine, but I had the same issue with the 500 not extending, I think it had to do with the funky naming in the EPG rather than nextend though. I don't recall exactly what the name was, but even my postproceccing.bat which has some logic to copy races to an external drive chocked on it.
Martin,
It looks like I spoke too soon... I think last weeks Xfinity race ended at the normal time so it didn't need to extend unlike the 500. Just checked today Cup race and it shows "Nothing to monitor" in the log which is what the log showed for yesterdays Xfinity log too.
Any chance it has something to do with the new EPG names? This year they are showing up as "NASCAR Monster Energy Series" and "NASCAR Xfinity Racing Series" rather than just "NASCAR Racing" as in years past.
Code:
[...startup]
2019-03-03 02:57:01.504 [DEBUG][1] NextEnd, Version=2.0.6274.30072, Culture=neutral, PublicKeyToken=null
2019-03-03 02:57:01.504 [INFO][1] About to connect to remote recording service
2019-03-03 02:57:01.519 [DEBUG][1] RecordingServiceProxy@exit
2019-03-03 02:57:01.519 [DEBUG][1] About to look for plugin directories in: C:\Users\Public\NPVR\Plugins\
2019-03-03 02:57:01.519 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\System\GetCoreTempInfoNET.dll
2019-03-03 02:57:01.535 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\System\SystemPlugin.dll
2019-03-03 02:57:01.550 [DEBUG][1] Plugin PDB also exists: C:\Users\Public\NPVR\Plugins\System\SystemPlugin.pdb
2019-03-03 02:57:01.691 [DEBUG][1] CaptureSource.LoadAll()
2019-03-03 02:57:01.987 [DEBUG][1] Skipping non-existant plugin directory: C:\Program Files (x86)\NPVR\Plugins\
2019-03-03 02:57:01.987 [DEBUG][1] Command Line --monitor
2019-03-03 02:57:01.987 [DEBUG][1] Sunday check
2019-03-03 02:57:01.987 [DEBUG][1] Checking for recordings from 2019-03-03 18:35:00 to 2019-03-03 22:35:00
2019-03-03 02:57:02.018 [DEBUG][1] Nothing to monitor
2019-03-03 02:57:02.018 [DEBUG][1] Late night check
2019-03-03 02:57:02.018 [DEBUG][1] Checking for recordings from 2019-03-03 22:35:00 to 2019-03-04 01:35:00
2019-03-03 02:57:02.018 [DEBUG][1] Nothing to monitor