Drum machine

Friends, you must admit that the lack of a drum machine in processors of the highest price category is one of the worst practices of today. The manufacturer, as it were, implies that the owner of such a device is already super professional and does not need to train a sense of rhythm, or uses a DAW or a slave-drummer for this. But this is not so, even pros sometimes just want to sit on a sofa in their penthouse to put on their headphones and play under four simple strokes before the concert. And since it is stated that QuadCortex is the most powerful device on the planet and it is from the future, then the drum machine in it must correspond to this level! I took the liberty of describing what it should be :relaxed:
Let’s get started!
Of course, this should not be just a set of a dozen different rhythms. Thanks to the touch screen, it can be a full-fledged sampler with a sequencer. Drum sample libraries can weigh quite a bit, a library of 12 samples will take ~ 1.5 Mb in wav format and ~ 150 kb in ogg or mp3. So can easily embed 2-3 libraries, as well as allow users to download several of their own. Given the ability to process the sound of drums with a reverb and equalizer, we can achieve a very wide range of sounds. This is what the main screen of our drum machine should look like:

Everything is pretty standard here, I will only describe the purpose of some buttons and interface elements. The largest window is the sequencer itself, in it we mark which instrument should sound at which moment of the measure, the red dots are the running light that marks the current time fragment during playback. The list of our instruments on the left is the sound of the drums. The “Kit” button is used to select a sample library.
And finally, on top the panel with several control buttons, now more about them:

  • Load - allows you to load a MIDI file from the device’s memory
  • Save - allows you to save a MIDI file
    You can create files with drum parts on a computer, this will allow you to rehearse in the absence of a drummer.
  • The following two buttons (“ 4 ” and “ b/4 ”) allow you to specify how many beats contains a bar and how to split each beat. The sequencer layout is based on these settings.
  • The yellow button “ 120 ” is tap-tempo, the current rhythm is indicated on the button, and if you hold it, a panel will appear on which you can set the rhythm with the slider and +/- buttons

  • The Play and Stop buttons speak for themselves.
  • The purpple button “ bar ” depending on the selected mode, displays the text “ bar ”, “ bars ” or “ Song ”. Tap opens a panel with some playback settings.
    • Countdown - adds a zero bar to prepare. Of course, you can add a countdown to the MIDI file, but it spoils the mathematical beauty and order, I don’t like when the verse ends with, for example, 33 bar and not 32. Or the whole song has 129 bars, not 128.
    • Repeat - serves to loop the drum part.
    • The second row of buttons allows you to set the playback of one bar, the whole song or part of it using the sliders and buttons below. This is useful for practicing a specific piece of a song, such as a verse.

  • Next are the buttons for moving through the bars one at a time, the central button contains the number of the current bar, when you click on it, a panel appears allowing you to immediately move to the desired bar.
  • Edit , a cool button, it contains a panel that controls the clipboard and a command to clear the current bar from all notes. The clipboard can greatly simplify the creation of long batches of drums. It contains several cells at once, you can tell it, for example, to remember bar 1, bar 9, and then insert them as necessary. In this screenshot, we see that 2 cells are ready for insertion, and 4 are empty, you can remember something in them

Pay attention to the part of the HiHat, you may notice that some notes are a little darker. Thus, the volume is marked, this allows you to Indicates accents and beats. To edit the volume of each note, you just need to click on the instrument of interest, the sequencer will take on this form:

Here, in addition to the volume of each note, we can adjust the overall volume of the instrument, its panorama and the send level to the effect chain.

  • “Settings” button, opens this panel:

Here we again see the ability to customize individual volume, panorama and send to the chain of effects, but for all instruments at once in a convenient table. The inconspicuous chain icon, to the right of the inscriptions vol, pan, fx is used to link all the faders, to simultaneously change. On the right we see the effects themselves - a reverb and an equalizer. And a few more buttons at the very top.

  • The first allows you to specify which MIDI-channel will be on, this will allow you to control it from the outside or vice versa, use it to control other devices.
  • The second button is the drunk drummer mode :slight_smile: Allows you to set some random quantization, making the drum machine more lively, contains 4 modes - off , light , medium , hard . Generally a pretty good feature, it really enlivens the drums.
  • Inverted . As you noticed in this sequencer, the “Kick” is located on top. Usually in different DAWs it looks the other way around, a note C1 corresponds to the “Kick”, and it is located below. I don’t really like it, let there be a button for inverting the view.
  • And the last button indicates instructs the drum machine to use global settings or different for each preset.

