Xbox One DVB-T/T2/C tuner

noggin · 2014-10-21T15:38:04+00:00

Hi all This looks like it could be very good value if Open Source drivers appear for it : http://www.xbox.com/en-GB/xbox-one/accessories/digital-tv-tuner#fb...

Luka Karinja

It works perfectly for DVB-T Slovenia and Italy muxes
Arch Linux with kernel 4.19.37

Hilman Chung

C vH wrote:

> sadly the stick has major problems at some stations, but that is not linux driver related because the same happens at the Xbox too :(

Hi C vH, sorry to bother (can't register on Libreelec), but your repository for nightly TVH builds seem to be down...

CvH

> but your repository for nightly TVH builds seem to be down

yes should be fixed this week (wrong bank account at the provider -> not paid :P )

> can't register on Libreelec

currently closed due HEAVY amount of chinese crap spam (2k messages in 1h)

Hilman Chung

C vH wrote:
> > but your repository for nightly TVH builds seem to be down
>
> yes should be fixed this week (wrong bank account at the provider -> not paid :P )

ha, no worries, would you mind to put the latest test builds on dropbox or google-drive? The site is still down and I would like to mess around with my rpi this weekend...

CvH

https://1drv.ms/f/s!Ap8mNU55Kk6C3Tu8qNMuDfyd1_aj

have fun :) hopefully everything is working soon again

zil dan

My configuration:

HTS Tvheadend 4.3-1857
Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-76-generic x86_64)

DVB-C with 4x Xbox One DVB-T/T2/C tuner

VAAPI i915 v1.6.0 (/dev/dri/renderD128)

In short I have the following configuration:
With hardware profile, all DVB-C channels on QAM64 tp work perfectly.
On QAM256 TPs errors occur and after a while the h264 hardware decoder is blocked until the channel is changed.
If I uncheck Hardware acceleration the viewing can be done despite the stream errors.

It is obvious that the problem comes from the USB tuner or more precisely from the drivers, but there could be a change in the TVH to restart the Video stream in libav.

Attach a log:


02:52:07.439 libav: AVCodecContext: reference picture missing during reorder
02:52:07.439 libav: AVCodecContext: Missing reference picture, default is 66123
02:52:07.771 libav: AVCodecContext: mmco: unref short failure
02:52:24.677 TS: DIGI/442MHz/DIGI Sport 3 HD: H264 @ #1711 Continuity counter error (total 2)
02:52:36.939 TS: DIGI/442MHz/DIGI Sport 3 HD: H264 @ #1711 Continuity counter error (total 3)
02:52:37.002 libav: AVCodecContext: Found reference and non-reference fields in the same frame , which
02:52:37.002 libav: AVCodecContext:  is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
02:52:37.002 libav: AVCodecContext: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
02:52:37.002 libav: AVCodecContext: decode_slice_header error
02:52:37.002 libav: AVCodecContext: Failed to upload decode parameters: 18 (invalid parameter).
02:52:37.002 libav: AVCodecContext: Failed to end picture decode after error: 18 (invalid parameter).
02:52:37.002 libav: AVCodecContext: hardware accelerator failed to decode picture
09:37:13.088 libav: AVCodecContext: Missing reference picture, default is 95603
09:37:13.230 libav: AVCodecContext: reference picture missing during reorder
09:37:13.230 libav: AVCodecContext: Missing reference picture, default is 95610
09:37:13.347 libav: AVCodecContext: reference picture missing during reorder
09:37:13.347 libav: AVCodecContext: Missing reference picture, default is 95618
09:37:13.347 libav: AVCodecContext: mmco: unref short failure
09:39:04.717 TS: DIGI/442MHz/Channel HD: H264 @ #1711 Continuity counter error (total 9)
09:39:04.813 libav: AVCodecContext: Found reference and non-reference fields in the same frame, which
09:39:04.813 libav: AVCodecContext:  is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
09:39:04.813 libav: AVCodecContext: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
09:39:04.813 libav: AVCodecContext: decode_slice_header error
09:39:04.813 libav: AVCodecContext: Failed to upload decode parameters: 18 (invalid parameter).
09:39:04.813 libav: AVCodecContext: Failed to end picture decode after error: 18 (invalid parameter).
09:39:04.813 libav: AVCodecContext: hardware accelerator failed to decode picture

Gurabli Gurabli

Hi,
I am thinking to get one of these for DVB-C on Rpi2/3 running Dietpi or Nanopi Neo2 weith Dietpi or Armbian.

Will run Tvheadend. Provider DIGI Hungary.

Any info if it is working fine for DVB-C? Low or high freq too? No continuity or lock errors?

Walter av

Hi Gurabli Gurabli,

Sadly for the Xbox tuner low and high frequencies errors on DVB-C qam256, the least was ~15/20 an hour both on shielded, correctly wired, filtered and amplified setups have been tested. Only DVB-T2 has been fine if reception is clean/strong with external antenne H265&AAC with FTA 1080p50. The results were similar on RPI3 vs x86.

