Hi all,
i'm the other half of the project mentioned by Ropski here.
The goal of the project is an audio-visual liveset/performance where the interaction between the audio and the video goes beyond the usual beat-synced inverts and such. I have a liveset with a bunch of sequencers synths, and drumcomputers, all controlled by midi. We have the midi-output of the complete set hooked to the midi in on Ropski's BCR2000 and which then goes into modul8.
For the interaction i've scripted some modules, one which triggers clips on a set layer depending on the incoming note on the set channel, with the option of making the in-point and the opacity of the clip velocity dependent, and another which can affect multiple layers, where the clips playing on the layers can be set to a defined playing speed and/or zoom-level when a note is being played on one of the set channels, and reset to the earlier settings when the note is released.
I haven't uploaded these modules yet as they still have a few glitches at the moment, and i've decided to combine them both in a single module together with some other stuff i've been trying, like an advanced midi patcher.
But I have a few scripting questions.
The first is regarding the issue in the topic I linked to above, not being able to record the sound input. The trigger module I scripted is mainly used for percussive sounds, which are generally pretty short. This means there's a lot of fast clip-switching going on, in sync to the sound, so it's pretty important to have some means of syncing a logical record to the recorded audio (and midi, in our case). For optimal modul8 performance we'd prefer not to have another program like Audacity running, so as a solution I tried scripting a module that reset the logical record time to 0.0 and started recording when a real-time start message is recieved, but although almost every other control in the main modul8 UI is accessible by a keyword the record-button apparently is not.. Why is this, and any chance of this being implemented in the future?
Next i'd like to know if there's any way of addressing the midi map (read-only) from a script, as i'd like to have some way to ensure that the midi-channels set in my modules don't overlap with those used in the main modul8 midi map.
Then I have a question about the modulesDict keyword, which i've succesfully used to prevent the same values being selected in different modules: is this dictionary and the values set in it stored when a project is saved?
Finally i'd like to ask if there's any possibility at all that the module editor could be ported to Windows... I was fortunate that Ropski was kind enough to park his (almost) maxed-out Mac Pro at my place for a couple of weeks, but inevitably he needed it himself again, and I don't have a Mac myself..