djsemuta wrote:Hi all. I am new to Modul8, but the short story is that I am doing essentially the same thing as the OP.
I am triggering M8 with Ableton on another computer via a hardware midi interface.
I believe that in my case at least, the latency comes from the time required to load a clip when triggering from the 4X4 media library.
That is probably true. Be sure to have your media in the right compression, Photo jpeg at 75% quality is suggested. That is the codec that is the fastest for the computer to unpack in RAM while still looking descent. The shorter your clips are the better. And don't make your clips in unnecessarily large sizes (width/height). Having a lot of RAM installed on your computer will help you. Have your media loaded and unpacked in RAM - if you mark a clip in the 4x4 media library and press the info button (upper left corner of the same window) you will find the settings for this.
If this is the case, must I then have every clip already loaded into a slot on the left and playing in order to get it to trigger in timely fashion?
This is another option. Then your media is already loaded in to a layer. I think theoretically you should be able to turn all layers off and then turn them on with a continuous MIDI signal that turns them on. When you do your midi mapping, be sure to have "Position" or "Layerset + Position" set, you'll find these buttons on top of the Modul8 main window when you go to MIDI mapping mode. And remember - it's the layer on/off button you'd want to map, it's the first little square to the left in the layer. You might get different result if you turn the opacity up and down, you can try that too.
If so, what sort of organization strategy would folks here recommend for a video show that essentially goes back and forth between a static image on the screen videos triggered in time with each song?
I imagined a scenario more like triggering session clips in Ableton, where the video sits there waiting for a play command, but things don't appear to work that way...

That's a third method and I think this is how John finally did. He edited all videos together and jumped to a specific place in the video time line for each song. I made a simple cue module for him with 12 cues. But I'm not sure that this was the ultimate solution either since there was a little delay every time M8 did that jump in the timeline. It could have been depending on the codec of the video I was testing with, I'm not sure. It wasn't optimized for Modul8.
This would NOT be the way for you if you're mixing video and stills.
Also, if I need to start a clip at some point in time >0, what's the best way to do that?
Nudge any of the timeline knobs (either side of the play/reverse button) or make a custom module that uses direct_media_timePositionSec. I'm not sure the latter is the perfect suggestion to a new user, but you can read all about making modules in the manual.
I'd like to have M8 running in a fashion that requires as little interaction as possible, and delivers the most consistent behavior possible.
I and many other people have done this. In my case, I made a set that was traveling with two musicians. They only needed to boot up the computer, launch my Module8 set and connect the computer to the screen. It ran super smooth. However - it took a lot of time for me to set it up that way, especially since the visuals I created was much more dynamic than only playing videos and stills.
So prepare to put in a lot of work in creating the set if you want it to be simple during the show. My set did't need to be touched at all during the show, but consider having a midi device for changing media sets or something.
For what you mention, videos and stills, I think loading media in to one layer could work and preloading in to different layers and turn the layers on/off would work too but you'd have to figure out how to do when you've used the 10 first layers and want to change media sets.
Thanks for any advice!
S