Elektron Musical Instruments

So, I'm compiling my semi-annual bug and proposed features
list for the Machinedrum UW, and would like to get the
community's feeling about one of the items:

+ Control + knob turn changes the corresponding parameter on
all tracks by the same amount.  For example, let's say I
change BD's SRR value from 80 to 127 while holding the
function key.  All other tracks' corresponding SRRs
increment by 47 - they don't all change to the same value
{127}.  So, in other words, function + encoder changes by the
amount incremented or decremented, rather than setting every
track's BRR parameter to the same value.  Is this behavior
by design?  There might be times when I want everything to
have the same value when I function + encode a parameter -
like mix volume, or filter settings.  The CTL machines work
the opposite way, applying the absolute parameter value to
all tracks.

So, Elektron-Users - how do you feel about this?  Would 
you expect one behavior, rather than the other?  Do you
prefer one behavior to another?

-- 
Yours,
Niall.
.. .  .   .    .     .       .           .             .                 .
Aleph Null.                             A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://aleph-null.net/niall.gpg .. ..

Personally I prefer and expect it the way it is now, I'd definitely
rather have relative versus absolute changes myself.

On 28/11/2007, Niall Munnelly <aleph@...> wrote:
> So, I'm compiling my semi-annual bug and proposed features
> list for the Machinedrum UW, and would like to get the
> community's feeling about one of the items:
>
> + Control + knob turn changes the corresponding parameter on
> all tracks by the same amount.  For example, let's say I
> change BD's SRR value from 80 to 127 while holding the
> function key.  All other tracks' corresponding SRRs
> increment by 47 - they don't all change to the same value
> {127}.  So, in other words, function + encoder changes by the
> amount incremented or decremented, rather than setting every
> track's BRR parameter to the same value.  Is this behavior
> by design?  There might be times when I want everything to
> have the same value when I function + encode a parameter -
> like mix volume, or filter settings.  The CTL machines work
> the opposite way, applying the absolute parameter value to
> all tracks.
>
> So, Elektron-Users - how do you feel about this?  Would
> you expect one behavior, rather than the other?  Do you
> prefer one behavior to another?
>
> --
> Yours,
> Niall.
> .. .  .   .    .     .       .           .             .                 .
> Aleph Null.                             A Simple Insinuation Around Silence.
> http://aleph-null.net
> .. .. gpg public key - http://aleph-null.net/niall.gpg .. ..
>
>
>
> Yahoo! Groups Links
>
>
>
>


-- 
Tarekith
http://tarekith.com

On Wed, Nov 28, 2007 at 05:28:15PM -0800, Tarekith wrote:
> Personally I prefer and expect it the way it is now, I'd definitely
> rather have relative versus absolute changes myself.

I can see the appeal of both approaches - thanks for
answering!

-- 
Yours,
Niall.
.. .  .   .    .     .       .           .             .                 .
Aleph Null.                             A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://aleph-null.net/niall.gpg .. ..

Yeah.

I agree : it seems better to have the choice between the two behaviors. That's why I think it's ok for me (though I even didn't know this difference, elektron newbie as I am...)

What ? A CTRL-AL-ABS and a CTRL-AL-REL machines ?? Hmm... could be a solution, but would be more machine for details. Isn't the Elektron's do-it-tricky way to compose one of the reasons of your choice, guys ?...

Thanks !

steve


> Personally I prefer and expect it the way it is now, I'd definitely

> rather have relative versus absolute changes myself.



I can see the appeal of both approaches - thanks for

answering!

 



















_________________________________________________________________
Découvrez le blog Messenger Le Meilleur du Web : toutes les vidéos qui buzzent le plus sur Internet !
http://meilleurduweb.spaces.live.com/

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

So, here's another one.  

Set up a new kit with a TRX BD and a TRX SD.
Make each mute the other in their machine edit mode.
Trigger BD on steps 1 and 7.
Trigger SD on steps 5 and 13.
Play back, and gradually increment the BD's decay to a very
long amount, like 120 or so.

You'll find that the SD doesn't chock the BD entirely -
rather, it acts like a sidechained duck, working only  
while there's a signal from the SD.  Hihats, though, at
least in the TRX set, do seem to choke the sounds totally,
as expected.  So, there's an apparent inconsistency in the
behaviors, here.  Do we like it?

-- 
Yours,
Niall.
.. .  .   .    .     .       .           .             .                 .
Aleph Null.                             A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://aleph-null.net/niall.gpg .. ..

Scratch this one.  It went away with a soft reset =P


On Thu, Nov 29, 2007 at 01:08:12PM -0800, Niall Munnelly wrote:
> So, here's another one.  
> 
> Set up a new kit with a TRX BD and a TRX SD.
> Make each mute the other in their machine edit mode.
> Trigger BD on steps 1 and 7.
> Trigger SD on steps 5 and 13.
> Play back, and gradually increment the BD's decay to a very
> long amount, like 120 or so.
> 
> You'll find that the SD doesn't chock the BD entirely -
> rather, it acts like a sidechained duck, working only  
> while there's a signal from the SD.  Hihats, though, at
> least in the TRX set, do seem to choke the sounds totally,
> as expected.  So, there's an apparent inconsistency in the
> behaviors, here.  Do we like it?

-- 
Yours,
Niall.
.. .  .   .    .     .       .           .             .                 .
Aleph Null.                             A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://aleph-null.net/niall.gpg .. ..