How to install NextPVR v3.7.5 plugin?

[ChrisHammond56 4]

I have been searching for almost a day now. I have copied the NPVR plugin v3.7.5 into the Plugins folder on the Synology box. I do not seen any config options for this in the main Emby Plugins menu. I Have checked permissions and they are ok, and rebooted quite a few time.

I did see somewhere that the plugin may only be for Windows, was/is that correct?

Thanks

Edited February 27, 2022 by ChrisHammond56

[Luke 42078]

Hi, what folder did you put it in?

[ChrisHammond56 4]

On my Synology, /volume1/Emby/plugins. Thanks

[Luke 42078]

Please attach the emby server log:

Thanks.

[ChrisHammond56 4]

This is the log after the latest reboot. I am messing with xTeVe at the moment for multiple M3U tuners as well as NPVR, so you may see some xTeVe stuff.

On a wider note, my ultimate goal is to have my two separate M3U sources (HDMI encoders) with exactly the same channel line-ups, but using one guide in Emby for multi-tuner recording purposes. That is why my path was to use NPVR as it combines the tuner resources.

FYI, NPVR is running as a docker container connected to the HOST network, so directly mapped to the port 8866

Thanks

embyserver.txt

[ChrisHammond56 4]

Just a quick update. I reviewed the logs that I sent, and I could see that, even though the /volume1/Emby/plugins folder exists, the actual one is:

/volume1/@appstore/EmbyServer/system/plugins

I moved the plugin to that folder and can now see the NPVR plugin in Emby. The only thing that annoys me with using NPVR is that (for tuner amalgamation), I have to settle for NPVRs recordings Etc. I would have liked to use two separate M3U sources and one guide within Emby and cut out the unnecessary NPVR, but until better tuner support arrives in Emby, I suppose needs must. Any news on the new improved tuner support? 

Thanks

[Happy2Play 9780]

Best guess would be dll permissions as the /volume1/@appstore/EmbyServer/system/plugins folder is the plugins that come with the server and are pushed to /volume1/Emby/plugins by default. 

If a default plugin is ever uninstalled, it will remain in /volume1/@appstore/EmbyServer/system/plugins and not in /volume1/Emby/plugins and show as removed in the system.xml.

[Luke 42078]

3 hours ago, ChrisHammond56 said:

Just a quick update. I reviewed the logs that I sent, and I could see that, even though the /volume1/Emby/plugins folder exists, the actual one is:

/volume1/@appstore/EmbyServer/system/plugins

I moved the plugin to that folder and can now see the NPVR plugin in Emby. The only thing that annoys me with using NPVR is that (for tuner amalgamation), I have to settle for NPVRs recordings Etc. I would have liked to use two separate M3U sources and one guide within Emby and cut out the unnecessary NPVR, but until better tuner support arrives in Emby, I suppose needs must. Any news on the new improved tuner support? 

Thanks

What kind of tuner do you have? What specific features are you waiting on?

[Carlo 4561]

7 hours ago, ChrisHammond56 said:

The only thing that annoys me with using NPVR is that (for tuner amalgamation), I have to settle for NPVRs recordings Etc. I would have liked to use two separate M3U sources and one guide within Emby and cut out the unnecessary NPVR, but until better tuner support arrives in Emby, I suppose needs must. Any news on the new improved tuner support?

What kind of problem are you having trying to use 2 m3u and one guide in Emby?

Unless you're trying to do something special with the 2 files Emby supports this already.

[ChrisHammond56 4]

Thanks for getting back to me. I don't think my request is that unusual. I have been using Emby for some years now with one M3U tuner source and the Emby Guide (premium member). It's been rock solid and have had very little issues that I couldn't solve myself (or find it was my fault anyway). However, last week I purchased another HDMI encoder, and connected the second M3U. That also worked fine, as I now have 2xM3U sources and they had been mapped to the correct channels. But, I now see two entries for each channel. BBC1x2 BBC2x2 Etc. 