And finally, a small nuance of the sample library. Since the drum machine allows users to load their libraries, you cannot hard-code the names of instruments. It is necessary to agree on the name of the samples and take the names from them. For example, like this:
01.Kick.wav
02.Snare.wav
03.HHopen.wav
etc.
The numbers and the file extension should be discarded, and take the middle part as a name. And please do not start numbering at 00, most people are not programmers and are used to counting objects from the number 1 :slight_smile:
I hope this impresses you, I killed a couple of evenings to develop this concept =)

Their Hero statement:

“Quad Cortex. The most powerful floor modeler on the planet.”

I can see the benefits to a few simple beats w/tempo control and a basic click track… but I don’t think NDSP intends this to be a fully equipped DAW.

No need to make it this complicated. I get a drum machine if I need that, but simple drum patters and metronome would be good for headphone practice. I use a Zoom b1 four for remote practice and that I more than enough (approx 20 simple patterns including metronome in 4/4,3/4, 5/4 and strait clic) possibility to set tempo and volume is enough.

6 Likes

Wow, what a great feature request and effort! This would be the deluxe version of a drum machine but I also would be happy with a simpler version of this.

4 Likes

This sir much like your last post is so very high grade trolling. My hat is off to you my friend. Truly.

3 Likes

I would appreciate such a feature. But a more simple approach would be fine too.

For this task, patch a smartphone in to
do that. Don’t waste QC resources on something like this.

Dont think a simple drum pattern would waste much resources… and I would prefer built in solution.

Want my Smartphone far away from my music corner to not check WhatsApp or Facebook all the time but just make music.

It takes processing power to do any of that. It takes storage to hold the files. You would really stop playing to check a message??

GarageBand on my phone does this amazingly, and it’s free. Don’t put development time into this, I want my plugins on the QC!!!

1 Like

Agreed it would a waste of resources of many different things. I understand the practice aspect. But you can get that on any smartphone, patch in with a cord off a phone anytime & done.

1 Like

Music is quality time… dont want to use my phone for any task there.

You can track CPU usage any time… no need to leave resources unused.

cool idea but i can think of about 100 features that are needed before this is considered.

Yeah I have to say that I personally think this is way too left of centre to take precedence over any feature related to improving sound and usability in regards to guitar/bass.

Something like this would be nice to build in to the QC:

But of course, there are other more important features to dev first… no doubt about that.

Well I don’t want to waste storage space on the unit with drum tracks. Give me that space for more captures, effects, IR’s etc.

I understand the goal here, but… its a floor modeler, not a DAW.
This is waaay overkill…

Just gimme a few beats and I’ll be happy.

It’s a great idea; but we have 4 analogue inputs.
We can easily get an external drum machine.

I’d rather that the Dev Team focus on lower hanging fruit that help improve my guitar tone

Don´t understand what more tone you want… this thing is incredibly good but has lack of looper and a few drum loops to adjust.

I totally agree, that a complete drum computer is overkill… but no drums is also not very convenient.

As March says… a few beats would be enought … if you can trigger fillers and so… would be very nice like the link I posted.

Also there is no lack of space on the device. How many IRs and Amps you are going to store? My experience is, that you are good with 2-3 Amps and 4-5 Effects… the QC can store 100ed … more than you ever will need.

But I will wait and see what Neural delivers with the next FW.

Agree that a simple drum machine would be nice - and 100% agreed on a loop pedal.
But a drum machine would not be the most efficient use of resource (imo).
a looper pedal on the other hand…

The resource I am talking about though is that of the Neural DSP Dev Team; Not the QC processor/memory.

I am sure that they are taking an Agile/LEAN approach to software development, updates and iterations. Thus they ought to target the low hanging fruit for the moment. And they ought to remain focussed on updates which relate to amending code rather than writing new code.

Amendments would be for CorOS v1.x.x
New code should be for CorOS v2.x.x

A drum machine would require new code. New code for the sound source, new code for the sequencer, and then new code to integrate this. Followed by QA to check for bugs that result.
And this for a team who so far seem to have been 100% focussed on modelling and AI.

so for v2.x - sure some rhythm integration could be cool (though maybe v3.x or even 4.x)

In the meantime there is plenty that would improve the core features. You mentioned one: a looper (I am not sure if that requires more than just rewriting the code to a delay pedal though - and I know time based effects are hard).

Things like adding sidechain functionality to the compressors, or allowing a footswitch input to expression pedals, these are things that for CorOs v1 updates would make a big difference to the core offering.

Also there is a lot they can do to improve the usability of directories and search etc…

BUT - I am NOT saying that this feature should be ignored…
Just prioritised

1 Like