*.mux-Plug "Jd-An-Drum"

[jd88]

The final version of "Jd-AnDrum" will be available for download soon. More information coming soon in the thread:
"MuLab & MUX Modular Community Library"

- - - - -

OVERVIEW:

1. 12 drum instruments, each with 2 sample slots and up to 2 analog drum instrument slots (--> source: original MuLab samples & some orig / mod. analog *.MUX instruments).

The idea is to be able to layer these or supplement them with layers. (see the example published later: e.g., clap and ride...)

Of course, samples can be swapped if needed, and all drum instruments can be edited.
-

D 01 Drum 12 Instr Layer.png

-

2. PRE Main Mixer: Separate mixer: Volume/Pan per slot.
-

D 02 Drum Instr Mix.png

-

03. 3 audio gates (e.g., a hi-hat can mute the open hi-hat, or a crash cymbal can be stopped via the sustain pedal, etc.)
-

D 03 Drum 2 MIDI 3 AudioGates.png

-

04. Per slot: Env/Tune mixer
-

D 04 Drum 6 Instr Tune Env.png

-

05. Individual drum parameters can be changed via an overview. The individual drum instrument editing views can also be accessed here.
-

D 05 Drum Parameter.png

-

06. 2 drum instrument MIDI event delay lines, for example, for calling up drum phrasing under certain conditions (e.g., velocity) or even calling up a short, event-delay-based pattern in real time. This line can be output via MIDI.
-

D 06 Drum 2 MIDI DelayLines.png

-

7. 2 send effects: Delay and Reverb
-

D 07 Drum Delay -- Reverb.png

-

8. 4 audio outputs, freely controllable via instrument (Please refer to the MuLab manual regarding the audio routing settings for the mixer slot. This is already permanently assigned in one of my "Jd-Sy-Comb" patches).

MIDI:
The split range within which the drum should react can be specified, as well as which MIDI notes should be assigned to each instrument for the possible MIDI output.

-

D 08 Drum 4 sepAudioOut.png

D 09 Drum InstrEdit.png

D 10 Drum InstrEdit.png

- - - - -

Using this in the "Jd-SyComb" creates a complete drum machine (including 3 patterns and MIDI output, live performance options, and much more).
A corresponding example will be available for download shortly.-

[dayvyg]

Wow! Very impressive.

[cousin_itt]

Great work!
I love drum synths, can't wait to try it.

[jd88]

Unfortunately, Uploading the last 2 plug-ins "Jd-AnDrum" & "Jd-Comb" will take quite a while.

It turned out that it is currently unusually (Not as easy as thought / has to be) cumbersome within MuLab if you have to change / expand / sort the automation data / parameters afterwards. Unfortunately, I don't have the time for that at the moment.

[jd88]

After waiting a long time for bug fixes/additions from MuTools, I've now uploaded the last two plugins, "Jd-AnDrum" and "Jd-Comb," simply "as they are." (stopped support / working on it)

I've made the mod section as clear as possible so that everyone can potentially work on/optimize (and understand) it for themselves. Especially since MuTools has fixed bugs, it should also be simplified/corrected accordingly.

- - - - -

It seems that MuTools isn't providing the "truly necessary!" updates, and fixing current bugs is taking far too long for me.

Since I work on an Apple Mac, I haven't been able to test the new versions that MuTools has been repeatedly uploading for Windows. (Perhaps there was a fix, or perhaps I could have adapted something to the aforementioned *.MUX files based on the new features?)

For me, the topic of MuTools/MuLab is off the table for the time being. It's a shame, but not a problem (I've long since switched back to my relevant DAWs/mod synths). So, MuLab was simply a nice test run.

- - - - -

The question posed in the forum: "Why isn't MuLab more well-known/widespread?" - This has nothing to do with a lack of advertising, budget, etc. You don't necessarily need marketing experts. MuLab could be so exceptional that it would gain recognition on its own. MuTools would certainly find a lot of support.

HOWEVER:

From my subjective point of view:

The main problem seems to be that MuLab repeatedly gets bogged down in things/changes (which sometimes just spontaneously occur to the programmer??). It seems to lose sight of what's essential/goal-oriented. It's hardly foreseeable where it's headed, when and how existing problems will be solved.

The number of programmers working on a project is neither important nor a justification for anything. The project (in this case, the DAW) simply needs to work.

- - - - -

As before: MuLab is a really great idea with a fantastic feature set/concept. Further development and finalization simply need to be straightforward.

[MuTools]

It seems that MuTools isn't providing the "truly necessary!" updates.

"truly necessary" might be a subjective thing.
What's truly necessary to you may not be truly necessary for another.
Anyway, feel free to be specific.

and fixing current bugs is taking far too long for me. Since I work on an Apple Mac, I haven't been able to test the new versions that MuTools has been repeatedly uploading for Windows.

Several bug fixes during the MuLab 10.2 beta, but indeed the MuLab for Mac updates have been lagged behind until now, but now MuLab App 10.2.17 beta for Mac is available here:
viewtopic.php?p=9235225#p9235225

The main problem seems to be that MuLab repeatedly gets bogged down in things/changes (which sometimes just spontaneously occur to the programmer??).

Here is the draft change log of MuLab 10.2: https://www.mutools.com/mulab-mux-change-log.html
Please tell me: What's on that list that you find a wrong choice?

It seems to lose sight of what's essential/goal-oriented. It's hardly foreseeable where it's headed.

MuLab's goal is to be a musical kind of "Lego".
Play around with "blocks" of sound and sequences, combine them and build something bigger, sound-wise and/or music-wise. For MuLab sound and music are very close to each other: A music track can be seen as a complex sound. MuLab's goal is to offer a creative sonic/musical playground. MuLab's goal is not to be the Nth traditional DAW, though MuLab also tries to support more traditional DAW work.

I also give high priority to avoiding the typical "bloating" of software that grows during many many years. That's why, for example, i decided to convert the racks into true MUX Modular patches. It's a win-win: The user gets many more musical options, yet the way to reach that does not get more complicated, at the contrary: It's all using the same MUX Modular tools.

The project (in this case, the DAW) simply needs to work.

It does, doesn't it?
If something is not working, please specify.

As before: MuLab is a really great idea with a fantastic feature set/concept. Further development and finalization simply need to be straightforward.

Can you please specify what you mean with "straightforward"?

Thanks.

[sl23]

Wow! When you look at that changelog, that's some list! Shows how much work you really do! Very much appreciated.