Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 782472" data-attributes="member: 82144">Hi velisObviously we listened to the feedback that we received from you and others when 1.2.0b was released. In MP 1.2.0rc the default channel identification for DVB-IP channels is the URL. You can enable channel movement detection to use ONID + SID, but I don't imagine many people will actually do that. There is always a trade-off between flexibility, code complexity and usability. We have decided not to do this as although it is the ultimate in flexibility, it makes TV Server configuration more complex to understand. Instead, we intend to follow the DVB standards as closely as possible. I freely acknowledge that there are aspects of DVB-IP that we have not implemented at all - we intend to improve support in the next version of TV Server. However, we are not going to bend over backwards to accommodate badly behaving providers.As I've already said, we intend to improve support for DVB-IP. I will keep that in mind when we go to deal with that code. Having said that, you make the assumption - perhaps rightly, but technically not guaranteed - that there is only one channel in each DVB-IP stream. TV Server supported DVB-S, T and C standards first where that is almost never the case. I'm sure reusing the existing code made it much easier to add support originally...As I've said, we listened to your feedback and made the URL the default identifier for 1.2.0rc.mm</blockquote>

[QUOTE="mm1352000, post: 782472, member: 82144"] Hi velis Obviously we listened to the feedback that we received from you and others when 1.2.0b was released. In MP 1.2.0rc the default channel identification for DVB-IP channels is the URL. You can enable channel movement detection to use ONID + SID, but I don't imagine many people will actually do that. There is always a trade-off between flexibility, code complexity and usability. We have decided not to do this as although it is the ultimate in flexibility, it makes TV Server configuration more complex to understand. Instead, we intend to follow the DVB standards as closely as possible. I freely acknowledge that there are aspects of DVB-IP that we have not implemented at all - we intend to improve support in the next version of TV Server. However, we are not going to bend over backwards to accommodate badly behaving providers. As I've already said, we intend to improve support for DVB-IP. I will keep that in mind when we go to deal with that code. Having said that, you make the assumption - perhaps rightly, but technically not guaranteed - that there is only one channel in each DVB-IP stream. TV Server supported DVB-S, T and C standards first where that is almost never the case. I'm sure reusing the existing code made it much easier to add support originally... As I've said, we listened to your feedback and made the URL the default identifier for 1.2.0rc. mm [/QUOTE]

Verification