August DVB-T210

derp derp · 2014-02-11T22:48:40+00:00

Hi. Was wondering if this was compatible with tvheadend as there's not much information from users about this device. Does anyone have one? Is it working wel...

lord slash

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

Zac Daman

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?

Anthony Thomas

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.
<<

lord slash

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?

Oliver Thomas

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?

lord slash

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

pi@raspberrypi:~/tvheadend $ vcgencmd codecenabled 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

Anthony Thomas

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.

lord slash

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

Crazy Cat

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

lord slash

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)

Piotr Brudny

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

Crazy Cat

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

lord slash

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?

Piotr Brudny

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.
<<

Crazy Cat

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

Piotr Brudny

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?

noggin

lord slash wrote:

> 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?

The AMLogic S905 platforms support HEVC/H265 decoding and have good Kodi support. Early revisions of the chip had issues that caused corruption on some DVB streams - but newer models are fine. The ODroid C2, Wetek Hub etc. all have this chip and support HEVC/H265 (and as a bonus will do so up to 2160/60p with HDMI 2.0 output) They both run LibreElec and Android versions of Kodi. I've played 2160/59.94p and 50p recordings in H265 using both devices, and have also checked 1080/50p H265/HEVC encodes I mastered myself.

They support both 8 and 10 bit HEVC/H265 encodes - but the Kodi builds only output 8 bit (so 10 bit video is truncated)

HOWEVER - the AMLogic kernel lags way, way behind the Pi (so has far poorer DVB Driver support) - so I'd keep the Pi as your backend running TV Headend (so you can run the latest DVB driver builds), and stream to the ODroid C2 or Wetek Hub or similar over Ethernet.

lord slash

Thanks for your answer. I just bought a Raspberry PI 3 because i read that with the last libreelec the H265 is supported at 720p and (probably) with some overclocking also the 1080p should be supported. I am waiting for the PI to arrive (it should be already here) and then i will start my tests and I will come back with some updates.If it won't work I will probably sell my PI2, keep the PI3 and buy an OdroidC2.

Ben Efrati

@CrazyCat,

I have Mygica PT360 and I'm using your media_tree git, I saw Antti Palosaari moved this tuner from cxusb to dvbsky. what do you think?

>Mygica PT360 PadTV tuner identifies itself as a Mygica T230. Both are practically same design, but different case and PT360 does not have remote. However, device didn't work well due to know FX2 FIFO problem.
>

>Newer dvbsky driver uses same API than old cxusb driver and it can handle FIFO issue. So move that T230/PT360 device to dvbsky driver.??

https://git.linuxtv.org/anttip/media_tree.git/commit/?h=mygica_t230_pt360&id=2c1bdd79876310c50baee7f321d10b184509ee43 https://git.linuxtv.org/anttip/media_tree.git/commit/?h=mygica_t230_pt360&id=3420b24c449023e3701c1130ed84d0a0166e56bf

Crazy Cat

I not test Antti commit, but make similar TS FIFO reset in cxusb driver
https://github.com/crazycat69/linux_media/commit/b55acc695c5979c0f5b0de8389ba22d8d364c2ea

« Previous Page Next Page »