@bbubulka said:
@bbubulka said:
@bbubulka said:
I think I know whats happening! I think its a kernal version issue. I started on 16.04.02. After reading through Hauppauge’s documentation again, I noticed their statement “Please note: only Linux Kernel 4.4 is supported at this time. This is the default kernel in Ubuntu 16.04.1”! I’m created a brand new virtual machine and will test this out. If this happens to be the case, WOW! More info to come!
So initial testing still shows no channels. I’m testing running Ubuntu 16.04.1 (Kernal 4.4) and Plex Server Version 1.7.2.3878 and followed directions per Hauppauge’s website. Ill recheck the logs.
@keithah , Here’s my logs below. This is a fresh install of Ubuntu 16.04.01 and Plex Server Version 1.7.2.3878
UPDATE: I ran everything again I mentioned in my earlier post with no success. I also ran software from How to Obtain, Build and Install V4L-DVB Device Drivers - LinuxTVWiki which had no impact either. W_SCAN still works and picks up signals:
w_scan -fa -A1 -c US -X
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for UNITED STATES
ATSC
VSB US/CA, DVB-T TW
scan type TERRCABLE_ATSC, channellist 1
output format czap/tzap/szap/xine
WARNING: could not guess your codepage. Falling back to ‘UTF-8’
output charset ‘UTF-8’, use -C to override
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 → TERRCABLE_ATSC “LG Electronics LGDT3306A VSB/QAM Frontend”: good 
Using TERRCABLE_ATSC frontend (adapter /dev/dvb/adapter0/frontend0)
---- Getting frontend capabilities----
Using DVB API 5.10
frontend ‘LG Electronics LGDT3306A VSB/QAM Frontend’ supports
INVERSION_AUTO
8VSB
QAM_64
QAM_256
FREQ (54.00MHz … 858.00MHz)
-----------------------_
- MANY ENTRIES OMITTED TO SAVE SPACE -
189000: 8VSB(time: 00:24.636) signal ok: 8VSB f=189000 kHz (0:0:0)
491000: 8VSB(time: 00:51.104) signal ok: 8VSB f=491000 kHz (0:0:0)
521000: 8VSB(time: 01:06.277) signal ok: 8VSB f=521000 kHz (0:0:0)
539000: 8VSB(time: 01:14.717) signal ok: 8VSB f=539000 kHz (0:0:0)
557000: 8VSB(time: 01:23.097) signal ok: 8VSB f=557000 kHz (0:0:0)
569000: 8VSB(time: 01:28.209) signal ok: 8VSB f=569000 kHz (0:0:0)
623000: 8VSB(time: 01:59.846) signal ok: 8VSB f=623000 kHz (0:0:0)
641000: 8VSB(time: 02:10.650) signal ok: 8VSB f=641000 kHz (0:0:0)
653000: 8VSB(time: 02:15.690) signal ok: 8VSB f=653000 kHz (0:0:0)
665000: 8VSB(time: 02:20.702) signal ok: 8VSB f=665000 kHz (0:0:0)
…
Done, scan time: 05:00.360
and you ran “sudo usermod -a -G video plex” right, to make sure plex user has access to the DVB devices?
@keithah said:
and you ran “sudo usermod -a -G video plex” right, to make sure plex user has access to the DVB devices?
Yes, I did. I believe the logs below also confirms Plex has access to the device:
INFO - * v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
INFO - * dvb_device_factory_t::get_device_list. Id dvb#v4l#0#/sys/devices/pci0000:00/0000:00:11.0/0000:02:02.0/usb1/1-1/1-1:1.1, Name Hauppauge Device, Standards 24
Still seeing the following warnings and errors:
WARN - [W] CV4lTunersStreamSrc::Start. pthread_setschedparam failed 1
WARN - [E] dvb_channel_scanner_t::do_scan. Tune failed for ####
One new log I’m noticing now is:
DEBUG - * DTV_STAT_CNR has failed for tuner 0, frontend 0
Sorry I only searched with Google (I blame them 
) before I posted my question at forums.plex.tv/discussion/274842/wintv-hvr-955q-not-finding-channels#latest which can be removed if the mods would like.
Installed Plex 1.7.2 clean on this computer yesterday (only Windows machine I have). I was excited to try out the live TV/DVR feature. Especially since I bought this darn XboxOne adapter and it’s been collecting dust.
Anyways, Plex is detecting the adapter. I have the type set to ‘Antenna’ and country of ‘United States’. Scanning keeps returning no channels though. I’ve restarted (I’m a sysadmin… insert IT Crowd joke here), changed usb ports, moved the antenna around, etc. I’m in an area where I have issues picking up a couple of local stations, but our NBC & PBS always come in strong almost no matter what. So I don’t think it’s a signal issue. I don’t have a TV in this room unfortunately to test with and no other TV Tuner software on this computer. I got the driver from Hauppauge’s site directly as well.
Here’s some other maybe pertinent info.
OS: Windows 10 Pro 1703 x64
Hauppauge driver version: 6.0.119.34217
Not sure it helps but my XB1 tuner works with my nvidia shield. Shows up in Plex as WinTV-HVR-955Q
@keithah said:
@MastermindJB Heard back from the devs and it sounds like its a permission issue. Can you make sure no other app has the tuner, like WinTV? If that doesn’t solve it, try to run Plex Media Server as your user, or as an administrator and see if that helps.
I don’t have WinTV even installed and I first plugged this tuner directly into the machine that has my media server on it specifically for this. My user account is full admin, but I’ll try some tweaking to it tomorrow after work and see what I find.
Same issue, same errors on Windows 10, I’m going through some testing of disabling as much as a can on the computer to see if something I have installed is conflicting with the tuner or causing it to be locked. I’ll post back if I find anything but wanted to add another hand up in this thread.
So that worked fairly well, I disabled pretty much everything, restarted plex, no difference. Then I thought about what else was left which was completely exiting my AV (Trend Micro, i had disabled it before) and exiting my remote desktop service (Team Viewer). I disabled both and switched to chrome remote desktop. At this point I realized that out of everything that could possibly be “using” the tuner it was likely TeamViewer. Sure enough it started working after that. Poking around in team viewer it looks like it was trying to use the 995q as a “capture” device for a camera for video conferencing. I havent confirmed yet that disabling that fixes it permanently (its getting late)… but that’s my suspicion.
TL;DR: exit all peripheral apps/services and try again, especially Team Viewer or anything else that is more likely to “grab” the tuner as a video or audio input.
Good luck!!!
@jaredw13 Thanks so much for reporting this!
@mastermindjb and @indyhill can you guys try to disable stuff like @jaredw13 said above and see if that solves your isse?
@keithah said:
@jaredw13 Thanks so much for reporting this!
@mastermindjb and @indyhill can you guys try to disable stuff like @jaredw13 said above and see if that solves your isse?
Interesting. I’ll try it tonight. I don’t have TeamViewer installed, but I believe Chrome Remote Desktop is.
@indyhill think of anything else that is installed that could use a video input device, like webcam software, Skype, messengers, VoIP clients with video capabilities. The tuner shows up as any standard webcam would so those apps may be grabbing it when they start.
Same goes for the audio input of the tuner, but I’m not sure of that affects Plex.
I was using Chrome remote desktop and it didn’t affect Plex at all, so that’s not likely your issue but you may want to kill almost everything that’s running except core services to see if you can at very least get it working.
Good luck!
Any info @keithah about when/if the 955q will be supported on the ShieldTV?
@spamies says his works already, but we had some issues in our testing which is why it isn’t on the list. Try it and let us know how it goes?
@jaredw13 said:
@indyhill think of anything else that is installed that could use a video input device, like webcam software, Skype, messengers, VoIP clients with video capabilities. The tuner shows up as any standard webcam would so those apps may be grabbing it when they start.
Same goes for the audio input of the tuner, but I’m not sure of that affects Plex.
I was using Chrome remote desktop and it didn’t affect Plex at all, so that’s not likely your issue but you may want to kill almost everything that’s running except core services to see if you can at very least get it working.
Good luck!
Grrrr, you know what it was? Windows decided to use it as the default recording device and default communications device which was locking it. I set the internal microphone on this iMac back to the default and it’s scanning away now. Thanks for the suggestions folks. I wouldn’t have thought to look for it as a standard audio device.
@spamies said:
Not sure it helps but my XB1 tuner works with my nvidia shield. Shows up in Plex as WinTV-HVR-955Q
Do you get actual channel reception? Mine shows up, but says “weak signal”.
@keithah said:
@spamies says his works already, but we had some issues in our testing which is why it isn’t on the list. Try it and let us know how it goes?
Mine is the actual WinTV-HVRE-955Q, not the Xbox 1 branded version. I am not sure what the HW differences (if any) are.
I get “weak signal” error from when view through Live Channels, but when I switch between channels I will get brief frame images of the prior channels show. I also am able to get reception from the same tuner/cabling when it is plugged into my XB1, so don’t think it is a true weak signal issue.
Tuner is recognized by Plex, but again get no channel reception via Plex Scan.
Live channels gives weak signal too? Then that’s likely your problem.
The xb1 driver could be better than the Linux one with weak signal… Not sure.
@keithah said:
Live channels gives weak signal too? Then that’s likely your problem.
The xb1 driver could be better than the Linux one with weak signal… Not sure.
I have reworked some cabling, and the USB tuner is now recognized by Plex.
@keithah FYI, I did get my Ubuntu setup to finally work last night! I found the issue to be with VMware ESXi. Even though I added the USB device to the server (VM) and PLEX saw the USB device, it would never pick up any channels. I completely wiped the server clean, installed Ubuntu 16.04.1 directly to the server (no virtualization) and followed the directions in Hauppauge’s Guide (which I did before) and all works fine now! Not sure what VMware is blocking or not allowing but wanted to give you a heads up in case others are virtually running machines. Maybe theres additional steps I haven’t found yet.
@spamies said:
Not sure it helps but my XB1 tuner works with my nvidia shield. Shows up in Plex as WinTV-HVR-955Q
Just wanted to confirm, I also have the XB1 tuner, and the Nvidia Shield. The tuner shows up the same as you mention, but when I select “scan channels” I get “No Channels Found”
Is there a secret to getting this working?
@TrikAiden said:
@spamies said:
Not sure it helps but my XB1 tuner works with my nvidia shield. Shows up in Plex as WinTV-HVR-955Q
Just wanted to confirm, I also have the XB1 tuner, and the Nvidia Shield. The tuner shows up the same as you mention, but when I select “scan channels” I get “No Channels Found”
Is there a secret to getting this working?
Had this issue up until this morning and the only difference is I tried the channel scan from my work pc as opposed to a pc on my home network. Found 9 channels and works with Nvidia shield and the 955Q tuner. Prior to this the tuner would be recognized in Plex but the scan would finds 0 channels. Strange.
Update
I have not been able to replicate this process on the xbox one tuner to get it to find channels. It was a 1 and done deal. 9 channels found on a random scan. The only other thing I did before the scan worked was I unplugged the HD tuner from the shield and plugged it back in before scanning. On another note I had an HDhomerun connect box just sitting in waiting to replace the Happauge tuner and once I did I got the results I expected. Not only do I now get audio from OTa channels due to audio passthhrough options, but I got 26 channels as opposed to 9 on the USB tuner.
