Wintv Stick

[Vicki Patolot]

Idiscovered it was down to the USB hub, or sticks, in that if I I unplug the hub from the raspberry pi and power off the sticks, the raspberry pi comes back to life. After a few moments I plug the tuner sticks back in an off we go with no trouble.

Hello,

Following the original post i plugged the HDD into the PI directly. The auto-mount function seemed to work better.

Anyway following your post above, I installed a second USB hub and connected the HDD to the USB hub. So to confirm the current profile.

Raspberry PI

Belkin Hub - 2 x USB Hauppage TV tuners

Belkin Hub - 1 x WD HDD

Re the power to the house. The Vero 4k unit and the Raspberry Pi (TV server) are on separate wall sockets, both in the lounge. So in principal when we had a power blip, both had issues (the Vero rebooted mid show, and the raspberry pi (TV server froze).

I reformatted your lsusb output in your post above; the only info I can read from this is that each Hauppauge device tells a connected USB port to have the max power current of 500 mA which is the maximum a single USB port can deliver.

So, it depends on the used USB hub whether it is able to provide 3 x 500 mA for HDD and the Hauppauge devices.

Do you have experience with the OSMC hubs? I bought one recently to work with three Hauppauge TV sticks, one of which is a dual tuner (hence pulls a little more current). But in theory should be 1500 mA so okay

hello Sam,

I tried in my PC and it worked great. I then plugged the hub back into the Vero4k and the Raspberry Pi and it worked a treat. So sorry for raising the issue. Not sure why there was an issue in the first place, probably me.

I'm trying to use Hauppauge's winTv soloHd USB stick on ubuntu 16.04 and 15.10, both seem to detect the stick, but kaffeine as well as me-tv both say there's no dvb device attached to the computer; I get UNCLAIMED when running lshw (translated):

If you have those modules, they should just load and set up the device.. You could install the kernel source package and take a look if the source has the following lines from this patch, _tree.git/commit/?id=1efc21701d94ed0c5b91467b042bed8b8becd5cc.

The newest kernel my system offers is the one I have installed. On the other hand, justyesterday a new beta of Linux Mint (18.0) has been released, based on a much newer version of Ubuntu; the official release should be this month. (And yes, I checked: newer kernel version and everything! \o/ ).

i hope someone here can help me. I have exact the same problem but i want to run the tvheadend-version on my raspberry. Actually just for testing. Later it should work on my Synology DS414 where the tvheadend installation don't see the wintv soloHD-Stick.

Firmware is missing xD you need to get those firmware files "dvb-demod-si2168-02.fw" is an older backup firmware, don't bother with that. you can find the firmware here -firmware/tree/master/firmware make sure you get the raw file (click on the filename in the list and press the raw button). -firmware/raw/master/firmware/dvb-demod-si2168-b40-01.fw

For years I have been using the Terratec Cinergy HTC Stick on Windows 7/8 computer and using DVBViewer Pro without issues, however moving to a new computer with Windows 10 I could not get the Cinergy HTC Stick drivers to work so I acquired the Hauppauge WinTV-soloHD.

Unfortunately the WinTV-soloHD / DVBViewer combination is giving me grief. Through the forum I learned that there was a Hauppauge service which I needed top stop running as it blocked DVBViewer from using the WinTV-soloHD, however having solved that I now find that the only a fraction of the TV channels available are found and no radio channels at all(list is included).

I'm located in Denmark and using cable with Yousee as the cable provider. If I run the WinTV V10 software that came with WinTV-soloHD there is no problem accessing all the usual channels, same ones I also had with the Cinergy HTC/DVBViewer combination on my old computer. A list of those channels as they shown with the WinTV is attached. Needless to say, apart from finding all the channels WinTV is a program that is severely lacking.

The service I stopped is called 'Hauppage TV Server' only as I went to look up the name right now I actually found it to be running again, only with no effect on DVBViewer accessing the hardware. Maybe it is just it running, but that it also had to be activated by the WinTV software for it to be causing the DVBViewer not to connect to the hardware.

Regarding cable reception, it has to be considered that besides the frequency there are two other important reception parameters: The symbolrate and the modulation. Some devices/drivers are able to detect the modulation automatically by trying one after the other. They don't mind if it is set up wrongly in the application. The only side effect is that channel switching takes longer. Other devices are not able to auto-detect the modulation. If you change to one of them, you may find that channels don't work anymore because the modulation in the channel list is wrong (see DVBViewer Channel Editor for details). Or channel search does not yield results, because the modulation is specified wrongly in the transponder list.

For trying different parameters I strongly recommend to use the scanner & transponder list editor TransEdit (see members download area). It may even be able to automatically create a transponder list tailored for your needs, based on information that I found here in the "Anden digital boks" section. I don't understand Danish, but I guess that are the parameters for the home frequency that provides information about all other frequencies in its Network Information Table (NIT).

I have been using the Denmark-Yousee -DVBC transponder list as it came with the latest DVBViewer version. I have attached it here for easy access, it is the one named DVBC_den_YouSee.ini

Just to try TransEdit while looking at the Yousee website I made do a scan using the Yousee file as stock, it not only found all the channels including those I have been missing, but testing using the Preview function they also work fine. So thinking I this was it I saved the channel list and imported it to DVBViewer only to find that the channels doesn't work there. So all good in TransEdit and no good in DVBViewer.

Using the info from the Yousee website and your description I had TransEdit do the Update thing which seemed to work, after which I had transEdit do a channel scan and this then went really quick as it did so using a much narrower search area than using the stock Yousee file. This search then found all the channels again and as before they work with preview, but once imported to the DVBViewer there is again no joy. For the files see the DVB-C_Denmark_Yousee_Custom ones attached.

I also tried using the custom transponder file created using transEdit to do a scan with DVBViewer, but doing so it find no channels. It seems DVBViewer is somehow using the hardware differently than TransEdit, my DVBViewer hardware setting can be seen from the image I have attached.

The WinTV-soloHD is listed as two devices, one for DVB-T and one for DVB-C and apparently one needs to uncheck the "Use device" check box on the DVB-T one for the DVB-C scan to find all the channels. I am wondering if perhaps the few channel I could find earlier is actually found as terrestial. I'm glad to now have all my channels, but it was a time consuming journey ?

The point is, the reception type of your DVB-T tuner is wrongly set to DVB-C! I can see the problem now in the hardware.xml from your support.zip. That's why DVBViewer tried to use it for DVB-C, because the first device from the top has the highest priority.

It's obviously a misconfiguration. I didn't check it, because I didn't expect that a user would do something like this. That's a lesson for me too! I think we should consider to disable the tuner type selection for physical (hardware) tuners with a fixed tuner type and only allow to change it by tweaking the hardware.xml.

Either a change in the hardware.xml or a clear indication of the type of signal searched would be good, the later would have told me on the first search something was up. It would also be good if DVBViewer and TransEdit worked in the same way, although had they done in this case I would likely have given up on the Happauge or maybe even on DVBViewer.

Do not get me wrong. I am a big fan of DVBViewer, the functionality being much better than what I see from the software that comes with the hardware. Only i imagine some potential customers are maybe scared away by the technical aspects, to a degree I think many expect it to be much more plug and play.

The main problem with DVBViewer is that some settings do not work without letting you know they don't work. In my case the tuner was selected as DVB-C in the hardware setting (and appeared to accept the setting) , the hardware file (for the Terratec version it's an ini not xml) showed it as being set on DVB-C but it was actually trying to tune on DVB-T because the tuner was not in the hardware database.

since I also use the WinTV solo usb stick (after many years of using Cinergy HTC stcik) I would like to ask you the following questions. My system is a Acer notebook with windows 10 (newest update) and the newest drivers by Hauppauge from 05.2020.

- the WInTv solo stick is not automatically reocgnized during system start, i.e. the stick in inserted but the Device Manager does not list it and in one of the USB devices there is the message "invalid device description returned" (something like this)

3a8082e126