Hi. The Syntakt is almost new to me. Is it possible to copy banks to another project to reorganize my Liveset. How is your workflow? Thanks.
1 Like
Yes you can do that. I use one project to create lots of different patterns, jams etc. then if I want to create a song with one of those patterns I copy it to a new project.
1 Like
As far as I know it is not possible to copy-paste entire banks to another project. You can copy-paste patterns though.
I structure my patterns as follows for live sets: 1 project where I create all of my patterns. I use 2 patterns for each track (e.g. A01, A02), so I can create 8 tracks per bank or 64 tracks in one project which is plenty. I structure banks according to energy level (e.g. A = ambient / intro, B = percussive/warm-up, etc). The second pattern is used as fallback version of the pattern I’m working on. So let’s say I’m working on pattern C05, I’ll often copy-paste that pattern to C06 as a backup. On this backup version I will also use pattern mutes to create an “initial state” of the track. So when I bring in the track during a live set, only some elements are active and I can un-mute the rest later.
Side note: You can copy-paste a lot of things on the syntakt: Track sound, trig sequence, LFO parameters, etc. This really speeds up your workflow 
5 Likes
Imagine a (PC/Mac) companion app that allowed you to pick Songs from various projects and build that into a new combined project in prep for a live set where it automatically copied over all the relevant Patterns used in each song and placed them sequentially from A1 to H16. That would be sweet.
7 Likes
That would be sweet indeed! Referring to the recent Elektron survey: It would also be dreamy to have software versions of the syntakt, digitone, etc so that you can tweak the projects in your DAW and then sync it back to the device. That way you can work on your tracks at any time 
(though not sure if that’s a good thing ;-))
2 Likes
I recently consolidated some favorites from across a few projects … and the tedium of copying patterns and switching projects 2 dozen times made me revise my workflow.
I think everyone does something different, but now when a project fills up, I make a copy of it, and in that copy I cluster my favorite material in the later banks, and erase any drafts, and then have banks a-e or so to work with, just because moving patterns within a project is so much easier.
Then for creating a longer set, either selecting patterns to put in the early banks of another new copy, or song mode, which can be a useful way to get away from remembering, swapping between, or reordering patterns within a project…
I too would love to have file-level control of patterns in the same way sounds work in Transfer…
4 Likes
Nothing is on the way to transfer directly an entire bank ?
What would be the technical issues for Elektron to implement that possibility ?
When you use 16 patterns in each bank to make a full song, having an easy switching possibility to an other project would be a must have.
1 Like
We really need something for this. I’m doing a new live set soon and I’m dreading the prospect of the hours I will have to spend endlessly iterating load project, copy pattern, load project, paste pattern, load project, copy pattern, … Hours because all the material is scattered across several workspace projects, and I’ll have to be constantly cross-referencing my notes to not make a hash of it.
I had this very same problem when trying to use DN for a live set. Loved the stuff I was making with it but it was scattered across several projects with no easy way to combine into one. Ultimately this made the DN much less useful for me and I moved it along (for other reasons too).
But I really believe that an Elk Herd-like software solution is needed for both DN and ST as well. Otherwise it feels like the potential of these boxes, especially in a long, continuous playing environment like a live show, is brutally diminished.
I would love to see this change in the future and it would make me reconsider several of the Elektron boxes tbh.
3 Likes
+1, I’m also looking for a pattern management solution besides manually moving patterns on the device.
I have a hunch that it should be possible to edit the MIDI SysEx dump, but from what I can tell, it’s not exactly easy.
At some point, I’ll bet a tool like elk-herd or elektroid will support Syntakt on my OS (mac) and maybe that will make it easier.
1 Like
I’m interested in this, too, and I did a little work with Nymphes SysEx and found it pretty tedious but workable for moving things around. I kept wondering then if anyone had ever made a tool to make decoding sysex a little easier, but didn’t find anything.
2 Likes
I’ve started another thread to discuss possible solutions to pattern management, if you have any notes on the subject, please add them there!
1 Like
For this thread and any future intrepid SysEx sleuths:
I’ve had a quick look at the SysEx coming out of Syntakt, and alas I’m unable to confidently discern even the highest-level structure. There are 153 discrete SysEx messages (F0 … F7), of which 128 are definitely the patterns in number order (with a post-machine ID header of 50 01 01 00-7F), and then 24 similar short messages with a header of 53 (where the 50 is), and one denser one with a 54 in the header. (The pattern ones match what you get when you send an individual pattern.)
The group of 24 is kind of a head-scratcher to me, I was expecting 16 songs … . I assume the last one is global settings and sound pool references. For comparison, a DT Sysex, also current OS, had 128 patterns plus 1 longer settings Sysex, which I suppose holds the samples list. Anyway, the inside of the Sysex is fairly opaque to me, clearly several sections and formats but I’m missing a few steps in order to make heads or tails of any of it. If I were able to read the pattern name, a pattern-moving webmidi program might be feasible, but otherwise I’m going back to crafting the perfect bucket-brigade delay sound on ST…
1 Like