I think you want what Old Mobius used to call "Bounce".
You could take the output from several tracks, merge them together and leave the result in an empty track. Then the bounce track would loop, and the source tracks would be Muted so you would only hear the bounce track.
There is still some support for that, but I haven't tested it in Mobius 3 and it may not work right.
You could do something similar by using the plugin host to route audio from Mobius output ports back to Mobius input ports. Which I think is what that video is demonstrating.
Configure each of the Mobius tracks you want to bounce to send to a different output port. For example, let's use tracks 1-3 sending to output ports 1-3. Now pick a track to be the bounce track and have that receive on a special input port, say port 4.
In the host, arrange to have Mobius output ports 1-3 merged and sent back into Mobius input port 4. Every host does this differently. It easy in modular hosts like GigPerformer or Bidule where you draw lines between plugin ports to make connections. The same thing is possible more traditional hosts like Ableton or Reaper, but I don't know the details of how to accomplish that.
Mobius is unaware that any of this is happening, track 8 is receiving audio that it will record and loop but it doesn't
know that it is a merger of what it is playing on tracks 1-3.
So while you can get the content from several mobius tracks merged into a bounce track, there are several problems that have to be addressed.
The first is monitoring. When you're recording Mobius tracks 1-3, you need to have the output routed to a port that you can hear in your monitors. This will be different than the bounce input port that track 8 using. So in the host you need to be doing one of two things:
- Split the output of Mobius ports 1-3 into two paths, one that goes to your monitor speakers, and one that loops back into Mobius input 4.
- Change the port wiring in the host between two different configurations, one for the initial recording, and one for the bounce. Maybe using some kind of "macro" facility in the host to do this quickly without a lot of UI interaction.
The second problem is Mobius track muting. Once you have recorded the bounce in track 8, it will start playing. But the source tracks 1-3 are still also playing. This will immediately double the volume of what was in tracks 1-3 and due to latency the bounce track will be slightly out of phase resulting in an unpleasant metalic sound. If you're doing this in the studio that may not matter, you can just manually mute Mobius tracks 1-3. But if you're doing this while performing live, you would want tracks 1-3 to be automatically muted the instant the bounce track finishes recording. You would need to use Mobius scripts for that.
The third problem is latency. Due to the way Mobius and the host send audio blocks to each other, the audio that the bounce track 8 is receiving from the host is usually delayed by one audio block. This means it will be a few milliseconds late and be slightly out of sync with the other Mobius tracks. Depending on what the other tracks are doing this may or may not be noticeable.
For those reasons, the ideal solution is to have the Bounce be accomplished inside Mobius. This has been high on the list for a long time, the RC-505 has a form of bounce so it is something people expect. But it is one of the more complicated things to get right so it may be awhile before it ia ready.
The addition of MIDI tracks raises some interesting issues, can you bounce MIDI tracks together? Can you bounce an audio track and a midi track together?
What about having Mobius playing a MIDI track, and at the same time capturing the output from the synth that is producing the sounds of that MIDI track?
This is also related to a concept many hardware beat boxes call "resampling". Take whatever is being produced by a device between two points in time, including any real-time performance controls that are being used, capture that, and store that somewhere as a new loop.