Tvheadend

Jaroslav could this be again related with Bug #3821???

tried on early morning to set the constellation to qam/64 and:

2018-11-10 08:14:23.091 mpegts: 714MHz in teste - tuning on SAT>IP DVB-C Tuner #10 (192.168.2.216@TCP)
2018-11-10 08:14:23.091 epggrab: 714MHz in teste - registering mux for OTA EPG
2018-11-10 08:14:23.091 subscription: 0214: "scan" subscribing to mux "714MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #10 (192.168.2.216@TCP)", network: "teste", service: "Raw PID Subscription"
2018-11-10 08:14:23.095 satip: SAT>IP DVB-C Tuner #10 (192.168.2.216@TCP) - RTSP SETUP error -5 (Input/output error) [6-461]
2018-11-10 08:14:23.142 satip: SAT>IP DVB-C Tuner #10 (192.168.2.216@TCP) - RTSP SETUP error -5 (Input/output error) [6-461]
2018-11-10 08:14:28.091 mpegts: 714MHz in teste - scan no data, failed
2018-11-10 08:14:28.091 subscription: 0214: "scan" unsubscribing

Finally had some results...

The problem is not related to constellation on auto.

There's 2 different problems with this device:

1. It seens to not support "RTP/AVP/TCP transport supported" thats why i got "RTSP/1.0 461 Unsupported Transport". It's strange a expensive device like this only support UDP.

2. The device is badly announced or the way it's announced it's not well understood by tvheadend. Let's see, the dedice show up as DVBT2-8,DVBC2-8 to make it work i had to change Tuner configuration from Auto to DVBC-8 and of course UDP mode.

With that device works... even i think not as good as expected.

Jaroslav, there's anything you can do on TVH side or both things are only DD related?

Thanks

Ricardo Rocha wrote:

1. It seens to not support "RTP/AVP/TCP transport supported" [...]

Known behaviour of all DD devices. If I remember correctly, when asked by users, DD answered something like "implementation of RTP not possible because of hardware limitations". (no, this answer doesn't make sense at all). Because of this, the "location" of your dd device within the network could be critical.

Tim Bremer wrote:

Ricardo Rocha wrote:

1. It seens to not support "RTP/AVP/TCP transport supported" [...]

Known behaviour of all DD devices. If I remember correctly, when asked by users, DD answered something like "implementation of RTP not possible because of hardware limitations". (no, this answer doesn't make sense at all). Because of this, the "location" of your dd device within the network could be critical.

if they confirm that's true i guess the equipment finish to pick return ticket!

Jaroslav Kysela wrote:

The hw is based on a slow ARM board and their FPGA with the networking stack and MPEG-TS data handling. I also asked to add TCP data support (I own one 4xDVB-T2 device), but they replied that's not possible (probably limited FPGA power). It would be probably better to look for Enigma2 boxes with FBC tuners and install minisatip to them, altough the FBC support might not be fully covered in minisatip (check issues).

Totally understood

what about the badly announce is it also from their side (just curiosity i am returning it because of tcp)

I did test already some of the FBC:

VU+ (have some driver issues)
Mut@ant have a very good device (you should explore this device if you have the time) cheap (less than 100eur), 100mbits, 3 frontends. However i think there's still some pid filtering issues on minisatip i believe and maybe it needs some network code improve also. I can exaust the 100mbits easily getting streams from enigma openwebif, but if i use minisatip it starts with CC errors and get instable just after 3 4 streams.
Gigablue (8 x dvb-c) is the next on the list