Yahoo Groups archive

Elektron Musical Instruments

Index last updated: 2026-04-28 23:22 UTC

Message

Re: To Jin (if they are on here)

2005-02-25 by gazaebal5775

OK I tried it.

I impoerted individual kits from MD and saved under their own names.
like..3_ EFM STD..... using sysex labrarian
Some of them reproduce same sound when I import specific kit's sysex
into machine lab but some of them don't.
e.g.; If I import kit 06 TRX MOOMIN, as soon as all the windows open,
track 7(rim shot) has gone. No sound at all.
So I tab the all the parameter's knob from MD and it still no sound.
However, if I radomize track 6 window from machine lab, it starts 
making noise.
Track 7 and 9 are gone when I do with kit 02 TRX STD

also when I import a kit in machine lab, some of them don't have 16
windows.  like 10 or 12....

........
Jin


--- In elektron-users@yahoogroups.com, "sidstationownsyou" 
<sidstationownsyou@h...> wrote:
> 
> 
> > OK, I see now.
> > So is there any way to get the current parameter's data from MD
> > and edit it from Machine lab?
> >
> 
> There is no way for any MIDI device (including MD Machine Lab) to 
detect what the current 
> parameter values are, or what the current machine type is (that I 
know of). There are, 
> however, two solutions.
> 
> The first is to take advantage of the sysex file import function I 
just added in this version. 
> It lets you import a kit from a sysex file (specifically, a kit 
dump).
> 
> The second way is to unplug you MIDI cables from MD after it first 
boots up. Then open as 
> many new documents as necessary, and set the machine type to match 
your MD for each 
> track. Then, connect the MIDI cables and tab the MD's knobs (or 
turn them if that doesn't 
> work). MD Machine Lab will detect the knob tweaks and update 
accordingly.
> 
> Sorry, but a lot of MD Machine Lab quirks come from the 
limitations of Machinedrum's 
> MIDI support (though it does offer MUCH better MIDI functionality 
than other synths I've 
> seen).
> 
> However, MD Machine Lab is meant to edit Machinedrum, not the 
other way around. I 
> suggest creating all your sounds in MD Machine Lab, and saving 
them (as MD Machine Lab 
> documents). You can re-open any documents you like to tweak them. 
The real power 
> comes through when you want to create a new kit. Just open all the 
documents you want 
> to use as sounds in you kit, then save the kit on MD.
> 
> Tip: create folders to hold each type of drum sound you make. For 
example, a "snare" 
> folder. Keeping things organized will help you to throw kits 
together quickly.
> 
> 
> > And second problem is...
> > Let's say I have 6 windows opend for 6 different sounds.
> > I go to window 1 (BD) from window 6.
> > As soon as I get to window 1, it changes the sound.
> > I lose kick sound I've edited.
> > This happens sometimes but ramdomly,,,not always....
> 
> As I said in my previous post, "If, for some reason, you have 2 
documents open with the 
> same track number, the document window you clicked on last will be 
the sound you hear 
> on Machinedrum". In other words, if you want to hear the sound 
from a particular 
> document, click on its window.
> 
> I made it this way so that you can work on as many documents as 
you like, even if some of 
> them have identical track numbers. It also helps keep things in 
sync (i.e. keep the state of 
> Machinedrum the same as MD Machine Lab).
> 
> 
> 
> 
> >
> > Maybe I'm asking too much......
> 
> It's no problem! I love getting emails about my program... they 
let me know that people 
> are actually using it ;)
> 
> >
> > Thank yo

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.