Just so you know, it thinks that 127W is 12.7W

[ilikenwf]

Describe the bug

There's a parse issue, when I connect and download everything from my e2 box, it sees my 127W channels and marks them as belonging to 12.7W.

Steps to reproduce

...

Expected behavior

No response

Software version

1.4

Download medium

GitHub Releases page

Platform running

I don't know

Architecture running

I don't know

Other (please specify)

No response

Additional context

No response

Log

No response

Screenshot

No response

[ctlcltd]

Sorry I can not find an authentic channel list for 127W on the internet, if you can upload an unedited list for 127W, taken from the decoder, it would help.

I did some testing, the value read from satellites.xml is correct, “127.0W C-band Galaxy 37/Horizons 4” shows 127.1W as expected. Also in edit is correct.

As far as I know, the orbital position value could be multiplied with West. This situation is not currently considered. Above 180 deg should be = 3600 - position, but would not be 12.7. Still to be investigated.

Thanks

[ilikenwf]

I'm using the satellites.xml from https://sat-forum.net/viewtopic.php?t=131&sid=a06764ad9f180a91970f14ba9b6046a2&start=140 because it's so fresh most of the time, scraped from lyngsat.

[ilikenwf]

...from what I can tell, other than maybe 5-7 channels extra, it's accurate.

[ctlcltd]

Thanks for the suggestion!
I would need a services list directly from a decoder, it would be more accurate.

[ilikenwf]

My e2 box should be able to output that for you to xml, right?

[ctlcltd]

Yes, saving from the software or taking the files directly from the decoder and zipping them.
The services file is "lamedb", or "lamedb5", or "services" (older Enigma), or "services.xml" (Neutrino).
Many decoders also export from a USB stick.

[ilikenwf]

lamedb.zip

Forgot I already had a copy from playing with the editor, though this should only have the adult lock applied to the two xxx channels...I don't want those personally.

[ctlcltd]

Thank you so much, I solved the mistake.
I limited the value to 4 digits, thus it does not parse the minus sign with negative 4 digit values.
The fix will take effect on the next release.

[ilikenwf]

Ah, very cool! Thanks for the great editor.