Elektron Musical Instruments

first off- this box rocks.  i havent been happier with a drum machine, ever (been thru tr909, er-1, xbase and a few others).

ran into my first problem this weekend, its not consistent, having trouble replicating it.  in record mode i was running a G-bank pattern 
(in pattern mode) and switched to another G pattern, which the machine did not visibly respond to (looking for that 1 arrow from 
current to next pattern).  hit the pattern button again but instead of a single arrow i got a double arrow, cycling between old and new 
pattern.  seemed to happen a handful of times- couldnt get that single arrow. i shut the machine down and booted back up, didnt have 
the problem again.  bootup screen shows D 1.12 (OS i presume).  is this a known problem?

tia.

angelzero.

--- In elektron-users@yahoogroups.com, "loopcycle" <angelzero@h...> wrote:
> bootup screen shows D 1.12 (OS i presume).  is this a known problem?

I've never heard it before. Mine will do some pattern-switching
weirdness (like just keep displaying the "bank" window rather than
changing patterns) sometimes, but it's usually when I'm in the mute
menu and then try changing patterns; or something along those lines. 
I can never recreate it when I try to :-)

My MD has the latest OS installed, and it shows "F 1.12b" at the boot
screen.  So perhaps you should try an OS upgrade (available at
www.machinedrum.com)?

If it keeps happening, try to narrow-down the exact scenario for its
occurance and email Elektron about it so that it can be fixed in the
next OS.

Joe.

If you have the one pattern running,

1. You press function and a different pattern you'll get the single
arrow and no cycling back to the old one. 

2.  You hold function and more than one pattern button you'll get the
double arrow and cycling multiple patterns in the order you pressed
the pattern buttons.

I don't think you are seeing a bug.  But I have seen problems with
this.  Often when I was in the G banks not too long ago I would see D
in that four dotted countdown/delay window.  So yea, there are
inconsistancies.  Hopefully Elektron will get the bugs out in a new OS.

--- In elektron-users@yahoogroups.com, "loopcycle" <angelzero@h...> wrote:
> first off- this box rocks.  i havent been happier with a drum
machine, ever (been thru tr909, er-1, xbase and a few others).
> 
> ran into my first problem this weekend, its not consistent, having
trouble replicating it.  in record mode i was running a G-bank pattern 
> (in pattern mode) and switched to another G pattern, which the
machine did not visibly respond to (looking for that 1 arrow from 
> current to next pattern).  hit the pattern button again but instead
of a single arrow i got a double arrow, cycling between old and new 
> pattern.  seemed to happen a handful of times- couldnt get that
single arrow. i shut the machine down and booted back up, didnt have 
> the problem again.  bootup screen shows D 1.12 (OS i presume).  is
this a known problem?

> 
> tia.
> 
> angelzero.

--- In elektron-users@yahoogroups.com, "endlessnessisticman" 
<endlessnessisticman@y...> wrote:

> I don't think you are seeing a bug.  But I have seen problems with
> this.  Often when I was in the G banks not too long ago I would 
see D
> in that four dotted countdown/delay window.  So yea, there are
> inconsistancies.  Hopefully Elektron will get the bugs out in a 
new OS.

That needs us to know about them! If someone would collect a list of 
bugs, and even more important - how to recreate them, that would 
mean wonders in getting them all fixed when we start the next update 
session for the Machinedrum. We try to catch all bugs that we see 
and get mentioned about, but many of the bugs I see mentioned on the 
list here are not known, and the description is not enough to 
recreate them so we can find them. Thats the big problem...

Daniel

Reply to this message with your bugs on the MD (that's Machindrum)
ONLY.  I'm going to keep a note pad handy when I use my MD.  Make sure
you are up to 1.12.

I can put them together.


--- In elektron-users@yahoogroups.com, "daniel_elektron" <daniel@e...>
wrote:

> --- In elektron-users@yahoogroups.com, "endlessnessisticman" 
> <endlessnessisticman@y...> wrote:
> 
> > I don't think you are seeing a bug.  But I have seen problems with
> > this.  Often when I was in the G banks not too long ago I would 
> see D
> > in that four dotted countdown/delay window.  So yea, there are
> > inconsistancies.  Hopefully Elektron will get the bugs out in a 
> new OS.
> 
> That needs us to know about them! If someone would collect a list of 
> bugs, and even more important - how to recreate them, that would 
> mean wonders in getting them all fixed when we start the next update 
> session for the Machinedrum. We try to catch all bugs that we see 
> and get mentioned about, but many of the bugs I see mentioned on the 
> list here are not known, and the description is not enough to 
> recreate them so we can find them. Thats the big problem...
> 
> Daniel

Here comes the MD bugs (OS 1.12):

1. This on needs external midiclock, MM for example. Set MD to 140 
and MM 190 (values doesn't matter as long they differ a lot). Set MM 
to send midiclock to MD and MD to Sync to it (so MD-bpm is in EXT 
mode). 
Problem number one: MD starts about 10 ms late on first hit, syncs 
after that. This maybe corrected by setting md to 190 as with MM, I 
dont know (I just thought of it)

Problem number two: Pickup temposcreen a few times and the MD falls 
with sync. It's nice to look how tight MD runs from tempo screen (can 
I really see this from here, I'm getting 0.3 tempodrifts, anyone 
else?), so this should not tremble(is this english?) MD.

2. If you make two global settings one with internal tempo and second 
one with external and change from external global setting to internal 
the MD shows still EXT in tempo. And you can't change it. It is 
workable by going to global settings and here you can see that tempo 
is set to internal, but when you set it again it recovers.

3. This one is still in 1.12. Take for example trx-snare and link it 
to e12-snare. Ok, now sequence the trx-snare. Everything works fine. 
Now go to e12-snare track and put one parameterlock with some grazy 
retrig (this is easiest to here). Now play the sequence. Every e12-
hit which is linked to trx-snare and happens after the e12-
parameterlock is going with retrig settings. This is with any 
machines, but easiest to here with e12. This should be fixed and when 
in link mode machines should also link the volumes, because now it's 
not possible to do velocity sensitive snareing with linked machines, 
because you have to do those hits that have different volume lock 
again in the another linked machine, for keeping the consistancy of 
your sound.

4. Sometime in MD songmode the mute column does not work, you can't 
change mute settings. I don't know how to reproceduce this... :(

Toni
Anymore anyone?

--- In elektron-users@yahoogroups.com, "tahvenaine2002" 
<tahvenaine@c...> wrote:

> Problem number two: Pickup temposcreen a few times and the MD falls 
> with sync. It's nice to look how tight MD runs from tempo screen 
(can 
> I really see this from here, I'm getting 0.3 tempodrifts, anyone 
> else?), so this should not tremble(is this english?) MD.

Don't take the tempo that displays in the tempo-window too serious. 
MIDI time clocks is no exact science. It is actually not a tempo that 
is transmitted, but ticks when the sequencer should advance. There 
are six such ticks for each led in the MD in normal 1x mode. The 
Machinedrum locks dead tight on these, but the tempo displayed is 
calculated from the time from one tick to another, and the exact time 
for these may vary a little, which can be seens as the tempo 
drifting. But the timing can be very tight anyway.

Hope you can follow my explanation. :) The bottom line is - don't 
panic if the tempo seems to vary some tenth parts of a bpm up and 
down.

Daniel