Reply to thread

Thanks for the answer mm!

But I think the problem is something different, please correct me if I should be wrong.

To save bandwidth we only request the pids for one channel, but to get EPG we had to add the pids 16,17 and 18.

Now if we have a URL like:

zdf_neo

rtsp://192.168.178.44/?freq=394&msys=dvbc&sr=6900&mtype=256qam&pids=0,650,660,670,671,672,675,680,16,17,18

TvService finds around 10 new channels (because of the PMT) and adds these to the DB and all get the same url which can't work, because we get only the video and audio pids for zdf_neo.

Maybe another example:

scanning this url (zdf_neo) with channel movementdetection activated:

rtsp://192.168.178.44/?freq=394&msys=dvbc&sr=6900&mtype=256qam&pids=0,650,660,670,671,672,675,680,16,17,18

gives me:

zdf_neo

zdf

zdfInfo

All wil have the same url: rtsp://192.168.178.44/?freq=394&msys=dvbc&sr=6900&mtype=256qam&pids=0,650,660,670,671,672,675,680,16,17,18

This can't work...

Now TvService scans zdf_info and updates all channels with this url:

URL: rtsp://192.168.178.44/?freq=394&msys=dvbc&sr=6900&mtype=256qam&pids=0,600,610,620,621,622,625,630,16,17,18

and if you don't activate the channel movement detection it updates all the channels with the same url to the same name (because it only compares the url).

I also added an option to disable the channel update function, so it still adds all chanles, but doesn't update the channels. The result is that only the first scanned channel of a transponder is working (what isn't that surprising, but I wanted to try it  )

I think this could be a solution! So we would have a much higher bandwidth (~50Mbit/s) usage, but for a temporary solution this shouldn't be a problem

So we would have one url per transponder like it is in DVB-C.

The advantage would be much faster channel scans (compared to 3h).

I will try it this evening and report back here