Tvheadend

lord slash wrote:

Anyway did you give a look at the media_build_for_14.10.tar.bz2 driver that the device producer sent me? Let me know if there's something that I can ask them because I am in contact with them and they seem kind of helpful

This is old sources, for T230 (0xc6887/0xc688) and X9330 (VID = 0xd230 - 0xd233)

PadTV HD 2.1.7.7 support T230C

cool! does this mean that you are getting closer to the support of the T230C for linux?

please check T230C support @ my linux_media using my media_build

git clone https://bitbucket.org/CrazyCat/media_build
cd media_build
./build --main-git
sudo make install


required tuner/demod firmwares attached and also included in dvb-firmwares.tar.bz2 @ my media_build

P.S. Look like my T230C sample now have brocken LNA before tuner and can't lock anything from my outdoor ant for low-power transmitter (500W and 40Km dist).

oh that's great! Now I am trying to figure out how to install it on my RaspberryPi 2 with OpenElec (the file-system is read only) so any help would be appreciated!

I ended up installing it on my Raspbian system: I installed the media build from CrazyCat and the Stick is finally recognized by my Linux! I still do have a problem: TVHeadend doesn't detect my T230C stick.
Let's start with dmesg:
[ 7.376640] dvb-usb: found a 'Mygica T230C DVB-T/T2/C' in warm state.
[ 7.624033] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7.624255] DVB: registering new adapter (Mygica T230C DVB-T/T2/C)
[ 7.624290] usb 1-1.5: media controller created
[ 7.632782] dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 7.664157] i2c i2c-3: Added multiplexed i2c bus 4
[ 7.664192] si2168 3-0064: Silicon Labs Si2168-D60 successfully identified
[ 7.664211] si2168 3-0064: firmware version: D 6.0.1
[ 7.671857] dvb-usb: no frontend was attached by 'Mygica T230C DVB-T/T2/C'
[ 7.672603] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/input/input0
[ 7.672640] dvb-usb: schedule remote query interval to 100 msecs.
[ 7.672770] dvb-usb: Mygica T230C DVB-T/T2/C successfully initialized and connected.
[ 7.672964] usbcore: registered new interface driver dvb_usb_cxusb
[ 8.499721] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS
[ 8.512050] cfg80211: World regulatory domain updated:
[ 8.512091] cfg80211: DFS Master region: unset
[ 8.512105] cfg80211: (start_freq - end_freq bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 8.512133] cfg80211: (2402000 KHz - 2472000 KHz 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 8.512161] cfg80211: (2457000 KHz - 2482000 KHz 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 8.512186] cfg80211: (2474000 KHz - 2494000 KHz 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 8.512213] cfg80211: (5170000 KHz - 5250000 KHz 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 8.512227] cfg80211: (5250000 KHz - 5330000 KHz 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 8.512241] cfg80211: (5490000 KHz - 5730000 KHz 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 8.512252] cfg80211: (5735000 KHz - 5835000 KHz 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 8.512285] cfg80211: (57240000 KHz - 63720000 KHz 2160000 KHz), (N/A, 0 mBm), (N/A)
@

but then when i go on the web interface of TVHeadend Configuration-DVB Inputs-TV Adapters the list is empty :-( What am I missing now? By the way, HTS Tvheadend 4.0.8~jessie

Thanks again!

[ 7.664192] si2168 3-0064: Silicon Labs Si2168-D60 successfully identified
[ 7.664211] si2168 3-0064: firmware version: D 6.0.1
[ 7.671857] dvb-usb: no frontend was attached by 'Mygica T230C DVB-T/T2/C'


oops, minor bug just reconnect device or rebuild driver with fix
https://github.com/crazycat69/linux_media/commit/02fbba7099437238ac617423fdff7e341ee2ce3d

thanks, I didn't rebuild with the fix, I only reconnected the device and now the stick is recognized (Silicon Labs Si2168 : DVB-C #0 and Silicon Labs Si2168 : DVB-T #0 ).
DVB-T services are detected, but no DVB-T2. I am following this guide https://tvheadend.org/boards/4/topics/21148:

I have created a new network named DVB-T2 for this purpose and assigned it to my both receiver.
Afterwards, I created manually a new mux with the following data:
frequency (Hz): 650000000
Bandwidth: 8Mhz
Constellation: QAM/AUTO
Delivery System: DVBT2
I left any other value by default (or AUTO). I went back to Networks and selected the new network "DVB-T2" and clicked on "Force Scan".

but the scan result is always "fail". I tried to activate the debugging logs but it doesn't write anything.

What am I doing wrong this time?

Edit: I compiled the TVHeadend 4.1 but i get the same result.. (HTS Tvheadend 4.1-2247~gb23686a)

What Signal strength and SNR on dvb-t mux ?
You can test your t230c on windows or android ?

SNR 31 dB and Signal Strength -55dBm (average, it depends on the channel)
I can test my t230c on windows, I already did a scan some days ago and I found two DVB-T2 HD channels (ARD and ZDF)

I tried again with my windows laptop and i took a screenshot of the DVBViewer settings of the two DVB-T2 settings.

Edit: the frequency that is written in the guide is wrong (or anyway not valid for me). I just changed it to 642MHz (as showed in the DVBViewer settings) and the scan was successful! :-) I will make more tests now

