Bug report – DVBViewer Pro Beta 7.3.1.9 (CI assignment issue with OctopusNet SAT>IP)

[angelsevov]

Hi hackbart,

 

I would like to report a bug in DVBViewer Pro Beta version 7.3.1.9.

In version 7.3.1.0, when using OctopusNet SAT>IP, you can assign a CI port/number and DVBViewer successfully plays the decoded stream. This works perfectly, and the CI assignment remains available and adjustable at any time.

 

However, in Beta version 7.3.1.9, the CI assignment menu only appears once. It shows a dropdown list where you can select the CI number, but after clicking OK and then Apply, the selection is not saved, and the CI assignment menu disappears. The stream also fails to play (for encrypted channels).

If you go back to the Settings later, the CI assignment option is no longer available. Rescanning for SAT>IP devices makes the menu reappear, but repeating the same steps (selecting CI number, clicking OK, then Apply) breaks it again.

 

Additionally, if you upgrade from 7.3.1.0 to 7.3.1.9 without touching the CI assignment menu, the decoded stream continues to work. But once you open Options → Hardware and access the CI assignment under the Settings button, the functionality breaks again after clicking OK and Apply — the stream stops and no longer decodes the channel.

 

Additional note:
If you start the application and the decoded stream plays (without changing the CI assignment after the update), a warning appears saying:

“TCP data transport not supported by the server.” (according to change log -DVBViewer automatically falls back to UDP data transport- but it was already on UDP)

When you go into the settings to change the CI assignment and break the functionality — there are two radio buttons appear to switch between UDP and TCP. Changing first to TCP and then back to UDP makes the warning disappear. I noticed in the changelog that you’ve added some new and exciting features related to TCP and UDP, so I just wanted to let you know about this bug/behavior.

 

First screenshot is from 7.3.1.0 and the second one is from 7.3.1.9

 

Edited 9 hours ago by angelsevov

[Griga]

This is a known bug. But it's easy to work around it. Before you change something in the setings after opening them, always click the server in the servers list at the bottom first.

 

Sorry for the inconvenience. Will be fixed in the next release.