Open Barracuda09 opened 1 year ago
Please use discussion #170 for ideas an possible sollutions
Hi @Barracuda09 ,
From my point of view this could be interesting. However, quite complex. I prefer before to implement these changes in the translation:
satip://...?src=8&...
then only in this case (SRC==8) do the translation. Usefull to restrict the translation to one specific satellite position only. It could be done adding satip-src=...
in the EXTINF
part.satip-mtype=...
.satip-filter-exec=my_binary%20param
. In this case, the read is done with the translated input, but then injected to this external tool (with a PIPE) to filter it reading from the PIPE. Some tools like the TSDuck could be used then to generate the PSI metadata that you want to create the scanning tables.I feel this could be more easy to implement. Do you think so?
Hi @lars18th
satip-src="xx"
is already implemented with #94satip-mtype="DVB-T"
I have to think about the use of it.satip-filter-exec=my_binary%20param
I don't see this as usefull for me, as I see the PSI metadata generation as a study object for me (and maybe with help, if there is any).Hi @Barracuda09 ,
Regards.
Hi @Barracuda09 ,
Regarding you new changes (WIP) with the PSI metadata, some comments:
a=fmtp:33 ver=1.0;src=1;tuner=4,240,1,15,11953.5000,h,dvbs,qpsk,off,27500,34;pids=
However, as you can see the pid list is empty. You will fix this?Regards.
The idea is to generate PSI metadata on a specific requested frequency.
The PSI will be build up by the Translation M3U file so it is possible for clients to 'search' for programs and will be redirected to the correct translation entry.
Example:
This should create PSI metadata for freq 200, 201, 202 and 203 when for example
rtsp://ip.of.my.box/?freq=10101
is requested from client during a channel search