I can't start NextPVR service after update.
I'm using windows 10 (22H2)
when I start NextPVR service manually
it says "The NextPVR Service service started and stopped on your local computer.
Some services will stop automatically if they are not used by other services or programs."
I checked event viewer.
Unable to start service.System.ComponentModel.Win32Exception (0x80004005): The executable you specified is not a valid application for this OS platform.
위치: System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
위치: System.Diagnostics.Process.Start()
위치: System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
위치: NextPVRService.RecordingService.StartServer()
위치: NextPVRService.RecordingService.OnStart(String[] args)
위치: System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
Often I display the OSD to see what the current time is, but with V7 it's no longer showing.
I've attached a screen shot from V6.
I assume I can modify the skin to add the time back in and started to look into it, but thought I'd mention it here first.
Art
I recently built a baby linux server for which two tbs devices are connected - 6281 and 6284.The 6281 worked flawlessly so I added the the 6284 with bbc three and bbc four (and the hd version) load data so slowly that it could never produce a picture. If i take the 6284 out bbc three and four are back. bbc one hd, bbc two hd load fine, so the mux singal is fine .
I also updated nextpvr from 6.1.5.231022 to 7.0.0.241105 at the same time as adding the 6284. Both cards worked fine in one of my win boxes. I installed sichbopvr my linux box as a test and it displayed bbc four hd fine!
i've added the log for when the particular tuner found bbc four and the nrecord logs. I didn't add the other tuner logs as some didn't have loop cable added.
History: I've been recording the Gunsmoke series for about a year now. But suddenly last week the xmltv data from zap2it got messed up. I get OTA, and Gunsmoke is broadcast on channel 51.1 at 12pm daily. The series then stopped recording because 51.1 was suddenly the same programming of 51.2. I could watch Gunsmoke at the right time on 51.1 on my TV set, but it wasn't being recorded on my computer which has the Hauppage tuner. Then at the last download of the zap2it data yesterday, I can see that the EPG is still wrong until Fri, but Sat it is fixed. Now the problem:
1. It doesn't appear to be able to set up recording for the Gunsmoke series. It still indicates recording for just about anything else, just not that one.
2. I tried exiting the guide, restarting the service, and reopening the guide, but no progress. Symptom was "cancel series" and the bar was not red.
3. I was able to get "record series" button by doing "cancel series" and restarting. I then did "record series," but there is no indication anywhere that the series will be recorded.
4. It's now back to "cancel series", but the bar is still not red, and there is no indication of record pending.
In the screenshots attached, I'm looking for any indication that Gunsmoke will be recorded (none).
I'm at a loss of what to do, but I certainly don't want to reinstall the software. Does anyone have an easier suggestion for me on how to fix this problem?
Screenshots:
1-Doesn't show scheduled
2-Doesn't show scheduled
3-Not red, so not indicated as scheduled
4-example of something scheduled
Logs attached
Was going to reboot my server after recordings had finished up and noticed the tray icon was red when it shouldn't be.
Nothing shows as currently recording in the client.
Checking the device status from the web app shows this:
Device Status
Hauppauge WinTV 885 ATSC Tuner/Demod (ATSC)
- \\.\pipe\NPVR_00956ba3-ea33-4559-8660-9f2287300e4f:pids=8187
Just an FYI -
Just now updated to V7, ran into the Resume issue right away, but see a fix is in the works.
I still had to rename NPVRCCExtractor.ax to avoid hangs on exit. My work around will be to continue using Yauiclient for closed caption support.
Art
Greetings,
I'm running nextpvr/nextpvr_amd64:latest in a container on a Synology NAS. Few issues:
1. In addition to a HDHomeRun HDHR3-US (legacy tuner), I added a HDFX-2US. HDHR3-US works just fine. The HDFX-2US appears in the device list, but I'm unable to view/record any channels. It has the same channels as the legacy tuner. I confirmed this by disabling the legacy tuner.
2. Despite no IPTV device, IPTV channels appear in the guide.
3. Guide takes a long time to load (>15 seconds), perhaps because all of the IPTV channels (over 1,000).
I recently updated NextPVR to 7.0.0.241105 using the upgrade procedure
I then updated the NextTool using its install procedure (including the symbolic links steps).
I tried to execute a NextTool command: `/opt/dotnet/dotnet /opt/nextpvr/system/NextTool.dll --file ...`
I got a missing assembly error:
Code:
Error:
An assembly specified in the application dependencies manifest (NextTool.deps.json) was not found:
package: 'MediaInfo.Wrapper.Core', version: 'MediaInfo.Wrapper.Core'
path: 'MediaInfo.Wrapper.Core.dll'
the file does not exist in /opt/nextpvr/system, however the file does exist in /opt/nextpvr/system.bak
Hello! I have a fairly straightforward setup that randomly (but regularly) drops a live stream with the following log message typically preceding the stream failure:
Quote:stream@2 got zero bytes
Connecting directly to the tuner does not appear to have the same issue. My Tuner is hardwired directly to my nextPVR linux box. Here's the basic setup:
Tuner: HDHR5-2US (Firmware: 20231214)
PVR: NextPVR (Version: 7.0.0.241105, docker container on a Linux host)
TV: Amazon Firestick (latest) Kodi (21.0) - NextPVR Addon (21.2.0)
The same behavior happens on two different clients. Both are the exact same(firestick -> kodi -> PVR) but one is hardwired, one is connected over WiFi. The channels that get dropped are very strong signals. For example:
Local CBS affiliate:
Quote:Virtual Channel
4.1 KCNC-TV
Frequency
599.000 MHz
Program Number
1
Modulation Lock
8vsb
Signal Strength
100%
Signal Quality
100%
Symbol Quality
100%
Local NBC affiliate:
Quote:Virtual Channel
9.1 KUSA-HD
Frequency
189.000 MHz
Program Number
1
Modulation Lock
8vsb
Signal Strength
100%
Signal Quality
91%
Symbol Quality
100%
Here are the logs that I pulled from NextPVR for what I believe is the whole request -- opening the stream to it failing:
This happened the last time there was a new release, too. I use IRSS to send Windows class messages to the client to control the application even when it doesn't have focus. It seems like the new version no longer responds to those messages. I believe there is some setting sub can turn on when he compiles the application. I verified it is using the same class name as before and tried sending the message directly from the IRSS Translator program to make sure it wasn't my remote control that wasn't working. I am using the released v7, not the prereleased version.
