Digitone feature requests!

Yeah, I would really like that too.

Yeah Monomachine and Machinedrum have an EQ on every track and it is very very useful in doing that or boosting some part of the spectrum.

5 Likes

A third LFO.

6 Likes

Request I submitted to Elektron earlier this year but got nothing but the auto-reply. I really wish they would look at Pattern Grouping.

ā€ Good morning/afternoon,

I have two feature requests for the Digi boxes:

  • Pattern Grouping
  • MIDI Takeover Behavior and/or CC61 ā€˜Send All Parametersā€™

Pattern Grouping:

Issue - Currently, when working on multi-pattern compositions, it is not possible to have parameter changes from one pattern be propagated to other patterns within a composition. On the Analog series (Rytm and Four), this is accommodated with the ā€˜Kitsā€™ structure and, on the Octatrack, with ā€˜Partsā€™. Changes made to the Kit/Part are reflected across all patterns using that Kit/Part.

Proposed Solution - Allow patterns to be assigned to either ā€˜Noneā€™ (default behavior) or 1 of 16 Pattern Groups per project (depending on memory constraints). Patterns assigned to the same Pattern Group will have all parameter changes reflected across all members of the same group.

Many users have been asking for a ā€˜Kitsā€™ structure on the Digi series for quite some time. I understand that it might be too prohibitive to implement a full ā€˜Kitsā€™ structure where users could save their sample/tracks/sounds settings to an easily recallable kit. I believe the fundamental issue is as described above though. Pattern Groups would address this issue in, I believe, a fairly easy, resource considerate method. All patterns currently have to store their settings in a table of hash of some sort. This same table could have another field added with the group ID to be referenced on pattern change.

Considerations -

  • Behavior of the ā€˜FUNC + Yesā€™ temporary pattern save. This would ideally be linked to Pattern Groups as well. A temporary save on one pattern could be reloaded from another pattern of the same group.
  • Behavior of ā€˜Global FXā€™ settings. Should ā€˜Global FXā€™ settings, when enabled, take precedence over Pattern Group settings? Conflicts?
  • Pattern Grouping should not be tied to or implemented in ā€˜Song Modeā€™ as this constrains users to that function.

MIDI Takeover Behavior and CC61 (Send all MIDI values to external controller):

Issue - Currently, when using an external controller, the MIDI takeover will jump to the value on the device being sent from the controller. If a person uses the control on the device to modulate Filter Cutoff then uses the Filter Cutoff control of the MIDI controller, the value on the device will jump to the incoming value producing undesirable effects.

Proposed Solution - Allow users to configure the MIDI takeover behavior as a global setting. In ā€˜Jumpā€™ mode, the unit behaves as it currently does; parameters will jump to the incoming value regardless of disparity. In ā€˜Takeoverā€™ mode, the parameter will not change until the incoming value matches the value on the device. This prevents undesirable jumps.

A less elegant but still effective solution would be to mimic the CC61 behavior of the Octatrack. This would allow a user to send CC61 to the device to ā€˜resetā€™ the values on the MIDI controller so that parameter jumps do not occur.

Thank you for considering these feature requests. The recent implementation of ā€˜Song Modeā€™ on the Digi boxes has been a welcome addition! For me, and many others, Pattern Grouping would make a tremendous difference not only for ease of multi-pattern compositions but for live performances as well.

Cheers!"

10 Likes
  • possibility to keytrack OFF an operator (A or B) to avoid him to be affected by the midi notes.

  • Possibility to tie notes in Arpegiator

  • Kits (for all black small Elektron boxes)

2 Likes

You know about the Legato play mode? https://youtu.be/VXx8kLO5Cl4

1 Like

Kits donā€™t make sense on Digitone.

Kits/Parts, or my suggestion of Pattern Grouping, absolutely make sense. Having multi pattern arrangements where you have to copy parameters back and forth between patterns, is a pain in the ass. Have a kit/or pattern grouping would fix this problem. Read my feature request I sent in just a couple of posts back.

5 Likes

OK, I guess thatā€™s a bit different then.

sorry i meant in arpegiator.

if m13wo says soā€¦ :wink:
A4 and ARytm have kits and itā€™s a really cool feature.
for me an access to a kit library like we have a sound library would be perfect.
on Digitakt, Syntakt but on Digitone too.

2 Likes

Like I have suggested here before wouldnā€™t it be simpler if you could just keep your current patternā€™s sounds while switching pattern? If the aim is to jam with the same sounds over several patterns this would be sufficient and allow parameter changes across different patterns without reverting. Machinedrum has this feature with its Classic/Extended mode and itā€™s just an on/off function.

Iā€™m personally very happy with the individual pattern (non-kit) functionality of the Digitone which allows you to make even small changes to the same sounds in different patterns without having to save a new kit with a new name every time. Actually I often wish Machinedrum and Monomachine had this. But Iā€™d welcome the Classic/Extended mode feature.

3 Likes

Thatā€™s the whole point of ā€˜Pattern Groupingā€™. It would make is so changes to sound parameters on one pattern would be mirrored onto all patterns in the same group. If I adjust the filter cutoff on Track 1, Pattern 1, it will be reflected in the ā€˜Pattern Groupā€™. It doesnā€™t do this now. If I make a multi pattern song then adjust say, the base-width filter to cut a little more low end out, I have to replicate that change across all patterns in my song. ā€˜Pattern Groupingā€™ would solve this.

Personally, I donā€™t care to save sound templates as ā€˜Kitsā€™. I just want the behavior of edits/changes being propagated across all patterns using that kit.

3 Likes

AT, PB, BC and MW control for internal sequencer same as for midi tracks.

why? because it makes DN completely different sounding instrument (almost like modular ) with macro assignments and per step and lfo macro modulations.

I donā€™t get why they left it, it completely open up DN as sound module.

6 Likes

It would be amazing yes!!!
Also as so many users have requested we need the midi tracks to pass through AT, PB, BC and MW messages.

6 Likes

Iā€™m still hankering after some expo curves for those envelopes, especially the decay. All I really want, actually.

7 Likes

I would like to have two modulator envelope delays, one for each modulator A and B1/B2, similar to the filter envelope delay on the Digitakt.

isnā€™t this on the second page of Syn2?

3 Likes

Yes, this is already thereā€¦

1 Like

Sorry guys, I requested a feature already implemented.
I have to explore better before requesting.

1 Like