Hey does it work the same way for digitakt? Where you can copy a pattern, load up a different project, and then paste it?
You can but the samples wont go with it, they will need putting in the same slots in the new project. It may be quicker to copy all the tracks to the sound bank, copy the pattern and reasign them once you paste in the new project rather than going through the sample list.
I never thought about this till the other day, but with the ol kit structure and 128 kits, 128 patternsā¦
By being able to load any of the 128 kits to each pattern yields:
possible combinations of kit/pattern variations per projectā¦ 
I agree with this.
The ability to copy a kit from one pattern to another would be great to have, and it would not disrupt those that want to keep it as-is.
For me I find that I fine tune sounds by using them in a composition which spans multiple patterns.
And yeah, I know I can use [TRK]+[REC] to copy a sound, and [TRK]+[STOP] to paste that sound to another track.
Without the ability to copy and paste the kit, itās a lot of steps to update patterns.
When you get 6+ patterns for a composition, itās gets crazy double checking every pattern to make sure all the sounds are right.
2 Likes
100% this for me. If the DT worked any other way regarding this it would mess me up so much. Iād rather develop patterns as I go and not have new tweaks I make effecting older patterns I was happy with.
Someone mentioned what if they wanted to change the kick for all patterns?
Just copy the damn kick part to all of the patterns you want. Itās really not a big deal. Itās actually even easier because you could copy just the kick if thatās all you wanted to change and not worry about messing other instruments up if you for instance opened a padās filter in a different pattern.
And rejoice in the ability to choose a different kick per pattern if you decide thatās what works. Very flexible. The method you guys want already exists. Copy those parts.
The want for kits to be locked across all patterns just for your slight convenience is ridiculous.
The want for a handy copy all parts at once separate from the trigs is totally a good idea Iām all for. 
2 Likes
Can we flag to keep this up? I still feel like there was some good conversation that could help others in the future.
Also sorry if I was a bit of a butt in my post right above this.
Iām all for requesting improvements to gear if they are needed and I donāt think the companies are infallible. The benefit of this specific workflow just happens to be right up my alley so I got too invested 
I noticed that that last block of posts was me replying to nobody as I saw the other user deleted their posts, so I just deleted mine too. It was sort of an off day for us and mostly needless back and forth, probably all the info has already been stated earlier in the threadā¦
Oooh I misunderstood and thought that message was regarding this entire post as a whole.
I get it now.
1 Like
Last night I copied 3 patterns with their kits to a new project, and wanted to share how I did it.
- Export each track sound to 8 available slots in order (I just use the default name for each)
- Copy the active pattern
- Switch projects (and save changes)
- Paste the pattern
- Set the sound of each track to the 8 you created in step 1
- Delete the 8 sounds from the +Drive (optional)
In the past when I did this, I jumped between the two projects 8 times (to paste each track sound).
When you set the sound on a track it adds the needed sample to that project.
Since each track has a copy of the sound, you can clear the ones in the +Drive if you want.
I wish there was something with less steps, but it was workable for me.
If anyone has something with less steps, please let me know.
Best regards,
Gino
2 Likes
Hi, sorry to revive an old discussion but it seems to be relevant to my questions.
Brand new Elektron user here - Iāve skimmed this thread but a lot of the talk comparing the Digiās system to the other boxesā has gone over my head, soā¦
Letās say I want to break into a section where I have a different bassline and groove. I copy into a new pattern & make the changes. No problem - until I want to āmixā the whole tune a bit; soften the attack on the kick, slightly pull a clap out of the reverb send, adjust the panning of a pad with LFO depth. Do I seriously have to copy and paste each and every change that I want made globally over to every other pattern manually?
Also - If I have a short pattern chain where I want to jam and gradually open the filter on a pad over the course of a few cycles - I canāt do that? The parameter values keep snapping back to where they left off in each pattern.
I get the benefit of having settings and sounds be independent for each pattern and with all the conditional and performance tools a ā4 barā pattern can develop and stay interesting for ages but Iām really hoping I can hold down a button combo for a āglobal/session per-track parameter change excluding p-locksā or something because switching between patterns to jam or chain arrangements on the fly while tweaking parameters is one of the main reasons I wanted to step away from a DAW - I didnāt for a second think a performance oriented sampler like the Digi would put be unable to do this and I definitely like to mix as I go when building the patterns too.
Iād be grateful if anyone would kindly shed light on a feature Iām missing or suggest a decent workaround. Many thanks in advance!
Since the Digitakt has no separate kit structure (like the A4/OT/AR) which could be shared between patterns, you are doomed to copy that stuff around.
Thanks for the reply!
Huh, I just read that I can instantly copy and paste all the parameter pages together so I donāt have to do them separately. Still kinda annoying that Iād have to do it per track per pattern after a little mix sesh but I suppose it would never be more than a minute of button bashing. Anyway, I suppose the independent per-pattern āmix sceneā thing by default could be thought of as a positive and flexible thing creatively. Iām not with the Digitakt now but Iām guessing pasting parameter pages across patterns leaves p-locks alone?
How about the issue with automating parameters between patterns - is there some kind of MIDI parameter sync trickery to get over that one?
I think you can also save your entire sound. Load it into the sound pool and access it from the other pattern. Remember that when you load a sound from the soundpool, it becomes a copy. So changes to existing sounds in the soundpool arenāt automatically ruining your other pattern.