Can also start a blank project, setup and assign a few patterns/chains/blank kits then save the project and lock it, and have a template project ready to rock with your most common workflow.
5 Likes
XponentOne, Iād never thought of that. I think itās a very cool idea!
I want to start to manage my extensive library of sounds in my AK, and go thru factory sounds and sound packs. Delete some, edit some, rename, relocate sounds.
If i go thru kits, and their 4 sounds, double clicking on the track will display the sound, now if i want to see where on the +drive it is located or if after editing it i want to replace that sound, how to do this? I know how to save it in a new place, but not where it was originally.
Thanks for your help
double clicking a track will bring up the sound browser, this can be focussed on either the sound pool (per project, 128 sounds) or +Drive (per machine, thousands of sounds) - whilst focussed on the browser you can audition sounds for that track, pressing yes will load them in
clicking a track will only reveal the name now assigned to that sound stored entirely within the kit, this is a legacy of earlier activity only, that sound is not stored anywhere, it is baked entirely within the kit (although its source may well have been a +Drive sound originally)
If you want to swap out a sound within a kit, just tweak and save or load from the sound manager and save into the kit
sounds like you may benefit from a refresh read on some ideas about sounds, kits, patterns etc from the manual or read the advice in the many threads on this topic 
:
3 Likes
great thanks. i didnāt realise that the sounds stored in a kit are a separate entity and can be different than the sound they might originate from in the +drive. Is there a way to name them differently? or they will have the name of the sound loaded from pool or +drive regardless if it has been edited in the kit?
Also, how do you move a sound from one slot to another in the +drive? is it thru sound manager? I think i know how to do it in OB, but working just with the synth at the mo, and wanting to get more familiar with it without using OB.
thanks
oh yeah just found reply to my first question. Sound manager: rename to rename the sound on +drive, rename track sound to rename the sound in the kit. nice
Is there another synth out with such complex data architecture? 
I like it however.
Yes the OT, where as the A4 I find easy, the OT just bogs me down in āhouse keepingā
1 Like
I see your first question was answeredā¦ But did you ever decide to set about cataloging your +Drive library with that knowledge?
I also would like to create a more organized +Drive with different Init patches and more categorized sections of sounds that I would like handy (in place of the preset list available now)
Seems like a healthy workflow improvement .
So I figured out an interesting thing this evening in learning how to use song mode, kits, and pattern chaining on my Analog 4 MK2. You need to create and save each kit before switching patterns to use new set of sounds per track or you will copy over the same sounds from other banks! Been loving creating kits, songs and chaining them together to create longer compositions. That and learning how to craft tunes on the Octatrack with parts, patterns and the arranger is soo much fun.
Upā¦
So did i understand the Connections right?
+Drive -> global
128 Soundpool -> per Project
1 Kit -> per n-Pattern
n Kits -> per 1 soundpool
8 banks x 16 pattern -> per project
Performance controls -> per Kit?
2 Likes
I am starting to think I might be going about this wrong.
I want to put together a composition so I do it this way
Create New Project
Track one make a sound and save the sound, track 2 , 3 4 FX etc
as I am doing experimental music I usually just use A1 pattern
When I am happy with what I have created I save the project
But now I have a second A4 I am able to move all sounds etc across except the projectsā¦
I think I should start saving my compositions as Kits correct?
Iām about to get an A4, so Iām very curious myself to see what tips folks have!
Sorry, but whatās your real question? I mean what do you want to accomplish?
Isnāt the essence of it (how to transfer stuff between two units) already answered in your previous post?
Nevertheless:
IMHO it seems to me you are a little bit confused about whatās stored where. So Iāll try to clarify it.
In regards to a single pattern itās more important to save the (automatically assigned) kit, because thatās where the sounds of all 4 tracks used in the pattern are really stored. So even without you knowing you are actually using a kit.
Saving a sound means āexportingā that sound from the kit to its own file.
Saving a sound separately is only necessary if you want to re-use a single sound somewhere else (for example: in another kit/project/whatever) OR if you want to preserve the actual settings of a single sound as backup.
Please read the first pages of the manual again (+ section āKits and Soundā) for more details about whatās stored in the different structures (Project/Kit/Sound/Pattern).
1 Like
If I understand you correctly, you would like to transfer a āsoundā, which is the patch of one synth voice, from one machine to an other.
There is a feature you could use: āGLOBAL MENU/SYSEX DUMPā
This allows to send whole projects, kits, single sounds etc. out to the midi world. You have only to configure your midi-setup with the two machines and send/receive what you need.
I would recommend to read the manual from page 59 on, to get the idea (I am on OS 1.22).
1 Like
Goodmorning,
Iāve been working with all kinds of devices the last 15 years. Now with my first elektron machine itās sometimes a bit confusing how stuff works. One of the things iām running into is the connection between patterns and kits.
With many of my āoldā devices, choices of sounds and parameters are stored within the pattern. With the A4 this is different. For every pattern you choose a kit (or create one) and save this with the pattern.
Iāve created about 10 pattern now and somehow i end up creating a dedicated kit for every one of them. This way i will probably end up having 128 patterns with 128 kits.
What is the use/advantage of having kits and patterns not āconnectedā as 1 save?
1 Like
The current design lets you reuse and assign kits to as many patterns as you want. But it also lets you have patterns with different kits.
If every pattern has different sounds for you (and thus its own kit), it sounds like overkill. But for me, kits become awesome once you use song mode: if you have various patterns that evolve your track, youāll likely reuse sounds a lot.
Having multiple patterns associated to the same kit makes sure that if I change/tweak the sound within a kit, it stays correct in all the patterns that use that kit.
2 Likes
There was Tabula Rasa project made by @void for that purpose, IIRC. I already asked where to download it, but anyway Iāll end up with making mine, with my default settings.
I have problem with my A4 mk2. Running latest beta. When I create new project, all the preset kit is gone. And I cant use kit sound on parameter lock. It appears empty. Any idea how to fix this?
This is normal, you should create a copy of a project that you like and delete all the patterns instead, this way the kits will be there.
1 Like