Jaroslav Kysela

  • Email:
  • Registered on: 2012-12-12
  • Last connection: 2017-07-08

Projects

Activity

Reported issues: 17

2017-07-09

12:47 Tvheadend Bug #4468: Tvheadend Sat>IP Server is not recognized by Eyetv
Matej Munih wrote:
> From my understanding, the problem is that both Eyetv and Geniatech Sat>ip are BACKENDS and doe...
12:45 Tvheadend Bug #4468: Tvheadend Sat>IP Server is not recognized by Eyetv
OK, do you have correct SAT>IP server config? For standard satellite clients, there should be announced only DVB-S2 (...

2017-07-08

17:26 Tvheadend Bug #4468: Tvheadend Sat>IP Server is not recognized by Eyetv
Don't ignore warnings from tvh:...

2017-07-07

22:24 Tvheadend Bug #4478: Stream profiles disabled but webui or older tvh clients are still able to use it
The profile should be changed to default when the name is not known or user has no permissions to it. Just check the ...
16:27 Tvheadend Bug #4474 (Accepted): SAT>IP with IPTV inputs never "locks signal"
OK, a next patch which should keep the playing state when a new SETUP is received after PLAY for the new session. Als...
16:26 Tvheadend Bug #4474 (Fixed): SAT>IP with IPTV inputs never "locks signal"
Applied in changeset commit:tvheadend|a9dffb7e96d5d0269840e40575e69ec996351ec1.
16:26 Tvheadend Revision a9dffb7e (tvheadend): satip server: fix the PLAY/SETUP state machine, filter stream in D...
16:04 Tvheadend Bug #4474: SAT>IP with IPTV inputs never "locks signal"
Looking again to spec, diagram in 3.5.9 paragraph (RTSP Method Summary / RTSP State machine). It appears that if PLAY...
09:51 Tvheadend Bug #4474: SAT>IP with IPTV inputs never "locks signal"
Do you know (or could you test), if it is enough to send 'empty' RTP packets until PLAY is received from the client? ...

2017-07-06

00:21 Tvheadend Bug #4468: Tvheadend Sat>IP Server is not recognized by Eyetv
Do you have SAT>IP RTSP port configured to 554 in tvheadend? Most of clients work only with this port.

Also available in: Atom