Version: 0.8.5 (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages OS: Linux Steps to reproduce: 1) DVB-T, there are two multiplexes (frequencies) in Prague. In both of them, there are channels with the same service ID. In my case, for example these stations (from channels.dvb): TV|CT 1|257(2)|273(CZE),|289|1|1|Terrestrial|506000|0|v|23|-1|64|-1|8|8|8|0|1||| TV|Prima|161(2)|84(CZE),|37|1|1|Terrestrial|674000|0|v|23|-1|64|-1|8|8|16|0|9||| 2) EPG events from both frequencies loaded (having tuned some stations on both frequencies for some time) 3) Tune one of those stations (In my case the station "CT 1"). Results: the events for "CT 1" and "Prima" are stored both in the same way and are not distinguished by the application 1) When I open the OSD, instead of 2 "CT 1" programs, usually there is one from "CT 1" and one from "Prima" (depends on their time) 2) When I open the EPG window, there are both "CT 1" and "Prima" records marked as if they would be from "CT 1" The same is for other pairs of TV stations with the same service ID.
The Service_ID is unique on a given Transport Stream (frequency). Both are set to 1 in your case, and this is legal, since these channels are on diffrent Transport Streams. But the Transport_stream_ID MUST also be unique on a given network. In your case, they are both set to 1. This is illegal. Report this bug to your broadcaster.
still we could deal nicer with that situation
kaffeine svn fixes that.
*** Bug has been marked as fixed ***.
I confirm, that the current svn version works fine for me. Both channels have different Network ID (1 and 10). Thanks a lot.