garageCube

Hi,
I would like to know, does any of the effects and loop play time can be synced to a midi timecode?

Not yet, but probably a possibility with v2 and the new modules system, that is, if the guys implement MIDI clock reading (please? )

Akira wrote: if the guys implement MIDI clock reading (please? )

You can get the midi clock (w/ DirectEvent scripting V2 beta2)
http://www.garagecube.com/forum/viewtopic.php?t=217

Hi,
I am about to purchase one of the vid trigger apps, and very happy with Modul8 demo.
I need the app to run with ableton live, following midi triggers and controllers.
I would like to know if I will be able to sync clip lenth/speed to bars/beats etc via midi time code (loop once a bar, twice etc...).
Other is the ability to do the same with effects cycle times/lfo's.
As I understand, some will be possible with the next (free upgrade) version, I would like to know what from these is planned, and when it will be avilable.

THANKS

modulator wrote:I am about to purchase one of the vid trigger apps, and very happy with Modul8 demo.
I need the app to run with ableton live, following midi triggers and controllers.
I would like to know if I will be able to sync clip lenth/speed to bars/beats etc via midi time code (loop once a bar, twice etc...).

Well, in Modul8 you can link any midi message to any controls. We know many musicans who pilot Modul8 by sending midi messages straight from a sound application.

Now for advanced users, Modul8 V2.0 can be scripted to interpret direct midi events. So your script can interprept midi clock messages and do basically whatever you want with them.

Yves.

The other point here is what I've been talking about with detecting clip length and changing the speed to match with midi clock or BPM via something like BACF and being able to change with switches to be multpliers.
Can we expect a "clip length" keyword to be added to the script keywords in the near future?

Please consider this!

boris wrote:You can get the midi clock (w/ DirectEvent scripting V2 beta2)
http://www.garagecube.com/forum/viewtopic.php?t=217

Well what do you know. I didn;'imply from your reply that you said MIDI clock was ALREADY there, since the screenshot didn't seem to show it (am I being blind? what o=would be the keyword?)

chromafresh wrote:Can we expect a "clip length" keyword to be added to the script keywords in the near future?

I will add clip entry/exit point keywords for the final release of V2.0. Maybe not for the very next beta, but it will there for the final release.

Yves.

Akira wrote:I didn;'imply from your reply that you said MIDI clock was ALREADY there, since the screenshot didn't seem to show it

Well, in the screen shots there was not midi clock messages. Now if you configure your device to send midi clock messages you should receive them in the DirectEvent script. If you do not receive the midi clock messages, let me know.

I added a script to the online library that prints all the direct event messages (it is called PrintDirectEvent) to the console. You can use it to see what midi messages you receive.

Yves.

sounds good... But, I would think that the start and end points would only be useful for "editing" clips to a beat ala the scratch knobs.
Or does this mean that one could do what I'm talking about? derive the total clip length, and conform it to a speed determined by midi or BACF? I'm not talking about starting and stopping playback with a rhythm but actually conforming the total length of the clip to a specified rhythm. Sorry to keep asking... it isn't immediately obvious to me that this would be the case.

well here is a dream then. It would be ultra awesome if you could tag all of your media with BPM. Then, either using tap or MIDI, adjust the clip speed to conform to the live tempo.

chromafresh wrote:I'm not talking about starting and stopping playback with a rhythm but actually conforming the total length of the clip to a specified rhythm. Sorry to keep asking... it isn't immediately obvious to me that this would be the case.

Well, this can be achieved by adapting the movie rate. A keyword that returns the time length of the movie should be added. Once you know the time length of the layer you can easily compute the required rate.

So if your rhythm requires the movie to be played in one second and the loop duration is ten seconds, the rate should be set to ten :

newrate = movieTimeLength / rhythmTimeLength

For many codecs, it's better to change the rate than changing the movie position all the time.

We'll make many scripting tutorials / examples once the V2.0 is done.

Yves.

Tagging media with BPMs is one way, but like for Motion Dive, they advise you to build all your media to conform to 120 BPM (for example kicks on 0 and 2, snares on 1 and 3, built with edits, effects, CG, whatever), and tapping BPMs in Motion Dive allows the user to automatically conform this media to the resulting BPM.
From a performance standpoint, having all the media be similarly adaptable is just more convenient, but its certainly not the only potential way.

What I've been suggesting here, is that the addition of buttons to allow for automatic 1/8, 1/4, 1/2, 1/1 or 2/1 speed playback would greatly increase performance options and that a keyword allowing scripting access to the total clip length would allow for this kind of usage to be built into the current BPM module "BACF." Sorry if this is hard to understand, guys, this kind feature is basically necessary for alot of people who use Motion Dive.

Thanks for your kind attention, as always.

yves@garagecube wrote:

chromafresh wrote:I'm not talking about starting and stopping playback with a rhythm but actually conforming the total length of the clip to a specified rhythm. Sorry to keep asking... it isn't immediately obvious to me that this would be the case.

Well, this can be achieved by adapting the movie rate. A keyword that returns the time length of the movie should be added. Once you know the time length of the layer you can easily compute the required rate.

So if your rhythm requires the movie to be played in one second and the loop duration is ten seconds, the rate should be set to ten :

newrate = movieTimeLength / rhythmTimeLength

Excellent!
I think I get the idea. (not ready to write scripts yet unfortunately... *sigh*

Thanks for your patience.

Akira:

Regarding midi clock (real time messages), you were right they are not properly handled yet. This is because real time midi messages can be inserted anywhere in the midi stream and my midi parser does not correclty handles this special case. I'll update that for the V2.0 next beta.

Yves.