If you want a correct working (dual)tuner for DVB-C use the "Hauppauge WinTV-DualHD 01590" (USB id 2040:0265 Hauppauge) or go HD-homerun quad.

You may even find a triple tuner, with iptv capabilities but not compatible yet with Tvheadend or Satip(tuner sharing) like the MUT@NT HD530C TRIPLE DVB-C which may cover you needs.

Gurabli Gurabli

Hi Walter,

Sorry to hear, I thought the Xbox tuner will work fine.

So you say the Hauppauge WinTV-DualHD 01590 is working perfectly with DVB-C, no problems at all? I already looked at this stick, but didn't find anything that confirmed it is working fully as it should.

I have a Mygica/Geniatech T230 in use now, but have problems with certain frequencies, and get continuity errors, glitches.

If you say the wintv-dual is running great, than I will buy one.

Gurabli Gurabli

One more thing: are both dvb-c tuners working now?
I am getting one and I do hope there will be no continuity errors or similar problems.

Walter av

Gurabli Gurabli to answer both questions, yes dual tuners are working. You have to use a recent 4.17 kernel or a hauppauge supported ubuntu kernel. On recent debian 10 buster it works ootb with only firmware requirement. See this thread for more info including comprehensive support for custom kernel (not necessary anymore):

https://ubuntuforums.org/showthread.php?t=2336566

Gurabli Gurabli

Walter av wrote:
> Gurabli Gurabli to answer both questions, yes dual tuners are working. You have to use a recent 4.17 kernel or a hauppauge supported ubuntu kernel. On recent debian 10 buster it works ootb with only firmware requirement. See this thread for more info including comprehensive support for custom kernel (not necessary anymore):
>

> https://ubuntuforums.org/showthread.php?t=2336566

Many thanks! Well, the kernel on Rpi and Neo2 are both higher versions than 4.17, so it should not be a problem. You mean every kernel after 4.17 has the support or it has to be 4.17?

Walter av

The Hauppauge support by Brad Love mostly get upstreamed to the linux media tree, in this case it means that support has landend in 4.17 and higher. Debian 10 works with linux 4.19 and its working ootb. However it can be that in future versions regressions can break things but be sure to check out https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder.

Gurabli Gurabli

Thank you, Walter.

I will receive my DualHD on Monday, hope it will work as it should. Your help is very much apprecieted.

Btw, do you think minisatip can be a good solution for me? It would be a source for a Tvheadend backend on remote location.

Walter av

Hi Gurabli Gurabli did you have any success with the Hauppauge dualHD already?

About satip, by default it uses some layer2 network tricks to get recognized by devices in local networks, which means you need to make a remote tunnel to make it function like it was designed. However minisatip and tvheadend are very configurable and you maybe able to make it work in a ip layer3 only routed fashion. Remember that Tvheadend HTSP protocol was designed to work over low quality network links from server to client but satip may need a better local wired connectioning with change in frame/packet size it will probably depend on client and channel/provider/hd/sd etc.

Tom Joyce

Perhaps foolishly, I started an entirely fresh install of the OS Formerly Known As Raspbian with the Buster kernel on my Pi3 with it's X-Box tuner that was, at that stage, working reasonably. Updated and upgraded everything, then proceeded to install tvheadend and dvb-demod-mn88472-02.fw, the firmware that has served me in the past from this thread. Saw the tuner, told it to look for the Sutton Coldfield muxes, but their scan status stays resolutely at PEND. Which is annoying. Extracting from dmesg I have the following


[    5.318738] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware
[    5.387491] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[    5.724628] dib0700: firmware started successfully.
[    6.239883] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
[    6.240645] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    6.250439] dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
[    6.536169] mn88472 3-0018: Panasonic MN88472 successfully identified
[    6.588066] tda18250 3-0060: NXP TDA18250BHN/M successfully identified
[    6.590327] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)...
[    6.590653] dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
[    6.591085] usbcore: registered new interface driver dvb_usb_dib0700
...
[   12.696260] mn88472 3-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw'
[   12.919328] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)

Can anyone suggest what the problem may be?

B W

Tom Joyce wrote:
> Perhaps foolishly, I started an entirely fresh install of the OS Formerly Known As Raspbian with the Buster kernel on my Pi3 with it's X-Box tuner that was, at that stage, working reasonably. Updated and upgraded everything, then proceeded to install tvheadend and dvb-demod-mn88472-02.fw, the firmware that has served me in the past from this thread. Saw the tuner, told it to look for the Sutton Coldfield muxes, but their scan status stays resolutely at PEND. Which is annoying. Extracting from dmesg I have the following
>
>
> [...]
>

> Can anyone suggest what the problem may be?

Did you assign the tuner to the network in tvheadend? Otherwise you might try right click and force scan

Saen Acro

> Can anyone suggest what the problem may be?

Problem is that scan tables are old

tryW-SCAN to find correct frequency's


w_scan -f t -x

S W

This Xbox Tuner with MN88472 didn't work for me for DVB-T2 either:
drivers, firmware got loaded:

