NextEnd v5 trial release

[mvallevand]

It's mainly a design thing. The way early is supposed to to work is it cancels immediately when the API says the game is over and the other parameters are ignored. I figure if you want commentary you would just use cancel since the talking heads will try and fill up the rest of the broadcast time, so why limit it. Cancel will kill the post padding though unless post game is used and preempt is not enabled

Martin

[BackwardsK]

So I should remove the --early and leave --cancel and --postgame 10? What I'm looking for is once the game is detected as over set the recording to end 10 mins after that point. If the recording is scheduled from 1-4p and the game ends at 3:40, record until 3:50. If the game goes until 5:15, record until 5:25.

[mvallevand]

I understand what you want. I won't change early because it is specifically meant to provide a way to stop recording early and allow comskip and post processing to have resources and subsequent scheduled recording not to have tuners blocked.

I thought that postgame would set a stop time even if it is early but if not I will change that for the future .netcore 8 version of NextEnd.

Martin

[mvallevand]

Looking at the code the --postgame 10 is all you need since the recording will simply end after the the 10 minutes, it doesn't need to be cancelled. If you want to force 10 minutes even if the show goes over the scheduled time use the --prempt parameter. If you do use --preempt you could block the tuner if you have back to back recordings and multi-rec isn't being used.

Martin

[mvallevand]

I am going to need to check early since.  Testing the new build, this last frame of a recording was canceled before the ref even signaled the out.  Looks like postgame needs a minimum 1 minute.

Martin

[BackwardsK]

Code:

2024-09-18 00:05:07.838 [DEBUG][1]      NextEnd, Version=4.2.0.16485, Culture=neutral, PublicKeyToken=null
2024-09-18 00:05:07.860 [INFO][1]       Using remote RecordingService
2024-09-18 00:05:07.860 [DEBUG][1]      Command Line --oid 850 --early --postgame 5
2024-09-18 00:05:07.860 [DEBUG][1]      NextPVR extending = False
2024-09-18 00:05:07.860 [DEBUG][1]      Preparing this event
2024-09-18 00:05:07.860 [DEBUG][1]      MLB Baseball Toronto Blue Jays at Texas Rangers 2024-09-18 00:05:00
2024-09-18 00:05:08.934 [DEBUG][1]      LivePvrData.Data.Net.Responses.StatusResponse [Title=MLB Baseball, Status=Warmup, IsValid=True, IsActive=True, IsComplete=False, IsError=False, ]
2024-09-18 00:05:08.934 [DEBUG][1]      Monitor status = active
2024-09-18 00:05:08.948 [DEBUG][1]      Service not running cancel monitoring

Setting up a new install on a new box.  Got everything working but this plugin.  This game is actively recording without issue, but the plugin bailed as shown.

fwiw, on this new box, I'm running nextpvr via a manual installation on a non-standard port, maybe that's the issue?  Another game started recording at 1:40 and the plugin bailed out with the same "Service not running" message.  That game is also being happily recorded.

[mvallevand]

In config.xml what do you have for

Settings/WebServer/Port

It should be checking for that port being open on any network device.

Martin

[BackwardsK]

Code:

  <WebServer>
    <UseCompression>true</UseCompression>
    <Enabled>true</Enabled>
    <Port>21097</Port>

That is the correct port the web service is running on.

[mvallevand]

Does the port show LISTENING on with netstat

The code it is using the example here https://learn.microsoft.com/en-us/dotnet...ew=net-8.0

Martin

[BackwardsK]

Hmm... you might be on to something. This particular box is locked down and netstat isn't returning any output, which makes me think the GetActviveListeners call is probably returning nothing as well, even though the port is active. Is there any way to specify the ip/port manually?