15 hours ago, alturismo said:

a matter of personal taste ...

 

to make it short as its offtopic here, stay in host mode now, keep in mind that its blocking now the used ports in unraid, like 9981-9983, ... so in terms another docker, app, ... needs it you have to rethink your setup. custom:br0 is not everybodys darling ....

 

 

Where would be ontopic to discuss this sort of thing?

Hi all, 

 

I cannot get the application to start: 

docker: Error response from daemon: error gathering device information while adding custom device "/dev/dvb": no such file or directory.

 

I have no tuner card, I want to get my IPTV stream onboarded in Tvheadend so I can connect Kodi to it. 

Not even sure if this is the right way to go about it. 

7 hours ago, nicolas246 said:

while adding custom device "/dev/dvb": no such file or directory.

as  you dont use a tuner, remove the extra parameter ...

Hi All

 

How do I define extra parameter

 

I tried --device=/dev/dvb however that is not a valid node.

 

I have a Sundtek USB DVBT2/C tuner 

Apr 19 10:04:34 Server kernel: usb 2-2: new high-speed USB device number 7 using ehci-pci

Bus 002 Device 007 Port 2-2ID 2659:1401 Sundtek MediaTV Digital Home III (EU)

 

After installing the driver it says

ATTENTION: Please don't forget to pass through the device:

/dev/bus/usb

 

--device=/dev/bus/usb 

 

However it is still not detected.

Edited April 19, 20233 yr by bally12345

12 minutes ago, bally12345 said:

Hi All

 

How do I define extra parameter

 

I tried --device=/dev/dvb however that is not a valid node.

 

I have a Sundtek USB DVBT2/C tuner 

Apr 19 10:04:34 Server kernel: usb 2-2: new high-speed USB device number 7 using ehci-pci

Bus 002 Device 007 Port 2-2ID 2659:1401 Sundtek MediaTV Digital Home III (EU)

 

After installing the driver it says

ATTENTION: Please don't forget to pass through the device:

/dev/bus/usb

 

--device=/dev/bus/usb 

 

However it is still not detected.

this sounds like a driver issue to me, are you sure the dvb-driver plugin (i assume you have that installed right?) supports Sundtek devices?.

I am using the Sundtek Driver plugin I will try dvb-driver plugin instead 

Very odd the support threads for drives suggest using /dev/bus/usb but it still not being detected within the docker. However is shown as adapter1 in the sundtek driver page.

Have rebooted each time after installing dvb-drivers

Hello together,

 

does anybody know where i need to add the following argument?

TVH_ARGS="--satip_xml http://192.168.1.111:8080/description.xml"

I'm trying to add my SAT>IP Receiver to TVHeadend and that would be the only way that the Discovery is working. But I can't find any suggested place on the Docker itself.

 

Maybe someone has done that befor.

 

Thank you and Best Regards

Stefan

1 hour ago, MVLP said:

I'm trying to add my SAT>IP Receiver to TVHeadend and that would be the only way that the Discovery is working. But I can't find any suggested place on the Docker itself.

 

may try to run the docker in host mode, when your SATIP Server is "regular" it should be discoverd automatically ...

 

otherwise, you have to wait for others which may can help as im using another tvheadend docker with SATIP where RUN_OPTS is added as enviroment variable and there you could add this too in bridge mode, but also consider to bind ports (tuners) and map ports (docker) when running in bridge to get a more stable setup with SATIP, not necassary in host mode ...

6 hours ago, alturismo said:

may try to run the docker in host mode, when your SATIP Server is "regular" it should be discoverd automatically ...

 

otherwise, you have to wait for others which may can help as im using another tvheadend docker with SATIP where RUN_OPTS is added as enviroment variable and there you could add this too in bridge mode, but also consider to bind ports (tuners) and map ports (docker) when running in bridge to get a more stable setup with SATIP, not necassary in host mode ...

 

I changes the Network from bridge to host and now it's seeing the Sat>IP Receiver.

Thank you for the idea!

I see that your docker image is based on the AUR tvheadend package (https://aur.archlinux.org/packages/tvheadend) that hasn't been updated in a while. As tvheadend have changed their versioning scheme, from what I understand (https://tvheadend.org/p/downloads), the new way to go seems to be with the AUR package based on git (https://aur.archlinux.org/packages/tvheadend-git). I was wondering, if you were keen on updating the container accordingly?

I already apologize in advance, if I misunderstood any of the facts, as I'm not familiar with arch linux. I just moved to your docker image from the linuxserver-version, because I needed to supply my own version of ffmpeg, that I couldn't get for the alpine container. I love that you're supplying a different version with more options!

7 hours ago, SvenPe said:

I see that your docker image is based on the AUR tvheadend package (https://aur.archlinux.org/packages/tvheadend) that hasn't been updated in a while. As tvheadend have changed their versioning scheme, from what I understand (https://tvheadend.org/p/downloads), the new way to go seems to be with the AUR package based on git (https://aur.archlinux.org/packages/tvheadend-git). I was wondering, if you were keen on updating the container accordingly?

I already apologize in advance, if I misunderstood any of the facts, as I'm not familiar with arch linux. I just moved to your docker image from the linuxserver-version, because I needed to supply my own version of ffmpeg, that I couldn't get for the alpine container. I love that you're supplying a different version with more options!

Thanks for the heads up, i see the notice on the downloads page and i have now switched over to the tvheadend git branch, please pull down the latest image at your convienience.

1 hour ago, binhex said:

Thanks for the heads up, i see the notice on the downloads page and i have now switched over to the tvheadend git branch, please pull down the latest image at your convienience.

Thanks for the quick resolution! I've been testing the image for the past hour and everything seems to be working just fine.

I recently updated hardware from i5-9600T (UHD 630 iGPU) to i7-11700t (UHD 750 iGPU) and also unRAID from 6.12 to 7.2.3.
TVHeadend can no longer record with vaapi intel acceleration. I see with intel_GPU_top that it is using the device, but I only get proper audio with some scrambled color video blocks/blobs. When running 'ls -al /dev/dri' in the container terminal(right), I noticed it doesn't say video(just audio) like it say in the main unRAID terminal (left):


Can someone that has VAAPI transcoding working please run the ls -al /dev/dri and give me the output from the TVHE container console? Any tips appreciated. I did see multiple reports of issues with 10th and 11th gen iGPU but they all seem to be from around 2021 and it seems should be fixed by now.

This is what the video recording looks like:

Edited January 22Jan 22 by OrdinaryButt

On 4/19/2023 at 2:44 PM, bally12345 said:

Hi All

 

How do I define extra parameter

 

I tried --device=/dev/dvb however that is not a valid node.

 

I have a Sundtek USB DVBT2/C tuner 

Apr 19 10:04:34 Server kernel: usb 2-2: new high-speed USB device number 7 using ehci-pci

Bus 002 Device 007 Port 2-2ID 2659:1401 Sundtek MediaTV Digital Home III (EU)

 

After installing the driver it says

ATTENTION: Please don't forget to pass through the device:

/dev/bus/usb

 

--device=/dev/bus/usb 

 

However it is still not detected.

Did you fix this? I have same issue with TBS USB device