12/28/2022 0 Comments Ableton modul8 sync![]() ![]() I then just had a midi cc message send from the device that I wanted to bring Midi into mainstage trigger the playback button on mainstage. So what I did was instead of syncing the tempo (might also work if you synced the tempo) I just set a fixed tempo in the concert or patch. The problem I was facing was that mainstage didn’t recognize the beat one. I think I may have found a workaround that I am currently testing. ![]() Again: you could trigger by hand, just like playing in-sync. The exceptions where this fails are certain clock based things, which can be Loopback or Playback, because they don't know the intention of the external device. Which means you have to follow the external device. If an external device provides the tempo, it's like playing with other musicians: somebody leads and the rest follows. Even if MainStage would support that, the external device would have to support that, too - which is not very probable. In most cases that is perfectly fine, but beat clock contains no information about down- or up-beats, which can be a problem in some cases. MainStage as a strict live application doesn't have a timeline, so there is no full-sync. #Ableton modul8 sync fullThis is supported since MainStage 1.0.įor full synching you actually need a timeline with bars and beats and being able to actually re-position if necessary. By itself you can extract the tempo out of it (by measuring the timing between several incoming beat clocks), but that's it. But what's the action object called "Midi Beat clock" for if it doesn't sync to it?īeat clock - as the name implies - is just a MIDI clock. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |