Hello everyone,

I'm new and this is my first post. I tried to schedule a recording that started late in the day and went past midnight until about 1:30 a.m. the next day.

I received an error message that rejected the schedule on the basis that it was more than one day (not a direct quote of the error message). I thought such a schedule would be common.

Have I missed something? Can this be done? Can I schedule a recording that runs over to the next morning? If so, can someone please tell me what I need to do to make it work?

Thank you.

Regards,
Noggle

Is there a way to disable the XML meta data for recordings, and to have all recordings in one folder instead of being filed to individual folders?

For example, all .TS recordings in one destination folder, no subfolders, no XML files. All I need are the video recordings.

Hello, 
I have just recently set up a Open Media Vault NAS and I am having trouble trying to figure out how to install the docker.

I tried using stacks in Portainer but I am getting this error. "Deployment error unsupported compose file version 1.0"

This was my attempt.

nextpvr:
    image: nextpvr/nextpvr_amd64table
    container_name: nextpvr
    network_mode: host
    environment:
      - PUID=998
      - PGID=100
      - TZ=America/Los_Angeles
volumes:
    -/srv/dev-disk-by-label-Media/one/nextpvr/config:/config \
    -/srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    -/srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \ 
ports:
  - "8866:8866"
restart: unless-stopped 


I am totally lost on how to deploy the docker container and I have no clue how to install it as I am brand new to all of this,
my aging brain is probably not helping. I can pull the docker image and it shows up in my images but I don't know how to configure it.


Thanks.

OK, I got rid of the compose file version error by adding a version: "3" line at the top and now get a new error "volumes must be a mapping" I thought that was what I was doing with
volumes:
    -/srv/dev-disk-by-label-Media/one/nextpvr/config:/config \
    -/srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    -/srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \

which are shared folders I setup and the absolute path.

I tried using putty with the 
docker run -d \
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/config:/config \               
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \
    --publish 8866:8866 \
    nextpvr/nextpvr_amd64:latest

and get "docker: invalid reference format."

Has anyone had any success in getting NextPVR to record NASA TV with an m3u/m3u8 IPTV list? (I hope I said that right. I kinda new with IPTV.)

Hi,
Quick question... is there an easy way to pick the epg big file made by nextpvr and export either to xml or txt?
If yes, instructions please.
Thx.

Getting a silly issue, not sure why

- http://127.0.0.1:8866 works
- http://192.168.178.230:8866/index.html works- and all other pages when full url given
- http://192.168.178.230:8866 doesn't work- 404 error

Had similar little niggles with first page not coming up before/ after login on a few different machines as I've been testing- they always work after I get first page and full page is given.

Any suggestions?

Hi all.
This may not be an NPVR issue, but I thought I'd post it in here to rule this out first before going to Kodi etc...

I was watching Destination America and the picture froze about 15:12 I think, and then it looks like Kodi quit about 15:15
I'm guessing this isn't a NPVR issue?

Have included the Kodi log in with the NPVR logs

Attached Files

  logs-20200530-1518.zip (Size: 518.94 KB / Downloads: 2)

So this is a fresh OS install, with the NPVR config and DB copied from the previous one but now I come to try to change the password I can't.

Error attached below reads Failed to update password. Confirm you've entered you existing password correctly

I've tried a number of times, remotely and locally - no dice...

The logs are also a bit odd in that this install has never seen the Hauppague stick, only an HD Homerun (The previous install had the Hauppague stick until I upgraded)

I can login fine, so admin/password is working, but I have just set up Nginx as a reverse proxy so I can access remotely and apparently that's not a secure username password combo to expose to the internet...

Cheers in advance!

Attached Files

Thumbnail(s)
   

  logs-20200530-1420.zip (Size: 851.44 KB / Downloads: 1)

I am getting this error message every time that I try to load the NextPVR client in Kodi. I have a laptop, a generic Android box and an Nvidia Shield. I get the error with all three devices. 

My network is fine. I can access all mapped folders on the server machine. I can access the server through the web interface on the laptop. I can ping the server machine from my laptop.

Kodi is set up and working on the server machine.

I ran ipconfig to double-check the IP address. It is correct and has been set as a static ip address.

I have enabled AllowRemoteStreaming in config.xml.

It isn't the firewall. There is nothing in the logs and I temporarily shut off the antivirus and firewall.

At this point, it is either Kodi or NextPVR. As soon as I install the NextPVR client addon on any of the devices, the erorr message pops up before I have had a chance to configure it. I configured, disabled/re-enabled, re-boot everything repeatedly, uninstalled, re-installed. Nothing worked.

Does anyone have any idea why this is happening?

Kodi Log https://pastebin.com/dyW4rkzw

Attached Files

  logs-20200529-2333.zip (Size: 171.67 KB / Downloads: 4)

Right now I'm still in the experiment phase of NextPVR.

With MythTV, multiple mount points / paths can be configured as recording directories, and then MythTV can be configured to either spread the load, most space available, etc. When it comes time to playback a recording, the MythTV database stores the name of the recording, but not necessarily the complete mount path, so if I choose to manually move a recording in the CLI from one recording directory to another, then mythtvbackend can still find it. (Because most users will have a reasonable number of mount points, it takes a fraction of a second to check each directory for the file that we're looking for)

If I create a share on my NAS, and configure the recording and LiveTV buffer directories to point at that share, then will I be able to move the existing recordings that are in the recordings subdirectory to the new mount point? Or is the NextPVR database storing the full path to the recording, so if I manually move it with "mv", that's going to break things?