The Stream class stream, which is named "Stream1" in the example setup, is a live stream that playback clients stream.
The source of a Stream class stream ("Stream1") can be files or other live streams. The Stream class can switch from one file to another, and to a live stream and back to a file, etc. These are in turn the source of Stream1, but the player will continue to play Stream1.
Yes, that is true. If you use an RTMP live encoder to publish a live stream named "myStream" you can play that directly, of course. But it is not what you are wanting to do when you are wrapping that live stream in a Stream class stream to use the loop-before-live example. You want to play the Stream class stream that wraps the live stream.
I considered some possible approaches to accomplishing that, but they all fall apart as I think them through.
For reference, the source for ModuleLoopUntilLive is included in the
collection download, but I don't think there is way to extend this to accomplish what you describe. You can have multiple loopUntilLiveSourceStreams as long as you have the same number of loopUntilLiveOutputStreams, and each the members of both lists have to be unique or you will probably have strange behavior, i.e. you can't share the same loopUntilLiveOutputStreams for different loopUntilLiveSourceStreams