One thing I have in mind… You can save the sounds you make to +Drive, let’s say I create a kick with a sample layer, and save to +Drive as “XXXKICK”, then I load another project with different samples in sample slots and … I can’t load that same “XXXKICK” anymore because that sample is not in the sample pool of that project, and only load the synth engine parameters… so I think save sounds in +Drive is a bit useless through different projects. I don’t know if is too hard to get samples playing from +Drive directly, but would be the perfect workflow for a machine like this, because when you have a lot of sounds with samples as part of the sound already saved in +Drive, the machine starts to be a bit chaos, because you can’t load that saved sounds like you really save them
Right from day one I’ve been figuring keeping track of kits/samples/sounds is going to be a bit of a pain. Not as intuitive as a DAW with presets and a harddrive to load stuff from (for me, at least).
What I’m doing is copying a project then replacing just a few samples of the 127 samples with new samples so in effect I’m sort of planning each project to represent just one song with whatever unique samples that song requires - if I have a killer vocal sample I want to use in a song then that can go into one project.
So far, as I’m learning the Rytm , I’ve only created 3 projects with each one containing mostly the same samples.
On the plus side, even with the stock preset samples that come with AR you can get a huge variety of interesting sounds.
Hi guys. I have been worried about this very same issue, as I use the sample options heavily.
I dissevered something today that may be helpful.
When you load a sound from the +drive to a new project, it actually copies the associated sample into the current project (into the first available sample slot) and relinks it automatically. So as long as you have available sample slots in the project, it appears that you can just import the sounds.
One confusing note: When “auditioning” sounds that you may want to import from the +drive, you can’t hear the samples along with the synth engine. But once you select the sound, it loads it correctly as Ive described above.
Any one else have any input about this? I really desperately want future updates to address the sample aspects of RYTM.
Blake
Thanks for this Blake. Didn’t notice it before, at least is a useful tip for load used sampled easily.
I NEED an update relating samples also! The lack of preview +drive samples is a huge pain in the workflow
Does this mean that the sample “must” stay in its respective folder on the +drive when you save the sound in order for the sound to be recalled accurately?