Handling Transport_stream_id conflicts

[Snakehand]

I recently bought a DM 500C, but my cable provider have, in their infinite wisdom, assigned the same transport stream id ( 0 ) to two different streams. This causes a bit of a confusion, as the streams will overwrite each other when I scan for channels.

The root of the problem is that Enigma, quite reasonably I must add, uses the transport_stream_id as a unique key in the transponder list.

Is there any known way to hack around this, or do I have to dive into the code and 'fix' it myself, which I can and will - with resulting code that will probably not be fit for the CVS repository

( Please answer in German if that is more convenient )