Rob Rob
- Login: robo989
- Email: robo989@hotmail.com
- Registered on: 2014-04-11
- Last sign in: 2019-02-27
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 0 | 0 |
Activity
2019-02-27
- Hi there,
I have an otherwise fully working setup but cannot upgrade from 4.2.6 to a newer version. I was happily ...
2015-06-17
-
03:39 Tvheadend General: RE: Sky Auto Channel Numbering
- Known issue, just tag them yourself. The bulk of the job is done at this point anyway...sorry but that's just way it ...
2015-06-05
-
13:20 Tvheadend Bug #2913: Scanning incorrect frequencies
- > By the way - you can edit the mux parameters and change frequency (set last three values to zero). The frequency ch...
-
13:16 Tvheadend Bug #2913: Scanning incorrect frequencies
- Jaroslav Kysela wrote:
> I have nothing against the "work-arounds" in the frontend settings (hardware input tree), b...
2015-06-04
-
11:19 Tvheadend Bug #2913: Scanning incorrect frequencies
- B C wrote:
> they are correct, take a look at kingofsat.net
> further more a tuner is able to lock a 27mhz transpon...
2015-06-03
-
22:25 Tvheadend Bug #2913: Scanning incorrect frequencies
- Jaroslav Kysela wrote:
> Frequencies are read from tables broadcasted in the MPEG-TS feeds. They contain also sub-MH...
2015-06-02
-
17:26 Tvheadend Bug #2894: Records view is displayed as flatten list in Kodi
- Jaroslav Kysela wrote:
> Applied in changeset commit:tvheadend|c90fb4180b6f06bf6d5bf28b3697e726dc9a6a92.
Thanks s...
2015-06-01
-
15:16 Tvheadend Bug #2894: Records view is displayed as flatten list in Kodi
- Jaroslav Kysela wrote:
> The wrong pathname for old configs should be fixed in v4.1-126-g145ca52 . Thanks.
Thanks... -
14:39 Tvheadend Bug #2894: Records view is displayed as flatten list in Kodi
- Rob Rob wrote:
> Also seeing this in 4.1-117.
> This is not a plugin issue - plugin has remained a constant before ... -
14:30 Tvheadend Bug #2894: Records view is displayed as flatten list in Kodi
- Also seeing this in 4.1-117.
This is not a plugin issue - plugin has remained a constant before and after these bugs...
Also available in: Atom