Program_number is a 16-bit field. It specifies the program to which the program_map_PID is
applicable. When set to 0x0000, then the following PID reference shall be the network PID. For all other cases the value
of this field is user defined. This field shall not take any single value more than once within one version of the Program
Association Table.
That is good!This patch now works great!
The PMT PID in the DB is always updated no matter what you do - you can't stop that from happening. The debug option makes the TV Server look for the correct PMT PID in the stream (technically: the PAT) and ignore the PMT PID in the DB. If you turn the debug option off then TV Server will use the PMT PID in the DB. Both methods should be the same speed, however if you turn the debug option off then tuning could fail or take a long time if the PMT PID for the channel changes. It is up to you whether you turn the debug option off, but I'd recommend that you leave it on...One thing to make clear for me - is abot debugoption "Always lookup PAT". Is am right, that if this option is checked, tv server would never right down a new pmt in sql server table? If this option is NOT checked, that a new PMT will be fixed in table and next time tv service want to show channel, it can get this pmt from table and don't look up for that in stream?
That is not my decision to make.Would that patches be integrated in new version of MP?
I really don't know anything about AlexPlas's patch. Do you need the combined patch because you have more than one NIC?It fails if I manually select my dedicated NIC attached to the port my ISP is streaming the TV and radios channel...
I don't know very much about DVB-IP, but I'm suspicious of the format of your M3U file:So, it's better than before, still not perfect. I have about 65 channels, and I manually entered tuning detail for about 10 of them. When I scan, it goes till the last I entered then stop saying scanis finished.
Sadly, I tried to create manually the channels without tuning details (quite long to do and boring - add channel, then add tuning entering each time 1, 8442, 1, 2001, 67, IP) hoping it would then recognize them and add the tuning details for me, but it didn't work.
I guess I must have the defined channels mapped to the DVBIP card, meaning they must have the tuning details (at least one) before doing a scan.
#EXTINF:10,BFM
udp://@225.1.1.152:1111
#EXTINF:-1,BFM
udp://@225.1.2.11:1111