Elektron Musical Instruments

Hi. Could someone please explain exactly how or refer me to the post 
that explains how to transmit machinedrums midi into cubase(or any 
software sequencer, pro tools etc.) so that each md sound/track is on 
a different track in the software sequencer. Like kik on track 1 in 
the software sequencer, snare 2, etc. etc. I searched for the anwser 
cause I seem to remember something about it but couldnt find an 
anwser. Thanks. Susan

On Sat, Oct 02, 2004 at 08:34:25PM -0000, vampyrecat13 wrote:
>    Hi. Could someone please explain exactly how or refer me to the post
>    that explains how to transmit machinedrums midi into cubase(or any
>    software sequencer, pro tools etc.) so that each md sound/track is on
>    a different track in the software sequencer. Like kik on track 1 in
>    the software sequencer, snare 2, etc. etc. I searched for the anwser
>    cause I seem to remember something about it but couldnt find an
>    anwser. Thanks. Susan

there is no good way.  the Machinedrum always outputs the triggering of
all tracks on its base MIDI channel.  the parameters for the
individual tracks are then mapped in sets of four to the four MIDI
channels in the MD's channel span.

the only way to map each track to a separate channel is to record
each of them individually and change your base channel in the global
section between each recording.

Ok so you have your six outputs you record your midi sequence from MD 
to a Midi track in whatever your sequencer is, then you create 5 more 
midi tracks set them to MD123456 then copy your whole sequence from the 
1 midi track to midi tracks 123456 now blow them all up and star on 
midi 1 cause thats where your kick is and delete all midi data on that 
track except the kick drum trigger pattern Then go to midi track 2 
delete all midi data except the snr trigger pattern so on and so on 
this is the best and only way to do it also when your first midi 
pattern from MD is imported to your sequencer remember to quantize that 
whole pattern so it snap to your sequncers 16th note grids then do the 
steps I mentioned above!!!!! Also when you want to burn your midi 
tracks to audio you will notice a bit of latency straying away from 
your sequencers 16th note grid you must go in and trim each audio hit 
on each of your audio tacks so that you push the attack of the waveform 
sample accurate to you grid Otherwise the latency from MD is going to 
be an issue when you use your softsynths becuase a softsynth has way 
less latency and then your timing for your song will suffer dramatic 
results so basically  time correct everything to grid you will see A 
huge improvement in you r mix as well from this but it is time 
consuming!!!!! Hope this helps regards Paul
On Oct 2, 2004, at 1:34 PM, vampyrecat13 wrote:

>
>
>  Hi. Could someone please explain exactly how or refer me to the post
>  that explains how to transmit machinedrums midi into cubase(or any
>  software sequencer, pro tools etc.) so that each md sound/track is on
>  a different track in the software sequencer. Like kik on track 1 in
>  the software sequencer, snare 2, etc. etc. I searched for the anwser
>  cause I seem to remember something about it but couldnt find an
>  anwser. Thanks. Susan
>
>
>
>
>
>
> Yahoo! Groups Sponsor
>
> ADVERTISEMENT
> <ff_holding_300x250_0904.jpg>
> <l.gif>
>
> Yahoo! Groups Links
>
> 	� 	To visit your group on the web, go to:
> http://groups.yahoo.com/group/elektron-users/
> �
> 	� 	 To unsubscribe from this group, send an email to:
> elektron-users-unsubscribe@yahoogroups.com
> �
> 	� 	 Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
> Service.
>
>  

[Non-text portions of this message have been removed]

speculation time.

is it possible?  probable?  coming real soon now?


-- 
yours,
niall.
.. .  .   .    .     .       .           .             .                 .
aleph null.                             a simple insinuation around silence.
http://syncretism.net
.. .. gpg public key - http://www.aleph-null.net/niall.gpg .. ..

--- In elektron-users@yahoogroups.com, niall munnelly <aleph@a...> 
wrote:
> speculation time.
> 
> is it possible?  probable?  coming real soon now?

I approached this subject quite some time ago on this list... and it 
was a pretty firm NO.  I even got into nit-picking the details with 
Daniel.  The problem is that the parameter locks can theoretically 
exceed the maximum data rate that CC's can handle.  I recommended 
that they just monitor the rate at which CC's were being sent, and 
send a flag saying "rate exceeded" to the user if and when it 
happened.  I put a lot of parameter locks into sequences, but it 
would be extremely rare to find enough locks in a given pattern to 
cause problems.  I even did the math to show that this is the case.  

As ususal, a "half assed" solution is never acceptable to elektron.  
Same reason they won't record the joystick movements as parameter 
locks - because you cannot store 14 bit pitch bends in the parameter 
lock structure.  It's all or nothing.  It's a good thing that what it 
does do, it does very well.

-gerald