usb 1-4.1: new high-speed USB device number 19 using xhci_hcd usb 1-4.1: New USB device found, idVendor=045e, idProduct=02d5, bcdDevice= 1.10 usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-4.1: Product: Xbox USB Tuner usb 1-4.1: Manufacturer: Microsoft Corp. usb 1-4.1: SerialNumber: 001097280915 dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' dib0700: firmware started successfully. dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner) usb 1-4.1: media controller created dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. mn88472 13-0018: Panasonic MN88472 successfully identified tda18250 13-0060: NXP TDA18250BHN/M successfully identified usb 1-4.1: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)... dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88472' registered. dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected. usbcore: registered new interface driver dvb_usb_dib0700 mn88472 13-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw'

when doing


w_scan -f t -c DE


./w_scan2 -c DE -f t2 
w_scan2 version 1.0.10 (compiled for DVB API 5.11)
using settings for GERMANY
DVB aerial
DVB-T Europe
scan type TERRESTRIAL, delivery system SYS_DVBT2, channellist 4
output format vdr-2.0
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
	/dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Panasonic MN88472": very good :-))

Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'Panasonic MN88472' supports
DVB-T2
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
BANDWIDTH_AUTO not supported, trying 6/7/8 MHz.
FREQ (42.00MHz ... 870.00MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
Scanning DVB-T2...
Scanning 7MHz frequencies...
177500: plp0 (time: 00:00.196) 
184500: plp0 (time: 00:02.236) 
191500: plp0 (time: 00:04.240) 
198500: plp0 (time: 00:06.284) 
205500: plp0 (time: 00:08.320) 
212500: plp0 (time: 00:10.332) 
219500: plp0 (time: 00:12.332) 
226500: plp0 (time: 00:14.376) 
Scanning 8MHz frequencies...
474000: plp0 (time: 00:16.408) 
482000: plp0 (time: 00:20.816) 
490000: plp0 (time: 00:22.848) 
498000: plp0 (time: 00:24.864) 
506000: plp0 (time: 00:26.864) 
514000: plp0 (time: 00:28.900) 
522000: plp0 (time: 00:30.920) 
530000: plp0 (time: 00:35.440) 
538000: plp0 (time: 00:37.472) 
546000: plp0 (time: 00:39.492) 
554000: plp0 (time: 00:41.508) 
562000: plp0 (time: 00:43.516) 
570000: plp0 (time: 00:45.564) 
578000: plp0 (time: 00:50.052) 
586000: plp0 (time: 00:52.100) 
594000: plp0 (time: 00:54.108) 
602000: plp0 (time: 00:56.120) 
610000: plp0 (time: 00:58.144) 
618000: plp0 (time: 01:00.164) 
626000: plp0 (time: 01:02.168) 
634000: plp0 (time: 01:04.192) 
642000: plp0 (time: 01:08.852) 
650000: plp0 (time: 01:10.884) 
658000: plp0 (time: 01:12.924) 
666000: plp0 (time: 01:17.468) 
674000: plp0 (time: 01:19.485) 
682000: plp0 (time: 01:21.505) 
690000: plp0 (time: 01:26.001) 
698000: plp0 (time: 01:28.021) 
706000: plp0 (time: 01:30.037) 
714000: plp0 (time: 01:32.065) 
722000: plp0 (time: 01:34.085) 
730000: plp0 (time: 01:36.093) 
738000: plp0 (time: 01:38.097) 
746000: plp0 (time: 01:40.129) 
754000: plp0 (time: 01:42.149) 
762000: plp0 (time: 01:44.161) 
770000: plp0 (time: 01:46.177) 
778000: plp0 (time: 01:48.193) 
786000: plp0 (time: 01:50.209) 
794000: plp0 (time: 01:52.217) 
802000: plp0 (time: 01:54.241) 
810000: plp0 (time: 01:56.261) 
818000: plp0 (time: 02:01.069) 
826000: plp0 (time: 02:06.769) 
834000: plp0 (time: 02:08.797) 
842000: plp0 (time: 02:10.801) 
850000: plp0 (time: 02:15.389) 
858000: plp0 (time: 02:17.393) 

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

I am nealy sitting next to the tower transmitting DVB-T2 on e.g. 522MHz.
I was trying RaspberryPi 4b with 32bit-kernel, userland kernel ~4.19
I tried Ubuntu 20.10 64bit kernel 5.4.0-33

I tried RaspberryPi 4b with 32bit-kernel, userland kernel ~4.19 with theRaspberry TV HAT where ifound all muxes and channels.

While doing

w_scan or w_scan2 i can see, that


dvb-fe-tool --femon

does show some lines with Vertibi or even Carrier but never Locks when scrolling past frequencies that match the senders scheme in w_scan*.

CvH

The DVB Tuner is known to have problems at some regions. The same happens if you put the tuner at the Xbox so it is likely a firmware/hw problem of the stick.
At other regions the stick works great.

« Previous Page Next Page »