NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support v
« Previous 1 … 12 13 14 15 16 43 Next »
no epg

 
  • 0 Vote(s) - 0 Average
no epg
madmanuk
Offline

Member

UK
Posts: 55
Threads: 4
Joined: Jun 2020
#1
2020-06-18, 10:00 PM
Hoping to use nextpvr with hdhomerun.

I have installed the docker image nextpvr_amd64 stable within docker desktop on a mac mini.

I used this command to create it:

docker run --restart always -dp 8866:8866 -dp 8020:8020/udp -v /pvr/config:/config -v /pvr/recordings:/recordings -v /pvr/buffer:/buffer nextpvr/nextpvr_amd64Confusedtable

there is communication with the hdhomerun, i have channels, live video, and have been able to record a snippet by time.

The mac is 10.10.10.250, and the hdhomerun is 10.10.10.248.

One slight oddity I noticed was that changing the EPG timeout in DVB/ATSC EPG setup doesn't appear to save, and the window does not close.
I changed that to 480 directly in the xml.

I enabled verbose logs and ran the epg.
I looked at the hdhomerun status, and I could not see a tuner being used.
Tuner 0 was already busy because I had paused a playback some time ago.

Thanks for looking.
I changed DVDVB/ATSC EPG Setup
B/ATSC EPG Setup


Attached Files
.zip   logs-20200618-2157.zip (Size: 79.99 KB / Downloads: 1)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,785
Threads: 769
Joined: Nov 2003
#2
2020-06-18, 10:09 PM
(2020-06-18, 10:00 PM)madmanuk Wrote: One slight oddity I noticed was that changing the EPG timeout in DVB/ATSC EPG setup doesn't appear to save, and the window does not close.
Sorry - I'm aware of this one. It's on my todo list.
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,785
Threads: 769
Joined: Nov 2003
#3
2020-06-18, 10:14 PM
I think inside your container, the IP address detected, which is where the HDHR is told to send the stream, is not visible to the HDHR:

2020-06-18 21:55:19.510 [DEBUG][13] legacy tuning requesting target rtp://172.17.0.2:8020

I suspect you need to add a HOST_IP=10.10.10.250 environment variable on your docker container. This will override the detected ip address, and tell the HDHR to send the data to the mac (which will ultimately be feed into the docker container)
madmanuk
Offline

Member

UK
Posts: 55
Threads: 4
Joined: Jun 2020
#4
2020-06-18, 10:47 PM
(2020-06-18, 10:14 PM)sub Wrote: I think inside your container, the IP address detected, which is where the HDHR is told to send the stream, is not visible to the HDHR:

2020-06-18 21:55:19.510 [DEBUG][13] legacy tuning requesting target rtp://172.17.0.2:8020

I suspect you need to add a HOST_IP=10.10.10.250 environment variable on your docker container. This will override the detected ip address, and tell the HDHR to send the data to the mac (which will ultimately be feed into the docker container)
Thanks.
Took me a few minutes to work out how to do that...
Added --env HOST_IP=10.10.10.250 on the docker run command line.
It does seem to have made a difference - there is some data coming back now, and tuner 0 is changing frequencies.
I still don't have data in the guide though.
More logs attached.
.zip   logs-20200618-2240.zip (Size: 32.18 KB / Downloads: 2)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,785
Threads: 769
Joined: Nov 2003
#5
2020-06-19, 01:12 AM
That's looking better, but it looks like the data isn't making it into the container from the device. In the device's web app, does the tuner seem to be sending to the right address, and indicate some data rate like stuff is being sent?
madmanuk
Offline

Member

UK
Posts: 55
Threads: 4
Joined: Jun 2020
#6
2020-06-19, 08:46 AM (This post was last modified: 2020-06-19, 09:47 AM by madmanuk.)
Thanks again for your response.
I took a couple of screenshots during an update.
The hdhomerun i/f does not show the destination IP, but there is a program number and a streaming rate.
When the process is finished, tuner 0 remains tuned, but with no streaming, rather than not in use like the others.