I am trying to get tvheadend running in vmware Lubuntu with T230.

I have installed Lubuntu 16.04 as VM and installed tvheadend2247 to it. Running fine. Connected T230 from host to VM. Connection ok and Lubuntu and tvheadend can see T230 as right DVB tuner.

I made the setup ready but muxes cannot be scanned! All the time scan fail. Included couple of screenshots.

Using telnet restarted (sudo service tvheadend restart) service and - no change. What to do? Which options in telnet should I use to get more info to log? Someone said that I can use daemon with option -f, but what difference does it make and how to use it? How can I (re)start tvheadend from telnet so that all notifications and errors will be printed to telnet session?

I guess it is too early to know if DVB-C works with the T230C?

I have a different USB DVB-C adapter that only partly works with Linux and it would be great to find a cheap adapter that supports DVB-C. Most others are far too expensive but the T230C is reasonable at £18.

So I've been playing around with my PI and TVHeadend and it's almost working (but it's not yet).
SD channels work perfectly, but HD channels play very jerky and are not really watchable. I checked the CPU usage and when I watch HD channels it goes up to 100%.
I actually think it's a Kodi problem because when I watch HD channels with my computer and VLC (TVHeadend backend is still running on the PI) the CPU goes to 50% and it works flawlessy.
I tried to activate hardware acceleration on OMXPlayer (Settings-Videos-Acceleration) but then I can only hear the sound and there is no video.
I set the gpu_mem to 256 (should be the maximum for a Raspberry Pi 2).. Do you have any idea of what else can I try?

Have you paid for the RaspberryPi video codecs? It sounds like they are not present, which is why the CPU load is going up to 100%.

You need to purchase the codecs from here:

http://www.raspberrypi.com/license-keys/

Which will then allow for the built-in GPU to decide video and reduce the strain from the CPU.

There's a tutorial on how to setup the Pi with the codecs once you've purchased them here:

http://www.howtogeek.com/137654/how-to-add-mpeg-2-and-vc-1-video-codec-support-to-your-raspberry-pi/

I have a feeling there's a Kodi addon which allows you to enter the codecs from the GUI in Kodi, but I may be mistaken?

I've already bought both the codecs and they are enabled:

pi@raspberrypi:~/tvheadend $ vcgencmd codec_enabled MPG2
MPG2=enabled
pi@raspberrypi:~/tvheadend $ vcgencmd codec_enabled WVC1
WVC1=enabled

what else could it be?

by the way, I've already built TVHeadend twice but it never starts as service. I get the following error: pi@raspberrypi:~/tvheadend $ sudo service tvheadend start
Job for tvheadend.service failed. See 'systemctl status tvheadend.service' and 'journalctl -xn' for details.
pi@raspberrypi:~/tvheadend $ systemctl status tvheadend.service
● tvheadend.service - (null)
Loaded: loaded (/etc/init.d/tvheadend)
Active: failed (Result: exit-code) since Sat 2016-10-01 09:28:55 UTC; 43s ago
Process: 3524 ExecStart=/etc/init.d/tvheadend start (code=exited, status=203/EXEC)

and when I manually start TVHeadend it says
2016-10-01 09:27:17.328 [ NOTICE] START: HTS Tvheadend version 0.0.0-unknown started, running as PID:3455 UID:1000 GID:1000, CWD:/home/pi/tvheadend CNF:/home/pi/.hts/tvheadend

Anyway TVHeadend works (as I said SD channels work with Kodi on the same PI and SD/HD channels work with VLC on my laptop) so I would first focus on the problem with the HD channels with Kodi (which is my main goal) and then eventually I will figure out what's wrong with my tvheadend build

You definitely need to be using hardware acceleration (omxplayer or mmal) for HD H264 content. When it is turned off that's why you're getting 100% CPU.

When I activate mmal hardware acceleration the image gets jerky and the cpu goes 100%, when I activate omxplayer I can only hear audio (very fluid) but no video...
I've attached the kodi logs when I activate MMAL acceleration or OMX acceleration

So you can't lock dvb-t2 in linux with t230c ?

I think I can say that DVB-T2 works with your driver on Linux. So far, it works only when I use my laptop with Windows and VLC as client, but not when I use my PI with Kodi as client. I actually just tried to use VLC on my Android phone as client and the HD channels also don't work.. anyway I guess my phone is too slow for 1080p HD channels..
Anyway I'm still fighting with Kodi in order to find out which setting brings the CPU to 100% (I just tried to disable deinterlacing but it didn't change..)

edit: I will attach a screenshot I took at the info during the vision of an HD channel (transmitted via DVB-T2)

Hi folks,

I've also received c689 version of T230. Thanks to Crazy Cat's media_build I've successfully managed setting up drivers. Device is visible in tvheadend now. However I cannot search any muxes. I'm using DVBC with QAM256. If I try to add some manually, I get FAIL message. Any ideas?

