Midi sync with Machine drum
can some one tell me how to make a MIDI sync, to hit the Elektron Machine Drum.
or where to find information about the compile of the midi msg?
You want to sync max to the drum machine or vice versa?
The 'rtin' object will receive realtime messages from your drum machine. I was never able to figure out if MAX could *send* these messages though (there doesn't seem to be an rtout object, at least not in MAX4).
The complete MIDI 1.0 specs can be obtained here:
http://www.midi.org/about-midi/specinfo.shtml
Joshua
hi,
like that :
fxw
What IS that?
> like that :
>
>
>
> fxw
----------------------------------------------------
hi
this is max 5 patch.
you have to copy all this text and select 'File/New from clipboard' in max 5
Here is the same patch for max 4.6 :
fxw
Hello, this a sync from max/msp transport hero > machine drum.
thx, for quick reply!
thx Francois the patch and detailed copy info ;)
regarding the MIDI specs... they are kinda new to me in terms of crontrolling hardware.
The Elektron Machine Drum is able to recive some sort of ctrl in where is would like a MIDI start, and stop msg. anyone knows about this?
I think this could be done with the [ ctlout ] object?
in the MIDI specs, can you guide me to where i need to read about this?
btw, that start, stop msg. is used to play, pause the machine
On May 17, 2008, at 1:38 PM, joewhat wrote:
> The Elektron Machine Drum is able to recive some sort of ctrl in
> where is would like a MIDI start, and stop msg. anyone knows about
> this?
These are considered "real time" messages.
This patch sends clock and transport info. It takes an argument for
what MIDI port to use.
Chris Muir
cbm@well.com
http://www.xfade.com
thank you very much chris
hi,
In the Chris patch, you can see the Start cmd (250) and Stop cmd (252). there is a 'Continue' cmd (251) and of course the clock click (248).
this is part of 'real time MIDI messages' not 'voices messages'. So the [ ctlout ] object can not send them.
Note : hexadecimal >> 250=FA, 251=FB, 252=FC
this seems pretty interesting..chris do you have a ClockIn patch to to show us..i tried it without reliable results..
anyway i've tried anohter time, with different approaches and there is no reliable possibility to sync max/msp as slave to a korg es-1, that's a matter of fact. it's very sad because i can sync reason to the es-1 with rock-solid timing
"anyway i've tried anohter time, with different approaches and there is no reliable possibility to sync max/msp as slave to a korg es-1, that's a matter of fact. it's very sad because i can sync reason to the es-1 with rock-solid timing"
This is tragic news for me because I'm supposed to be doing a show with a friend where our laptops are slaved to an ES-1. He's using Reason, I'm using Max. I can get the Transport in my Max patch to start when I hit "play" on the ES-1, no problem. But the tempos drift and apparently there's no way to directly slave Max to the ES-1. Can anyone think of a workaround here?
I believe the ES-1 can send a midi clock out. In max, the rtin object will receive this kind of messages. you can hook it up to a counter object with 23 as max count (0 to 23) and each cycle will give you one beat. Or.. even easier you can hook the rtin to the sync~ object.
I encountered the same issue with my machinedrum a few days ago when I wanted to switch my master from max to the MD and all my problems got solved when I found the rtin object.
Good luck.
Thank you. I was trying some stuff with rtin and sync~ and not having much luck. I'll try the counter thing.
Any chance you could post a little example of how you personally use rtin and sync~?
This is my rtin subpatcher.
I am stuck with a transport object as my main clock because I use vsts that need to be bpm sync.
I use the sync~ object to calculate the bpm and send it back to the transport object and I detect the 250, 251 and 252 messages which are play, unpause and stop, respectively from the machinedrum.
If I did not need to use the transport object, I would use a counter like I explained previously. I got the counter idea from the rtin reference. You need to select 248 otherwise the rtin object will receive other messages such as play and stop like I previously explained.
Apparently, the 248 messages can also be used with the seq object, by sending the message "tick" to the seq object every time a 248 is received. Look at the rtin help for more details.
I ended up just using two midiout objects to send realtime MIDI values from the two MIDI-out ports on my controller. Sent one to the ES-1 and one to Reason on my friend's laptop (via his controller). Simple as anything and worked like a dream.
(FYI, when we tried to slave his laptop to the ES-1, the laptop said the tempo was something like 119.75, when the readout on the ES-1 said 120, which explains the drifting I was experiencing.)
Hmm for me it didn't work with the midiout object.. it must depend on the devices..
As for the tempo saying 119.75, I think it's because max is more accurate than these devices.. my machinedrum often gives me 159.9 instead of 160.