16 replies to this topic

[jeanclaude]

I seem to have a problem when I enter the "manual channel scan" interface :

when on the "satellite" datafield, the 'cursor-right' isn't working. Only 'cursor-left' is working.

this is very annoying as when I have to go from '19.2E Astra 1" to "23.5 Astra 3" I have to navigate through the whole Clarck belt ! (with my steerable dish)

tried with the remote and with the web-interface, neither is working.

 

'cursor-right' is working correctly on the other input fields, viz 'search mode', 'polarisation', 'FEC', etc.......

problem is present on both my DB8000 dreamboxes.

 

[Dimitrij]

Use button 'open movie list'.

[jeanclaude]

indeed - pressing the [PVR] button opens a list of available satellites which I can select.

but where's the logic in keeping the <left-arrow> active, and disabling the <right-arrow> button ?

[Dimitrij]

Open satellites.xml

show entry position=

Maybe '19.2E Astra 1"position  between same as "23.5 Astra 3"

[littlesat]

Both left/right button should work.... At least here it does...

Edited by littlesat, 26 April 2017 - 13:48.

[jeanclaude]

my satellites.xml is coming from Henk, so I suppose it's a valid one - besides, pressing the [PVR] button generates a list of all satellites of the clarck belt (for my steerable disk, for my fixed disk I get a list of available satellites only so this looks OK to me).

even when I change the satellite in something else using the [PVR] button, and coming back to the manual scan interface, the <right-arrow> still isn't working, whereas the <left-arrow> is. And only for this datafield, on the other datafields left & right arrows are working as expected - strange ......... image was updated last weekend so should be up-to-date.

OK, not a big problem any more, I can use the [PVR] button to select the correct satellite, and as littlesat does not have the same problem it does not seem to be a general error.

[Erik Slagter]

This is a known bug, not a feature, I know it from the tuner selection for loop through, but apparently it comes up at different fields as well. I've tried to find it, but never found the cause. This is work for a python expert. The buttons ARE assigned in python, it just doesn't work sometimes.

[Dimitrij]

jeanclaude

please show your satellites.xml

[littlesat]

I never experienced it and I never found how to trigger is

[jeanclaude]

Dimitrij,

here goes :  satellites.xml   630.35KB   3 downloads

[Huevos]

I never experienced it and I never found how to trigger is

Bug is very real. I've looked and never managed to track it down either.

[littlesat]

In satfinder I can imagine as there transponders are zapped

[Rob van der Does]

I never experienced it .....

Yes, you did. You did confirm this bug in the past.

Problem is: it's a conditional bug, and nobody has any idea what the condition is.

[jeanclaude]

anything I can do to help ? it's repetitive here, and it's working above and below the input field, so if I can produce some kind of trace that might tell you what's happening .......

[Rob van der Does]

If it's happening now, that doesn't mean it will be happening tomorrow or the day after.

Most of the time this works fine, but sometimes the bug kicks in (and leaves again without a trace).

[Erik Slagter]

@Littlesat, try the loop through option in tuner setup. Mostly you can go left (tuner down) but not right (tuner up) which is kind of a pain when you have two FBC tuners.

[littlesat]

I cannot look or verify now but I can try... when you describe it like that I'm afraid we need to remove some ghost code... how is that list build there?