This is messy, but I suppose it's OK if you are only using LiveTV. However, Recording takes us into a rabbit hole. Please correct me If I mis-used Emby here, but if I setup a series link (via the Guide), Emby creates a series attached to that channel (and for that purpose, that tuner only) OR I can select 'All Channels'. By 'all channels' I assume Emby is referring to any channel in the channel list (BBC1, BBC2, ITV, can you guess I am in the UK?). For tuner conflicts, if that series happens to be broadcast at the same time as I am watching another channel on that tuner, it would fail to record as the tuner would be in use at that stage. The backup would be to use the second tuner with the same channel. If I select the 'All channels' for the series, then I think Emby may select the next tuner, however, it would also choose any channel that the recording is broadcast on (which would not restrict to the specific channel required in the first place).

I hope I haven't confused you so far. I remember from my tinkering in the past about tuner selection issues (with both Plex and Emby), so in a previous life, I had used NPVR for the grouping of tuners. That way, one source could be presented to the server, and NPVR would allocate the 'available' tuner. 

I have multiple options at this stage.

1. Use 2x Emby M3U tuners, have duplicate channels in the guide, and select the series based on tuner/channel (very messy to organise that Series schedules don't overlap)

2. Use 2x NextPVR tuners in Emby 

3. Use 1x NextPVR Plugin

As mentioned previously, option (1) is not at this stage of Emby tuner development desirable for me. So, option 2 or 3. Option 2 does work, however, when I record something, Emby randomly stops the recording and says that its completed, however, NPVR still says that Emby has a tuner open. Only until the official ending of the programme does the tuner get released.

I thought it may be because I was using M3U, so that is why I reverted to option (3). However, I still see the same behaviour with this option. Recordings are cut short. So I am now at the stage whereby any multi-tuner support is not working for me. I haven't revisited option (1) to see if the same truncated recordings exist, as I have ran out of time over the weekend.

I can see from the log (attached) that for the recording of the BBC1 programme Long Shot (line 1516), Emby reports that its going to record for 55 minutes. However, Emby closes the connection (but keeps the tuner open in NPVR) after just 3 minutes (line 1600). This is a severe example, as sometimes it can go for 1hr 30ish of a 2 hour programme.

So, is this an Emby issue, or NextPVR issue? Not sure. I want to eliminate NPVR completely, and go back to my working environment that I was happy with. As I say in my opening paragraph. Using 2x M3U and Emby guide would be my preferred method, but multiple same channels, and series/recording issues are a no-no.

Any feedback would be appreciated. Thanks

embyserver (3).txt

[Luke 42078]

Quote

As mentioned previously, option (1) is not at this stage of Emby tuner development desirable for me. So, option 2 or 3. Option 2 does work, however, when I record something, Emby randomly stops the recording and says that its completed, however, NPVR still says that Emby has a tuner open. Only until the official ending of the programme does the tuner get released.

Hi, do you still see this on a newer beta?

[ChrisHammond56 4]

Hi Luke. Let me test that out. Are you meaning the .28 or .29 Beta release?

[Luke 42078]

Yea try the .29.  If you still run into it then let's look at an example:

Thanks.

[ChrisHammond56 4]

Hi Luke. No change unfortunately. I did a few test recordings, and it just stops randomly. I do see in the logs that there was an error, but I am unsure how to interpret. In recording-conversion... at line 602: Seek to start failed.

I am unsure what to do next. I have eliminated NPVR by going with 2x M3U sources in Emby (and having 2x the same channels in the guide section).

Thanks

recording-conversion-e3767a3f-076d-4d13-88a5-0f43608d76b7_1.txt ffmpeg-directstream-97a9f884-5fb8-42a7-8861-928b6072e604_1.txt embyserver (9).txt

[Luke 42078]

So just to confirm, you're importing an m3u source into the server that contains rtsp urls, is that correct? What software is publishing the rtsp?

[ChrisHammond56 4]

Correct. I have an m3u file that references rtsp urls. I am not using any SW provider. It's coming straight from my HDMI encoder (local LAN). I have multiple streaming options with the encoder, of which I am using rtsp. I have also tried http, but not with .29. I am attempting that now.

These are the details from VLC when streaming RTSP:

...

And HTTP:

Only difference I can see is that audio is AAC vs ADTS

Thanks

[Luke 42078]

Yes I would suggest http as that is a much simpler protocol.