Elektron Musical Instruments

I got your email, but when I tried to reply, the delivery was refused.

So I decided to post a message on here instead (I'm not sure if you're a member of the 
Yahoo Elektron group or not).


It's supposed to work like that. Here's what you're missing: you
should have one document open for each track you want to work with.
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.
Try playing around with opening/saving/closing multiple documents. I'm
sure you'll get the hang of it.

Let me know if you're still confused :)

Andrew

 
 
you original email:

It's a fantastic app.
thank you so much first.
I really want to use it.
However, I have a problem.
Everytime I change the track(eg.BD to HiHat), the track copies all
the parameters from previous track.
So they all sound same.
If I choose some different sound in machine(on hi hat track) menu
and go back to previous track(BD track), now it again copies all the
parameters from hi hat track and BD track sounds hi hat.

Am I missing something?

Please help.

Thank you
Jin.

Thank you so much Andrew!
I'll try that and get back to you 


--- In elektron-users@yahoogroups.com, "sidstationownsyou" 
<sidstationownsyou@h...> wrote:
> 
> I got your email, but when I tried to reply, the delivery was 
refused.
> 
> So I decided to post a message on here instead (I'm not sure if 
you're a member of the 
> Yahoo Elektron group or not).
> 
> 
> It's supposed to work like that. Here's what you're missing: you
> should have one document open for each track you want to work with.
> 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.
> Try playing around with opening/saving/closing multiple documents. 
I'm
> sure you'll get the hang of it.
> 
> Let me know if you're still confused :)
> 
> Andrew
> 
> ?> ?> you original email:
> 
> It's a fantastic app.
> thank you so much first.
> I really want to use it.
> However, I have a problem.
> Everytime I change the track(eg.BD to HiHat), the track copies all
> the parameters from previous track.
> So they all sound same.
> If I choose some different sound in machine(on hi hat track) menu
> and go back to previous track(BD track), now it again copies all 
the

> parameters from hi hat track and BD track sounds hi hat.
> 
> Am I missing something?
> 
> Please help.
> 
> Thank you
> Jin.

> 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

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

Is the MIDI Base Channel in MD Machine Lab's preferences the same as the MIDI Base 
Channel on your Machinedrum? If it isn't, that would be the source of your problems.


--- In elektron-users@yahoogroups.com, "gazaebal5775" <sixbong@s...> wrote:

> 
> 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

It was the same.
I had 1 for machine lab
and 1-4 for MD(I'm not sure what 1-4 means)


--- In elektron-users@yahoogroups.com, "sidstationownsyou" 
<sidstationownsyou@h...> wrote:
> 
> Is the MIDI Base Channel in MD Machine Lab's preferences the same 
as the MIDI Base 
> Channel on your Machinedrum? If it isn't, that would be the source 
of your problems.
> 
> 
> --- In elektron-users@yahoogroups.com, "gazaebal5775" 
<sixbong@s...> wrote:
> > 
> > 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

hmm... not sure what the problem is...

I haven't been able to find any bugs, and no one other than you has reported any. Could 
you send me the sysex files you're using? My email address is on my site:
http://www.cs.camosun.bc.ca/~c0262447/

Also, could you give a detailed description of the problems you're having? Try to be very 
detailed. Tell me every step you perform, and the exact results of each step. The more info 
the better.

Thanks,

Andrew


--- In elektron-users@yahoogroups.com, "gazaebal5775" <sixbong@s...> wrote:

> 
> It was the same.
> I had 1 for machine lab
> and 1-4 for MD(I'm not sure what 1-4 means)
> 
> 
> --- In elektron-users@yahoogroups.com, "sidstationownsyou" 
> <sidstationownsyou@h...> wrote:
> > 
> > Is the MIDI Base Channel in MD Machine Lab's preferences the same 
> as the MIDI Base 
> > Channel on your Machinedrum? If it isn't, that would be the source 
> of your problems.
> > 
> > 
> > --- In elektron-users@yahoogroups.com, "gazaebal5775" 
> <sixbong@s...> wrote:
> > > 
> > > 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