Elektron-Users

...the ability to have any one of the 16 sounds be able to spread across a midi keyboard. this way you'd have octave control of each hit. i doesn't seem like it'd be that hard to implement...but i really have no idea :-D

that would be neat...good idea...I like that one.

What i would like to see implemented ?:

1 -one scale setup per machine (just like the Swing,Accent,Slide)
So you could have, say: BD and SD running for 4 bars; while the CH's are going for 3 bars.
This way the MD would get a 1000x more lively ((i reckon)).
(or maybe not bars but just steps for even more weirdness)

2 -I'd like to have the old program-number option back (os 1.12) When I don't use the internal sequencer (it's not that often) I would like to switch the kits instead of triggering a pattern. maybe a Global function?

( can't they make an option in that c6 software that just converts the old sysex to the new and the other way round? ) (i reckon they can but rather don't, because they change OS's very often)

3 -And i have to agree with MokBor: I would rather have a rocksteady MD than a pimped-up blingbling MD with shiny wheelcaps. Please 1st fix the existing bugs before implementing even more! (e.g. MIDI-machines)

dB-)
Bart

speaking of all this, i wonder when this new feature enhanced MD OS will be out?

BartBral wrote:
What i would like to see implemented ?:

1 -one scale setup per machine (just like the Swing,Accent,Slide)
So you could have, say: BD and SD running for 4 bars; while the CH's are going for 3 bars.
This way the MD would get a 1000x more lively ((i reckon)).
(or maybe not bars but just steps for even more weirdness)


Elektron already stated that this wouldn't happen and we discussed about this ealier(i believe in this topic) to keep it short it would require a complete change in the MD OS requiring a rewrite, which is not gonna happen. To spruce up a pattern to be more organic and lively just use a lot of lfo's :-D that should get the job done aswell.


2 -I'd like to have the old program-number option back (os 1.12) When I don't use the internal sequencer (it's not that often) I would like to switch the kits instead of triggering a pattern. maybe a Global function?


This is also not gonna happen, there will be no changes made to the global menu becuase that would break compatiblity with older made sysex backups, also this subject was also discussed about ealier.


( can't they make an option in that c6 software that just converts the old sysex to the new and the other way round? ) (i reckon they can but rather don't, because they change OS's very often)


Let's focus on a good stable os like i said ealier, i still have some bugs, and still find new quirks.


3 -And i have to agree with MokBor: I would rather have a rocksteady MD than a pimped-up blingbling MD with shiny wheelcaps. Please 1st fix the existing bugs before implementing even more! (e.g. MIDI-machines)





Im also a bart :-P

Although im not dirty of a feature request either. :-D

I would like to introduce a change in the lfo system, to allow even more complex envelope like modulations by using the trig settings, While the options trig, hold and free are available i reckon a "trig target track" option should also be availble.

In it's current form lfo's only can be trigged by the track it's location is on, i use mutiple lfo's on 1 machine or track alot(lfo's from different tracks mapped to one track). Altough it's not possible to use the trig from the track unless the lfo is on the track itself. Now it just follows the trigs that are on the lfo track location. With an additional trig type we can let all lfo's be trigged from the same track.

I guess this will be hard to implent becuase the lfo trigs are probably hard coded to the track. But it's always nice to inject some new idea's.

That's an interesting idea...you could achieve the same thing currently by dedicating the surplus LFOs to trigging in sync with the target pattern (and generate no noise), obviously sacrificing that track for sound generation...but that idea would make it way easier.

Okay then, a new 'machine' idea then. What about a 'retrig' midi machine.

I was thinking (dreaming) somethin' like this:

note# | note lenght | cc# | CC Attck/Decay env
-------------+--------------+---------------+---------------+
numb. of trigs | retrig time |trig VelAtck/decay | pitch bend |

i was thinking, Quantized retrig times would be nice with that, and that CCdecay could be a sort of attack/decay env going thru a sampleAndHold (sampling every triger) and using that for the cc amount. Same for trig Vel attack/Decay. ..... oh jeay with that attack/decay envelope i mean negative values would increas attack time - Positive values would increase decay time.

just a thought (dream)

-Bart dB-)

whoa...retrig midi machine....that's an awesome idea...plus the "CC envelope" thing is sick...good thinking man, got any other machine ideas?

(it seems like the "machine" concept is so modularizable...what if they released a toolkit to allow user-made machines! yeah right...)

ggoodwin wrote:
whoa...retrig midi machine....that's an awesome idea...plus the "CC envelope" thing is sick...good thinking man, got any other machine ideas?

(it seems like the "machine" concept is so modularizable...what if they released a toolkit to allow user-made machines! yeah right...)

Dunno how much MD users have the skills to build machines. Trust me there is some high level programming required for that sort of stuff. I guess that's simply impossible.