Importing Drum Samples - Sample Based Instruments via Pigments etc

Lab AstroLab
#1

Hi Everybody new to the Arturia Ecosystem and working with the AstroLab.
Been frustrating but getting close to being able to relax while exploring as I learn the ecosystem.

Does anybody know how or if possible to import Drum samples laid out through the keyboard. I know Arturia has “drum sounds” here and there but usually it’s just a one sound like a kick, mapped and stretched over the keyboard.

I did purchase Pigments and had red something about being able to import that way, but that be more for a sample based instrument?

Love to hear any ideas,
Marcus

#2

Hi

You can import up to 6 samples in Pigments sample engine and choose the Keyboard Map option to select separate key ranges for each sample. As there at two sample engines, you could have 12 samples but they would share keyboard ranges. Additionally one sample engine could use velocity mapping to only play those samples with a certain velocity range. There are a lot of options and I suggest seeking out a good video tutorial and experimenting. Good luck.

2 Likes
#3

Hi,
there are a few instruments in AstroLab that are able to import user samples:
CMI V, Emulator IIV, Pigments, Synclavier V and Vocoder V.
Each one has its own mapping features.

  • While Pigments can import multiple samples (up to 6 per Sample Engine), its key mapping is automatically assigned in octaves (however, instead of key mapping, Pigments can also rotate through the samples in round robin or ramdomly, or via a modulation source)
  • CMI V can use up to 10 samples per preset, freely assignable to key ranges (without crossfades), but no velocity zones (although it is possible to assign a velocity response to each sample)
  • Emulator IIV can use up to 8 samples per preset, freely assignable to key ranges, and velocity ranges, both with crossfades
  • Synclavier can use up to 12 samples per preset, freely assignable to key ranges OR to velocity ranges (OR selected via the Mod Wheel)
  • Vocoder V can use up to 12 samples per preset, either mapped automatically to one key each starting at C1, or cycling.

So, for drum kits, depending on the number of samples and whether velocity switching between samples is needed or not, I’d use Emulator II, CMI or Synclavier.

3 Likes
#4

Thanks I thought I had replied to this on my phone but looks like.

heres a great intro to the sampler video i found thanks Funt

#5

thanks Sean great Info.
Do you know.
If i buy one of these instruments during the sale, will my next V collection price reflect what I already have?
Just not ready to dive into the whole thing yet but some of these larger sample capabilities other than pigments might be a good place for me to start and purchase while still on sale!

#6

Sean I’ve tried uploading my edited User Sample from Pigments into Analog Lab V which works good. BUt then when importing it to Astrolab something seems to fail.
I heard from Simon that in the latest update this should have simplified things.
The loading bar says it’s transferring but I cannot find the preset on the search within Astrolab nor is it showing up in whatever BANK / Playlist I’ve exported it too…

Any suggestions?
Simon Said to make sure the APP was not simultaneously active which it is not.
thank you

#7

I’m having this exact same problem, and I’m up to date on firmware, etc. Created a new preset in CMI V (because I could assign the specific keys that I liked) but I can’t get it to show up on the Astrolab. Haven’t tried creating and moving something in Pigments but it sounds like I have the same problem. When I make an edit to an existing preset and “Save As” and then send that new one to the Astrolab, it works fine… but maybe something about using new/unfamiliar samples that aren’t in the main Arturia sample library is the issue?

#8

Once you’ve created a custom sample preset in Analog Lab (whether it’s was created with CMI V or with Pigments), you have to transfer that preset and its samples to AstroLab.
When AstroLab is linked to Analog Lab, if you simply select the preset in Analog Lab, it will load the samples in AstroLab only temporarily, while that preset is selected, but the samples are not yet stored in AstroLab’s storage.
You must use the “Add to AstroLab Library” option in Analog Lab to store that custom preset and its samples in AstroLab.
After that, you can add this custom preset to AstroLab PlayLists.

#9

Thanks for the quick reply! Unfortunately, I’ve been doing this. I’ve saved the preset in the instrument, then found it in Analog Lab. It comes up in Analog Lab, but when I select these new presets in Analog Lab it doesn’t also show up on the Astrolab display. (When I select other Analog Lab presets, they do show up… but when I move to these User presets, the Astrolab display just stays on the previously selected preset.)

When I click on “Add to AstroLab Library” in Analog Lab with one of these presets, it seems to indicate that it worked, but then when I go into the Library it’s not there.

My operating theory right now is that I need to move the samples themselves into some specific folder (I’ve just been loading them into the instrument from the “Downloads” folder or whatever). I do get a pop-up when I try to add to the library that says “AstroLab wants to access your Downloads folder” and I click on “Allow”, but maybe that isn’t working? Do you know what folder is the “right” folder for user samples?

#10

That is odd. I don’t have this issue here.
You mentioned that you are up-to-date on the AstroLab firmware (1.3.0?), but is your Analog Lab also up-to-date (currently 5.10.6.5147) as well?
Are you using Analog Lab in standalone mode, or as a plug-in in a DAW?

I guess that until the first issue above is solved, it’s not going to work correctly for the transfer.

I think that when you import a sample from your download folder in one of the “sampler” instruments (CMI V, Emu IIV, …) and you save the custom preset, that sample is automatically copied to a Samples folder in the Arturia Library/Program Data folders.
(it does on Windows, not sure on Mac)

A-ha! That might be the culprit. It sounds like a permissions issues. Not sure how to fix it. That would be a question for Tech Support.