[Feature Request] New Drum Machine

Software Instruments V Collection
,
#1

Hello

I created this topic some weeks before new forum was created, I copied my topic and want continue it in public discusion. You can add here another ideas if you like to add.

as I can’t find any forum for software (this is for V Collection only as I see) therefore I post it there.

My idea is for new drum machine software (vst and standalone) which will be similar to Pigments (in visual part especially for GUI).

  • It will have 16 or 32 pads for drum sounds, maybe make it modular like and user can decide how many drum pads need?
  • Each pad can hold several sound generators (some inherited from Pigments?)
    • sampler
    • FM
    • virtual analog
    • spectral
    • resynth (load samples as spectral / harmonics)
    • I can imagine to have some modules from Spark 2
    • those generators can by stacked, that means user can add multiple samplers in one pad or mix them all togheter (3x samples 1x FM 4x VA in one pad)
  • Each sound generator will have
    • filter section (minimum two selectable filters, maybe it can aslo be inherited from Pigments?)
    • ADSR (for each generator, that means if pad will have 4x sampler, each sampler will have own ADSR) with option to edit ADSR for all generators in pad.
      and last FX section for pad
    • Additional ADSR and MSEGs for control pitch, amp / volume, etc…
  • Sequencer, it is not necessary for me, maybe in first release it doesn’t have to be, but I can imagine that someone will appreciate it. Also if there will be some, I would like it to have also some automation for internal fx for pad (if pad will have some FX inside)
  • Slice mode - it load sample and turn each slice into pad (with sliced sample in sampler generator) and aslo generate a correct time sequence in sequencer (if there will be). Then each slice (pad) can be edited to own wish. For example change some pad from sample into another generator.
  • And last include good samples, maybe from Spark?

This is only general idea, I can imagine more details but I think for start it is enough. Also if someone have another ideas, feel free post some here.

2 Likes
#2

+1

@Arturia: Is there news regarding a drum machine or at least a VST?

1 Like
#3

Hi @Obelix and thanks again for all your feedback :metal:

Thanks for sharing your ideas to improve our Software instruments.

We will mark this topic as a feature request to let our team know about it. Let’s see what they are preparing for the future and hopefully they will make your dreams come true!

Best :zap:

1 Like
#4

Why don¡t use Spark 2? It is an amazing product which lacks some love, like a resizable GUI. Only for Spark 3 I will update to Arturia collection.

2 Likes
#5

Because of non existing resizable GUI. It is hard working on 4k monitor without resizable GUI.

Btw. those ideas for new drum machine is not strickly for new product, it can be aplied for Spark 3 (for example). But for the completly user interface change (similar to Pigments) I suggest it as new product.

1 Like
#6

Hi @silikonanswer and welcome to our Sound Explorers community!

Please make sure to subscribe to our Newsletter to be the first to know about any updates or other exciting news from Arturia.

1 Like
#7

But maybe it’s easier to use the code of Spark 2. It has many features. It just needs some cosmetic changes. I don’t know what it’s easier. I would love the es product will have at least all the Spark 2 features. I think the V Collection needs a drum synth/sample. I will upgrade to the next V Collection only if a drum synth is added. I am more than happy with what offers now synth wise.

#8

I agree silikonanswer, it is underrated.
I spent some time programming the modular with good results, imo.

Maybe more compatibility with Bst in Prefs. My Spark controler died a few weeks before the one year garantee. Since it is not in production anymore, Arturia gave me a rebate on the BstPro. Despite being more powerful, I sometimes miss the old Spark controller.

#9

It is hard to say if it is easier. Sometimes it is better start write new code. Of course, the sound engine can be reused. Everything depends how it is written.