>
> Ok so you have your six outputs you record your midi sequence from MD
> to a Midi track in whatever your sequencer is, then you create 5 more
> midi tracks set them to MD123456 then copy your whole sequence from the
> 1 midi track to midi tracks 123456 now blow them all up and star on
> midi 1 cause thats where your kick is and delete all midi data on that
> track except the kick drum trigger pattern Then go to midi track 2
> delete all midi data except the snr trigger pattern so on and so on
> this is the best and only way to do it also when your first midi
> pattern from MD is imported to your sequencer remember to quantize that
> whole pattern so it snap to your sequncers 16th note grids then do the
> steps I mentioned above!!!!! Also when you want to burn your midi
> tracks to audio you will notice a bit of latency straying away from
> your sequencers 16th note grid you must go in and trim each audio hit
> on each of your audio tacks so that you push the attack of the waveform
> sample accurate to you grid Otherwise the latency from MD is going to
> be an issue when you use your softsynths becuase a softsynth has way
> less latency and then your timing for your song will suffer dramatic
> results so basically  time correct everything to grid you will see A
> huge improvement in you r mix as well from this but it is time
> consuming!!!!! Hope this helps regards Paul

My MD receives midi clock from Logic and it had to be delayed by 12 
samples; and latency shouldn't be an issue on the MD, it's not a 
plug-in with a buffer setting...
So, if you set up correctly your sequencer, you should be able to have 
perfectly on time MD, always.

By the way, I think that recording the patterns of the MD into midi is 
almost a non-sense.
I understand the purpose of recording midi cc, but you should record 
the audio instead of midi notes.

For the way I work (creating patterns on the MD, recording 6 audio 
tracks from the 6 outputs, then arranging the parts into Logic), it is 
an unnecessary step, but it could be useful to someone else that works 
in a different way.

How do you get perfect timing with your MD slaved to logics sequencer 
and what do you mean you had 12 samples of delay how did you compensate 
for that within logic? I just like to beable to edit more on the 
computer but right now im expieriencing even when recording straight 
audio out of the MD into Protools sequencer a significant delay meaning 
the attack of the hits is not spot on with grid have any suggestions?
On Oct 4, 2004, at 6:33 PM, Federico Ciapi wrote:

> >
>  > Ok so you have your six outputs you record your midi sequence from 
> MD
>  > to a Midi track in whatever your sequencer is, then you create 5 
> more
>  > midi tracks set them to MD123456 then copy your whole sequence from 
> the
>  > 1 midi track to midi tracks 123456 now blow them all up and star on
>  > midi 1 cause thats where your kick is and delete all midi data on 
> that
>  > track except the kick drum trigger pattern Then go to midi track 2
>  > delete all midi data except the snr trigger pattern so on and so on
>  > this is the best and only way to do it also when your first midi
>  > pattern from MD is imported to your sequencer remember to quantize 
> that
>  > whole pattern so it snap to your sequncers 16th note grids then do 
> the
>  > steps I mentioned above!!!!! Also when you want to burn your midi
>  > tracks to audio you will notice a bit of latency straying away from
>  > your sequencers 16th note grid you must go in and trim each audio 
> hit
>  > on each of your audio tacks so that you push the attack of the 
> waveform
>  > sample accurate to you grid Otherwise the latency from MD is going 
> to
>  > be an issue when you use your softsynths becuase a softsynth has way
>  > less latency and then your timing for your song will suffer dramatic
>  > results so basically� time correct everything to grid you will see A
>  > huge improvement in you r mix as well from this but it is time
>  > consuming!!!!! Hope this helps regards Paul
>
>  My MD receives midi clock from Logic and it had to be delayed by 12
>  samples; and latency shouldn't be an issue on the MD, it's not a
>  plug-in with a buffer setting...
>  So, if you set up correctly your sequencer, you should be able to have
>  perfectly on time MD, always.
>
>  By the way, I think that recording the patterns of the MD into midi is
>  almost a non-sense.
>  I understand the purpose of recording midi cc, but you should record
>  the audio instead of midi notes.
>
>  For the way I work (creating patterns on the MD, recording 6 audio
>  tracks from the 6 outputs, then arranging the parts into Logic), it is
>  an unnecessary step, but it could be useful to someone else that works
>  in a different way.
>
>
>
>
> Yahoo! Groups Sponsor
>
> ADVERTISEMENT
> <ff_holding_300x250_0904.jpg>
> <l.gif>
>
> Yahoo! Groups Links
>
> 	� 	To visit your group on the web, go to:
> http://groups.yahoo.com/group/elektron-users/
> �
> 	� 	 To unsubscribe from this group, send an email to:
> elektron-users-unsubscribe@yahoogroups.com
> �
> 	� 	 Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
> Service.
>
>  

[Non-text portions of this message have been removed]

On Tue, Oct 05, 2004 at 01:13:17AM -0000, oldmanfury wrote:

> I approached this subject quite some time ago on this list... and it 
> was a pretty firm NO.  I even got into nit-picking the details with 
> Daniel.  The problem is that the parameter locks can theoretically 
> exceed the maximum data rate that CC's can handle.

gerald,

thanks for the (as-always) informative response.  this does sound kinda dubious, but it
sounds like it's pretty well established that parameter locks over CC just won't
happen.

so, how about a program that can translate the sysex dump of a single pattern (or maybe
a chain?) to a standard midi file?  is it possible?

-- 
yours,
niall.
.. .  .   .    .     .       .           .             .                 .
aleph null.                             a simple insinuation around silence.
http://syncretism.net
.. .. gpg public key - http://www.aleph-null.net/niall.gpg .. ..