Debug log says:
2016-10-02 21:14:17.000 mpegts: 146MHz in UPC - tuning on Silicon Labs Si2168 : DVB-C #0
2016-10-02 21:14:17.001 linuxdvb: Silicon Labs Si2168 : DVB-C #0 - failed to tune [e=Invalid argument]

w_scan output attached.

System info:
Bus 001 Device 005: ID 0572:c689 Conexant Systems (Rockwell), Inc.
uname -a: 4.4.0-040400-generic
lsb_release -a: Ubuntu 14.04.5 LTS (server)
tvheadend: version 4.0.9-13~g64fec81~trusty


try scan-s2 - https://bitbucket.org/CrazyCat/scan-s2

update: unfortunately the DVB-T2 stream in Germany is H.265 which is not supported by the Raspberry Pi 2.. any idea of what can I do?

Ha! Thank you Crazy Cat. I've successfully added muxes and search for channels. Output from scan-s2:

8 TV;UPCPL:122:M256:C:6900:101:102=pol:0:2:301:1537:3:0
Polsat Sport News;UPCPL:122:M256:C:6900:201:202=pol:0:2:302:1537:3:0
TVP Kultura;UPCPL:122:M256:C:6900:301:302=pol;308=pol:306:2:303:1537:3:0
ATM Rozrywka;UPCPL:122:M256:C:6900:401:402=pol,403=qaa:406:2:304:1537:3:0
TVP Historia;UPCPL:122:M256:C:6900:501:502=pol,503=aux:506:2:305:1537:3:0
TV 6;UPCPL:122:M256:C:6900:601:602=pol,603=qaa:0:2:306:1537:3:0
Polo TV;UPCPL:122:M256:C:6900:701:702=pol:706:2:307:1537:3:0
PULS 2;UPCPL:122:M256:C:6900:801:802=pol,803=aud:806:2:308:1537:3:0
TVP Rozrywka;UPCPL:122:M256:C:6900:901:902=pol,903=aux:0:2:309:1537:3:0
TTV;UPCPL:122:M256:C:6900:1001:1008=pol;1002=pol:1006:2:310:1537:3:0
TVP Info;UPCPL:122:M256:C:6900:1301:1302=pol:0:2:313:1537:3:0
TVP 3 KrakÂow;UPCPL:138:M256:C:6900:301:302=pol:306:2:5603:1537:56:0
TVP Polonia;UPCPL:138:M256:C:6900:401:402=pol;408=pol:406:2:5604:1537:56:0
TV 4;UPCPL:138:M256:C:6900:601:602=pol,603=und:606:2:5606:1537:56:0
Polsat;UPCPL:138:M256:C:6900:701:702=pol:706:2:5607:1537:56:0
TVN 7;UPCPL:138:M256:C:6900:1101:1102=pol;1108=pol:1106:2:5610:1537:56:0
Mango;UPCPL:146:M256:C:6900:101:102=pol:106:2:401:1537:4:0
Tele 5;UPCPL:146:M256:C:6900:201:202=eng:0:2:402:1537:4:0
TVP ABC;UPCPL:146:M256:C:6900:301:302=pol,303=aud:0:2:403:1537:4:0
Disney Channel;UPCPL:146:M256:C:6900:401:402=pol,403=eng:0:2:404:1537:4:0
Superstacja;UPCPL:146:M256:C:6900:501:502=pol:0:2:405:1537:4:0
Polsat 2;UPCPL:146:M256:C:6900:601:602=pol,603=und:606:2:406:1537:4:0
Stopklatka TV;UPCPL:146:M256:C:6900:701:702=POL:0:2:407:1537:4:0
TV Trwam;UPCPL:146:M256:C:6900:801:802:806:2:408:1537:4:0
TV Puls;UPCPL:146:M256:C:6900:901:902=pol,903=aud:906:2:409:1537:4:0
Galeria UPC;UPCPL:146:M256:C:6900:1101:1102=pol:0:2:411:1537:4:0
Fokus TV;UPCPL:146:M256:C:6900:1301:1302=pol,1303=aux:1306:2:413:1537:4:0
TVN HD;UPCPL:210:M256:C:6900:101:102=pol;108=pol:106:2:2401:1537:24:0
TVP 1 HD;UPCPL:210:M256:C:6900:301:302=pol,303=aux;308=pol:306:2:2403:1537:24:0
TVP 2 HD;UPCPL:210:M256:C:6900:501:502=pol,503=aux;508=pol:506:2:2405:1537:24:0

However the quality is really bad. I've attached logs from debug.
Once again I'm stuck. Can it be because of the QAM256?

lord slash, I'm afraid rpi is not able to play H265. Even my N3150 has problems with this codec.

Snr 37.5 dB for 256qam. Good or bad, i don't know :-)

Anyway, I have some problems with video quality. I can say there is no video Screenshots attached. TVHeadend take ~30% single core CPU. Any ideas? What can be the cause? Problems with decoding?