Multiplexed V1_1.m4s+A1_1.m4s manifest examples

[Murmur]

https://github.com/Dash-Industry-Forum/dash-live-source-simulator/wiki

Multiplexed Content
For eMBMS, better robustness can be achieved by multiplexing audio and video segments. This can be done automatically by the server. It happens if the path to a segment has two underscores in the next to last path component, like .../V1__A1/123.m4s. In this case the two segments V1/123.m4s and V2/123.m4s are fetched and multiplexed. The corresponding thing happens for the init segments. For this to work, the MPD must be manually changed to have a multiplexed representation.

I guess this paragraph has a typo it should say V1/123.m4s and A1/123.m4s segment payloads(video+audio) are merged?

Do you have an example for the live stream how this manifest should be edited. If one segment file contains data for both video+audio payload how is AdaptationSet/Representation elements be written?

normal live: http://livesim.dashif.org/livesim/testpic_2s/Manifest.mpd