Suggestion: SRC parameters for mappings

[lars18th]

Hi @Barracuda09 ,

Instead of using the parameter "fe=", I prefer to use only the "src=" in the SAT>IP requests. Then I want to assign one source position to virtual frontend "TS Reader" and another different to the "Streamer". So I suggest to add to the configuration a "LNB configuration" for such frontends indicating a default SRC. Then, for example, if you assign SRC=1,2 to physical fe0, SRC=3 to "TS Reader" and SRC=4 to "Streamer", then you don't need to indicate the "fe=" in the request.

You agree?

Note: Another comment. Please, add at some point (documentation or UI) that "TS Reader" is [Virtual FE with FILE|PIPE input] and "Streamer" is [Virtual FE with NETWORK input]. At time is quite confusing to see the difference. 😉

[lars18th]

Hi @Barracuda09 ,

After re-think on this, the request doesn't have sense... directly! That's because inside the mapping.m3u you can define what you need.

So, I feel that what has sense is to have the option for filtering using the SRC parameter like this example:

#EXTINF:-1 satip-freq="200" satip-src="2", Translation to: File uri="/usr/satpi/test.ts"
rtsp://%1/?msys=file&uri="%2Fusr%2Fsatpi%2Ftest.ts"

Please, can you consider to support this?
Thank you.

[lars18th]

Hi @Barracuda09 ,

You'll address this enhancement soon? I really want to map different sources to different mappings.

Thank you!

[lars18th]

I close this as it's implemented.

Thank you @Barracuda09 ! 👍