![]() Since Madmapper does support MTC or a timecode based sync. I basically use Qlab to hit play and then count seconds/minutes, until it executes the next action. I wish there was an easier way, but without a cross-application sync function, madmapper won't sync across timecode. Note: I did get madmapper to sync to an MTC clock, but it ran 1/4 the speed it should. If I had the time I could route the MTC through Osculator, correct the values, and then plug it back into madmapper, but stacking all these applications is not ideal.ĭespite Veźer's functionality and OSC query, I found it easy enough to copy the OSC address in madmapper and paste it directly into Qlab. Without a time base sync between madmapper and Veźer, Qlab was quicker to set up and troubleshoot (IMO). I tried Vezer a while back, but settled on Ableton Live Suite for controlling madmapper - Vezer is a bit limited in the audio department and I make heavy use of Ableton's warping to align beats with the timeline grid in there. ![]() It certainly isn't the cheapest solution, but Max-for-Live (M4L) makes it easily to build patches that send OSC commands (or MIDI nodes) to Madmapper. There are a few publicly available patches out there, including ones specifically for Madmapper, but the possibilities are really endless with M4L inside of Ableton Live - and you can build it visually, without having to write code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |