Hi I ran into problem with copying whole tracks across projects. I can copy the trig sequence with sample locks and even the parameters so everything should be fine and the track the same. But the trigs with locks won’t play and when checking what sample they are playing there is nothing, it shows just —. So I could go over it and manually assign new samples but there has to be something I’m missing. How would you go about this?
Also it seems sometimes that the same thing happens when saving a project and trying to play it after turning the device back again next time I work on it.
Thx for help
I think you first have to create the same sample pool in the same order as your other project / track because it’s looking to assign the missing samples from there, otherwise there’s nothing for it to attach itself to.
I might be wrong so hopefully someone can confirm, but I seem to remember that this is the reason why you get nothing on locked trigs after copying tracks across projects.
Upon investigation it looks like you have a locks folder and not a sound pool so I’m not sure that it works the same as it does on digi devices, I guess we’ll have to wait for some kind model samples expert @Leonsarmiento @bibenu to stop by and give us an answer.
Not sure about that, maybe I’m not understanding.
1 Like
Oh that would make sense. So there is a way to make the sample pool so that it would assign samples to the locks before pasting the actual sequence? I don’t know how but one not very elegant way could be that if I use locks on other tracks so that lock on the original track would be assigned the sample with the same lock number but it could be a different sample?
I know it works like that on some other elektron boxes, I wasn’t aware the data tree on model samples was different in that regard. I would imagine if it’s going to work, that it will be similar but hopefully one of the people I tagged (or someone else) will clarify because I didn’t see any clear information about it when I searched for an answer.
Not sure I can help directly. (I really didn’t get on well with using sound locks to get round the limitations of 6 tracks).
But some thoughts anyway … they might turn out to be part of a solution.
I experimented with working with a kind of ‘sample pool’ that I read about on the digi boxes. What I did was to use patterns A01-A04 to load up the sounds I planned to use in a project without actually putting sequences on those patterns, just loading samples. Then for the actual patterns with sequences, I would choose samples from those 24 in RAM.
There are quirks to working this way. For instance, if you try to do this without pre-loading A01-A04, then you may hit some random results … I suspect the RAM is numbered dynamically or something … so if you were to change the samples already in RAM (in my case by changing a sample in A01-A04) then it all got messed up. So long as I left A01-A04 untouched, it all worked.
You might also experiment with exporting the pattern as a sysex ( Config → backup ). I can’t remember if the exported sysex contains the sounds or not, sorry.
1 Like
That’s weird, you should not be losing sample locks… unless you accidentally remove them from Ram or delete them from the Drive.
Basic question, are you using the latest firmware update?
Indeed there are some limits due to the structure of the M:S. You have locks folder and Ram folder. Ram max is 64mb per project and locks folder is 20 something per pattern.
You might be unintentionally replacing samples from the Ram to free space for new sample locks in the current pattern. That will make previous locked samples in other patterns disappear since they are unloaded from Ram.
If you plock a lot in your patterns you will hit these limits easily. If you can chain your samples, using Digichain for example, you can override the 20 something sample locks limit and have hundreds of samples for massive locking.
1 Like