what about which version tvheadend is on vero4 64bit or 32bit ?
from sundtek forum:
It’s just like this:
If TVHeadend 64Bit is installed then the 64Bit driver needs to be installed.
If TVHeadend 32Bit is installed then the 32Bit driver must be installed.
I would not be clear why TV Headend should have a scan problem, if it sees the tuner then it works too. If it does not see the driver then the wrong driver is installed - there are not many other options.
You can also unpack the files and simply copy them over the existing ones on the system.
Is this a new Sundtek tuner?
Was this working previously with Vero 4K? or Rasp Pi?
Can you please post a link to the exact tuner that you have.
I am using two Sundtek tuners (one DVB-T and one DVB-S) with Vero 4K, and all I need to do is run the sundtek.sh script. Both tuners work with very well with TVH on OSMC with no issues and no additional configuration required.
If it’s a new tuner, then maybe there is something new/changed in Sundtek tuners.
It might be necessary to contact Sundtek.
Are you running two instances of TVH? If you get ‘Address already in use’ for port 9981, then it means that TVH is already running, and listening on that port.
That’s what I’m wondering. He seems to be trying to start tvh manually and may have compiled it or installed from another repo or deb when that’s not necessary.
I would clear out all traces of TVH with apt-get purge and find -name tvheadend and start again with the AppStore install.
What i am done is copy old tvheadend directory from old vero 4 system to newly installed osmc vero4 and tvheadend dont see my adapter but from sundtek own mediaclient for example i can play channels on PC.
i think i need completely uninstall tvheadend .
yes i have and i tried without second tuner but no luck
Yes, I think you should start again with a new installation of OSMC on Vero 4K.
When OSMC is installed, then install the TVHeadend app from the OSMC App Store.
When that is done, then download and run the sundtek.sh script.