Honestly I think more voices if I had to choose. More tracks would bump up against the voice limitations faster.
1 Like
More tracks would only mean more people would complain about the lack of voices.
1 Like
A simplified 2 operator engine that has double the voice count has been discuised in the âshould digitone expect its own machinesâ topic. Along with some sort of drum mode where you load presets onto keys (which would be more or less user friendly/fast version of multimap)
Both are great ideas and might be plausable because they dont require more compute power.
Ive been experimenting with 2op sound design lately, and there is a surprising amount of variety of what you can do due to different routings (lines, dotted or otherwise) and operator linkages (Things you can do with A â C are different from what you can get out of B2 â B1, or even A â B1), and ofcourse - the feedback position.
Id imagine that âsimplifiedâ doesnt exclusively mean 1 operator + 1 carrier limit. In order to make it same compute weigth, there will probably be only 1 lfo and 1 filter (i would probably keep base-width if i had to choose one to keep)
Regarding tracks. If previously mentioned drum mode can be a thing, and has per sound mute ability, it would be just wonderful, and will eliminate the âall my percussives are squeezed into one track and its cumbersomeâ issue, at least for me. I would probably not use it as much for performance, but for arranging. Would be great to be able to copy a pattern and mute some sounds, instead of going through trig+yes to see which ones you want to remove.
you can read more about it here:
6 Likes
Unless itâs already possible and i just canât find it (likelyâŚ), iâd like the ability to lock the pitches per operator so they donât key-track.
1 Like
Throwing in for a Strum/trill feature.
It could be built into the current arpeggiator. Where the arp cycles through notes, a strum mode would do the same but hold the note played after one cycle, for the duration of the note length.
Arp mode is Strum up/Strum down/Strum true?
Arp speed becomes the speed that the strum is played, this could be as fine as 128th note resolution.
Range would be like doing a piano slide up to the desired note, so setting the range +2 means you intend to strum a chord 2 octaves higher than the one thatâs entered.
Hi there Elekton ppl and Elektronauts,
I thought it would be nice to drop another silly request
(since youâve been listening quite often 
and in some way or another even incorporated some of them, more than once even, tx!)
AnyhowâŚhere it is:
Since DigiTone is behind on additional nice stuff, with their brothers and sisters getting all the love and attention (Elektron wizards probably hard at work behind the scenes in the Elektron laboratory to fix the issue as I type this crap)
Additional Midi controllers for the 4 midi channels
(more than the 8 assignable midi cc slots at hand + LFOâs/LFO types)
- Randomization and a Randomization Menu
Where one can set the target range to be randomised by the percentage/value of chance, also entered. Presented as a list of tick boxes displaying which parameters to affect or not/skip
And while youâre at itâŚ
A batch parameter change DUMP or something that makes the ears ring
Maybe you could make a midi parameter batch Bank, like the sound pool instruments? This way you can stress out your external hardware to go into âbrick modeâ by subtly overloading it with a quick bulk send of midi parameter changes
In essence, like a stored preset bank (like instruments) for external hardware.
(Also serving people that have midi controllable HW without the ability to store their presets in a good way)
So this way, you can use the âswedish sequencingâ on your preferred audio sandwiches, use external hardware synth/module/DAW plugin/whatever tickles your fancy⌠and program it like itâs an Elektron using TRiG locks
So to recap:
1 - more midi parameter slots (making it a nice additional midi controller per Track - nice for usage in eg Live set and switching between hardware)
2- External (midi parameter) Soundpool/soundbank (Electron style sequencing of external HW)
3 Bonus - TURBO MiDi THRU Since the digital boxes are in essence equipped with Turbo midi, it would be nice to have it pass MiDi over USB out to external hardware without chopping off arms and legs, skinning the bare bones clean, but with all bells and whistles please?..
or, manufacture some updated version of the TM boxes?
Cheers guys !!!
Also like I mentioned in the recent Electron LIVE performance with the AH+
Maybe you could make the AH+ be able to load a small custom sound pool of samples (a skinned down version of a DigiTakt sample engine/wavetable-like)
additional AH+ TEXTURE LAYERiNG
Somewhat reminiscent of the âDevious Machinesâ texture plugin?..
So you can eg: set the range of when a sample kicks in/trigger crossover points
or make other frequency ranges, LFOâs, Gate or velocity/volume open the triggerGate
Wet/Dry level to blend and mix in the sample/loop with the Live Audio feed.
For instance having some additional noise/harmonics to bring out some extra dirt/grittyness when applying additional distortion/overdrive further down the signal chain
? GLiTCH repeated artifacts as the mixed TEXTURE LAYER tops ? + within the desired bandpass frequency range of course. ? Or granular glitchyness, also nice ?
? Use the TEXTURE LAYER as a send for NY Parallel stuff ?
? Maybe have an arpeggio/chopper Gate Module on/off sequence that triggers the sample/texture, that with the synced/slave midiclock could make a rhythmical texture pattern on top??? It could also be a SC filter, whateverâŚ
? Controlled Feedback loop/Ring Mod Module ?
Another random brainfart:
SPLiT STEREO iNPUT MODE
(like you can do with the audio input on the DN)
To process Left and Right channels individually of each other ?
eg to have some nice additional movement by the natural phasing effects when summing? Or crazy panning???
Maybe you can also set it up as a SPLiT SiGNAL Module or CHAiN SPLiT in-between the modules in the chain, and then build/modulate/mangle the split signals onwards from that point? And then have a MERGE SiGNAL as well to glue it back together just before the master bus hits it? I dunno, just some ideasâŚ
Okay, okay Iâll stop my nonsense (for now, but Iâll be back with more - just because my lack of having a social life)
Anyhow pls give the DigiTone some love, thanks!
Just MORE MiDi SLOTS the MiDi PRESET POOL (for batch midi parameter TRiG printing) would be feckinâ awesome, and you can forget about the rest of all the stuff/silly requests mentioned above
(and the parameter randomize menu would be also reckonâ awesome, as a nice bonus to randomize external hardware, right before saving it to the MiDi PRESET POOL)
Cheers all 
EDIT: revised mockups with two alts. V1 has some adjustments, V2 has two destinations instead of 4, and uses the two knobs in between to select dividers/multipliers instead.
I always end up wanting more LFOs, specially since FM synthesis can get so much interesting with very subtle movements⌠considering how unlikely it is that we will get more of them, I thought of this alternative: a mod page where you could assign the LFOs we already have to other destinations - using the push action from the encoders to cycle through multipliers or subdivisions.
Right after mocking it I realize they probably wouldnât go with something like this since:
- It buries modulations sources way too deep into menu diving, probably a cause for confusion.
- Theyâve never added that kind of push action on those menus (v1). TBH I would be more than happy to have something like this even without divider/multipliers - just more destinations for the same LFOsâŚ
8 Likes
I might be crazy but this is how the Digitone already records right? Notes replace each other. Thatâs what I find slightly annoying, you canât build on a sequence by adding layers like on the 707 for instance. Example: On the Digitone when I play 16 steps of a root note and I want to add a fifth on the 1 and 12 or something, I have to physically play the root and fifth together on those steps, instead of layering the fifth and adding to the sequence.
edit: I just checked, and itâs actually bit of both. Notes do get replaced by newly played ones (so no layering) but it doesnât wipe the sequence so if youâre just jamming and trying things out youâll end up with constant barrage of 16ths at the end. 
2 Likes
@Oxenholme they do, yes, which i love. but what im trying to say, i didnt explain properly. its called âTime Warpâ on the toraiz Squid, i believe++
from Sound On Sound:
While Iâve got a few niggles with the basics of sequence creation on the Squid, thereâs one feature that is brilliant. Despite the name, Time Warp isnât a function for changing timing of sequences â the Squid has a bunch of other mental features for that, which Iâve described elsewhere. No, Time Warp is a way to capture events that happened while you werenât recording. Weâve seen this idea in DAWs before but this is the first time Iâve found it implemented in such a usable way.
During playback, the Squid generates a rolling buffer of up to 16 bars, capturing what you do in the background. If you hit the Time Warp button the pads switch to a view that represents the bars currently in the buffer. Tapping a pad will begin preview from that position. The main encoder sets preview length from one to four bars. Previews launch in time, just like a regular pattern. Switching to Pattern view and tapping an empty slot will save the current preview.
Time Warp works really well, letting you jam away then jump back and grab things that are working. I used it in a similar way to how I record in Live: recording a part a few times over, then finding a section I didnât fluff, or capturing a few variations as separate patterns.
1 Like
Ah like capture in Live. Yeah that should be implemented on everything that ever existed. Itâs brilliant.
I still wouldnât mind an overdub mode though, but a quick search on this site shows Iâm not alone in that 
1 Like
Yes, capture. Forgot what it was called elsewhere.
Iâd like an overdub mode too I think but itâs actually works pretty well the way it is. I donât find it too difficult to play over recorded midi intentionally without wiping out too much, depending on your timing I guess. You can sort of like purposefully overwrite the ones you want to replace in real time
1 Like
Itâs definitely fine for what it is but I tend to develop sequences differently because of it. More use of trig conditions and locks for variation instead of melodic layering which I would do with an overdub enabled sequencer.
1 Like
Having the DN sequencer output its midi would change my life. My particular workflow is to develop patterns strictly on the hardware instruments themselves and then record all the midi and audio to my DAW for arranging and mangling. I can record my encoder movements to their individual automation lanes with no trouble. Iâd love to be able to record the note data with the same ease. Ideally this would be a global or project-level setting and not per pattern as it is on the M:C, A4, and AR. Currently itâs doable, but with some tedious workarounds that I could live without.
Iâd really like a base width filter on the inputs!
10 Likes
Sermslikeyouwant an euclidean sequencer to be added to the DN. I would love it 
3 Likes
This! And on Digitakt too.
1 Like
Electron If you donât have intention of implementing retrigger for their synths, add ratchet and burst as one of the probability choices.
Their sequencers seriously need update. Suggestion, Logic gates, Euclid, and modulation of tempo and steps by LFO
No more LFO then please allow us to set mod wheel and breath controller as destinations. And a sequencer as mod source and destination.
Necessary from the first OS, fixed ratio, random arpeggiator, parameter slide
7 Likes
⢠Physical modelling synthesis (love textured, metallic, glassy, resonating sounds) !
⢠Comb Filter
⢠Layering samples
⢠Morphing capabilities
7 Likes
Overdub would be nice.
3 Likes
I wish it was possible to disable âSend to Mainâ for the Inputs (Dual, L, R). Currently the Signal is needlessly doubled when using Overbridge. You get the dry Input via the Input Channel and you get the mixed dry + wet via the Main. Imho, it would be much better if it was possible to only get the wet Signal (Chorus, Delay, Reverb) via the Main, since you already get the dry Signal from the individual Channels.
Alternatively (or maybe in addition) it would also be useful to be able to send the Input signal to the FX without turning up the Inputs Level (on the Ext-Mixer Page).
1 Like