I am seeing lines like :
2020-06-19 09:21:47.868 [DEBUG][46] Have received 417172 bytes from rtp source

maybe some data is reaching the container?

I found something else, I do not understand.

This is from the latest set of logs:
2020-06-18 23:31:46.029 [DEBUG][16] parameters:
2020-06-18 23:31:46.029 [DEBUG][16] method: setting.devices
2020-06-18 23:31:46.029 [DEBUG][16] refresh: true
2020-06-18 23:31:46.029 [DEBUG][16] format: json
2020-06-18 23:31:46.029 [DEBUG][16] sid: c644106d-5672-4835-9d7f-e83bfb066c08
2020-06-18 23:31:46.029 [DEBUG][16] client_ip: ::ffff:172.17.0.1
2020-06-18 23:31:46.029 [DEBUG][16] user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36 OPR/68.0.3618.125
2020-06-18 23:31:46.029 [DEBUG][16] host_callback: 10.10.10.250:8866
2020-06-18 23:31:46.030 [DEBUG][16] setting.devices
2020-06-18 23:31:46.051 [DEBUG][16] CaptureSource.LoadAll()
2020-06-18 23:31:46.343 [DEBUG][16] [
{
"DeviceID": "12519937",
"LocalIP": "10.10.10.248",
"BaseURL": "http://10.10.10.248",
"DiscoverURL": "http://10.10.10.248/discover.json",
"LineupURL": "http://10.10.10.248/lineup.json"
},
{
"StorageID": "AFC7FE88-1E39-418B-0251-13CA57CEFC7D",
"LocalIP": "10.10.10.222:54626",
"BaseURL": "http://10.10.10.222:54626",
"DiscoverURL": "http://10.10.10.222:54626/discover.json",
"StorageURL": "http://10.10.10.222:54626/recorded_files.json"
}
]
2020-06-18 23:31:46.345 [DEBUG][16] Downloading from http://10.10.10.248/discover.json
2020-06-18 23:31:46.352 [DEBUG][16] Found HDHomeRun: 12519937 (4 tuners)
2020-06-18 23:31:46.352 [DEBUG][16] LineupURL: http://10.10.10.248:80/lineup.json
2020-06-18 23:31:46.567 [DEBUG][16] Local Devices: <devices>
</devices>

10.10.10.222 is an iMac, which should not be involved at all.
The same lines appear, even after turning 10.10.10.222 off and restarting nextpvr.


Attached Files Thumbnail(s)
                   
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,785
Threads: 769
Joined: Nov 2003
#7
2020-06-19, 04:47 PM
You could try going to the Settings->About page, holding the Ctrl key on your keyboard, and clicking the verbose logging button that shows up, then do an Update EPG and post the logs again.
madmanuk
Offline

Member

UK
Posts: 55
Threads: 4
Joined: Jun 2020
#8
2020-06-19, 04:53 PM
These are verbose logs from when I saw the data transfer quoted above.
I can run another set if it is helpful.
Thanks.


Attached Files
.zip   logs-20200619-0924.zip (Size: 190.13 KB / Downloads: 2)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,785
Threads: 769
Joined: Nov 2003
#9
2020-06-19, 05:53 PM
Did you get the message about enabling verbose logging until the next restart? I can't see it in the log.
madmanuk
Offline

Member

UK
Posts: 55
Threads: 4
Joined: Jun 2020
#10
2020-06-19, 06:07 PM
I would have said yes, but if you can't see it my memory must be flakey.
Here are a fresh set.
Since the previous set, I changed -p 8020:8020/udp to -p 8020-8030:8020-8030/udp - in case that makes any difference...
Thanks again for your time.
.zip   logs-20200619-1807.zip (Size: 61.61 KB / Downloads: 1)
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (6): 1 2 3 4 5 6 Next »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode