NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Docker arm32v7 v
1 2 Next »
Almost there, but no Scan button

 
  • 0 Vote(s) - 0 Average
Almost there, but no Scan button
GlowTube
Offline

Junior Member

Posts: 26
Threads: 9
Joined: Aug 2007
#1
2021-12-22, 07:41 PM
I was happy to learn that there's a Dockerized NextPVR for the Raspberry Pi4. I have configured things and I'm almost there, lacking only the "Scan" button on my device page. Here are my configuration details:
  • RPi 4 , Raspbian 11 Bullseye
  • NextPVR Docker container arm32v7stable, version 5.2.3.211114
  • Hauppauge WinTV HVR 950 USB tuner
  • HD Homerun HDHR3-CC (3 tuners)
  • Guide information from SchedulesDirect

When the Pi boots there's a lot in the dmesg relating to the HVR 950. There was a complaint about missing firmware, and I followed other instructions on the web to furnish the xc3028-v27.fw file. I ran the container using the docker-run command given on the Docker install page, and I was able to bring up the web UI on port 8866. Under Settings/Devices I see my one "IPTV device" along with my three HD Homerun tuners. But there's no "Scan" for the HVR 950, only "Import/m3u" and "Import/XC" (and I'm not sure how to use those options).

As a side-note, if I decide to use one of the HDHomerun tuners, it will Scan, and NextPVR accumulates a large channel list. And from there I can tune any of those channels fine. That's great, but for this exercise I'm interested in the HVR 950, not the HDHomerun's.

Also, I use this same Hauppauge tuner on a Windows copy of NextPVR, and it works fine there, including a Scan button. It required a Windows driver download from Hauppauge to work correctly.

Lastly, I was a little surprised that the docker-run command does not include any --device clauses that would jam the path of my USB tuner into the container.

Thanks for any advice!
mvallevand
Online

Posting Freak

Ontario Canada
Posts: 52,919
Threads: 956
Joined: May 2006
#2
2021-12-22, 07:46 PM
You need to get the tuner working in the host before it can work in Docker. After that you will need to pass through --device=/dev/dvb

Martin
sub
Online

Administrator

NextPVR HQ, New Zealand
Posts: 106,699
Threads: 767
Joined: Nov 2003
#3
2021-12-22, 07:46 PM
It sounds like you only have the IPTV and HDHR devices listed on your Settings->Devices page, which means the HVR950 device isn't visible in your docker container.

Quote:Lastly, I was a little surprised that the docker-run command does not include any --device clauses that would jam the path of my USB tuner into the container.
Ultimately the commands will vary depending on what type of setup you're using. If you're trying to use a physical tuner from docker (your HVR-950), then you'll need to add "--device /dev/dvb:/dev/dvb". Most people are doing IPTV, or HDHR style devices these days so don't need this.
GlowTube
Offline

Junior Member

Posts: 26
Threads: 9
Joined: Aug 2007
#4
2021-12-22, 09:21 PM
Thanks, that was it exactly... --device /dev/dvb was all it took. Scan button appeared, scan done, channels tuned. Happy camper!

I agree with others in the group that the Pi4 is not fast enough to send an HD stream to a web browser client, due to the transcoding load. Stream freezes every 5-10 seconds. Tonight I'll try the Pi4 server with a Kodi/Nvidia Shield client, which should be plenty fast enough. In this instance I'm hoping the Pi4 sends the received MPEG-2-ts stream verbatim and lets the Shield deal with it. Thanks again, for the quick and helpful responses!
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



Possibly Related Threads…
Thread Author Replies Views Last Post
  RPi4, Hauppauge dualHD - Channel Scan returns no data mikeh28 7 3,794 2020-02-15, 05:24 PM
Last Post: sub

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

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

Linear Mode
Threaded Mode