Neuzeit Instruments Drop

Similar to your approach, except in my case the Drop is paired with a 16 x drum sample drum rack in Ableton Live (with Push 3) and my approach is to (kinda) replicate a TR-1000/TR8S layout.

Knob 1 is filter cutoff, knob 2 is pitch, knob 3 is length (ie amp decay in a drum sample context), knob 4 is FX send (usually a stereo delay).

Faders are drum levels, buttons are mutes. I could use the buttons as a second FX send (on = 50% send level, off = 0% send level) but in practice the buttons on the Drop are great for performance mutes IME, nice and clicky (in a good way).

It is such a great bit of kit. With just those 4 knobs plus fader and mute per drum x 16 drums I can create huge variations with snapshots without even having to change the pattern that’s playing on the Push.

3 Likes

For those not able to stretch to the cost of the Drop… https://www.elektronauts.com/t/ableton-live-12/203153/3972

Can the macro variations morph between them, that should the strength of the Drop.

was the question for me?.. then yes that M4L device can morph seamlessly between the snapshots (with quantisation to finish/ start on beat) and also crossfades like a certain Elektron instrument…

1 Like

Or even… use both. I do. Great combo.

my problem with this type of setup, is that I may need a to create multiple setups for multiple patterns if all of a sudden I need to be able to tweak a parameter that is not on that list.
Because Elektron boxes are multi timbral, and unless you keep your tracks always mapped to the same instruments/machines//samples all the time on every pattern, you cannot always expect to have a machine that will open the filter the same way, because of the multiple filter types, though at least picked parameters that exist on every instruments. If you start using parameters that are unique to a machine, then once again, you will have to juggle between different drop configs when you change patterns or songs.
imo, that was too tedious to keep up with and introduces considerable time on composition, which I’d rather keep doing as much as possible on the Digi boxes.

A new idea? Need new drop template now. Did you dare putting this exotic drum machine from the DN2 on the wrong track? New mapping template to support that pattern now…

I now prefer using macros, like I had shared above, and make these changes per pattern within teh digi boxes, meanwhile, I just create snapshots of this same template every time on Drop and compose ad hoc in teh digitakt macros menu, for FXs that are going to be the ones to have fun with while a pattern is playing. for all risers and other transition effects, I try to compose it using the ā€œlastā€ condition within patterns. Managing transitions with the drop is fun, but over complicates things imo.

Like someone mentioned earlier, it can be compared as an octatrack with tons of crossfaders assignable to each patters.

The drop solves a lot I think, but can be also a time trap. it can do so much, it is easy to spend time over complicating your process, so I always find myself always wondering if I am solving for the initial problem I want to solve, which is to streamline my process, and not get in the way of finishing songs.
Sometimes I find that I can easily complicate it with the Drop too. Aaaand that’s what it makes it a super deep, yet dangerous piece of gear that will keep being a workhorse for different use cases. like the OT was for me.

Curious to hear how that works out for you.

We could really use a sticky post for various community made templates in here :slight_smile:

3 Likes

Probably not what you are looking for, but this is why I sold my Drop.
It was just taking up too much time, and imo it doesn’t integrate that well with grooveboxes, ie. the pattern changing.

After too much messing around, I decided that my Octatrack can fulfil all of my performance needs.

It’s a great controller, but if you have limited time, I think it’s a bit overkill.

3 Likes

The more I thnk about it, the more I find EzBot’s take about using it with the Octatrack only, like he did in his video, to be one of the best use cases.
At first, I was, ā€œwhy would you not use it with the digitakt or digitone?ā€ , then it made more sense as I got mine.

1 Like

That makes a lot of sense. In my case, I have a layout for techno and for ambient/experimental and I always map the same instruments / effects to the same tracks across all patterns. Thus I can create a layout on Drop which would be usable across all patterns.

I was thinking of using macros too (Modwheel etc.) but to me that creates another layer of abstraction which I’d have to create and maintain. Also, I’d need to tune different parameters on each track separately and save it in a macro, whereas if I have parameters on drop directly, I can just play around with these and save as a snapshot, which is very quick and handy.

As my mate said recently, it’s all a bit of a puzzle and one needs to find what works for them. I 100% agree with this statement.

I will only start integrating the Drop into my setup in a few weeks as I have a gig coming up and don’t want to get disctracted with a new toy. Will share what I’ll set up eventually.

2 Likes

Was looking at one and after reading what DiVeR had to say I am now inclined to drop the idea. Moreover, I think P3SA seems a better choice to do a similar function. I supposed one of the reasons that could be attributed was that Thomas refused an online editor on PC which would help speed things up and transfer easy presets made by other users.

2 Likes

I just want to add that, all I am saying applies to my use case of Elektron boxes; aka, using multiple patterns over a song, by ex: progress from patterns 1 through 16 to play the full song. Same applies for song mode.
If you use single patterns per songs on digi boxes, none of my comments are relevant. and the drop becomes a better companion all of a sudden.
Each snapshot on the drop matches a song/pattern and in that case, it’s a fail proof system, as long as you don’t need to change projects on the drop in the middle of a set.

4 Likes

I really wish this had an OLED screen.

Some tasty new updates to Drop in the FW 2 beta!

2026-04-24 Firmware v2_01-beta-10

  • New: Eight layers!
  • New: Layers can now be named and colored. The Layer A/B buttons can be assigned a dedicated behavior, such as Previous Layer or Next Layer, or they can be set to temporarily shift to a specific layer while holding the button. The order of layers can be changed
  • New: Mapping Helper Functions: Slot copy/paste, reset to default message, collision warning, and auto-fix collision
  • New: Curve type ā€œFlexā€: A linear curve with two individual X/Y coordinates
  • New: Curve type ā€œFeedback Onlyā€ with no MIDI output
  • New: LED styles that react to MIDI input by changing color, showing clipping, or displaying a volume meter
  • New: The MIDI database browser now allows filtering by section and shows, in mapping, when a database link was used for assignment
  • New: Control element colors added: red, green, blue
  • New: USB setting ā€œHost Priority,ā€ which allows Drop to function as a host-only device on a USB port (required for Elektron Tonwerk)
  • New: 24 PPQ clock input speed
  • Improved: Overall clock sync precision
  • Improved: When copying, pasting, or moving control elements, they now swap with the existing ones instead of overwriting them
  • Improved: A backup file is created when opening an old project with new firmware v2.0x
  • Fixed: Moving control elements now takes snapshot save selection groups into account
  • Fixed: USB connection to the Befaco MIDI Thing v2 expander
  • Fixed: Smaller issues along the way

https://www.neuzeit-instruments.com/firmwares

8 Likes

Awesome! I’ve been waiting on this update to integrate Tonverk into my liveset

1 Like

Wow. That’s quite a list. Having more than two layers is a big deal IMO, it means the Drop could replace a bunch of other MIDI controllers in my setup.

(Edited for clarity)…

It does also mean that the lack of a computer editor becomes a bit more glaring. With 2 x layers (A and B), mapping all of the Drop’s controls involves naming and colourising 96 different controls (ie 6 physical controls per channel x 8 channels x 2 layers, and even more than that if you include different layers enabled by the clickable knobs). It takes a while and is quite tedious but it’s doable.

With up to 8 layers, that would mean manually configuring up to 384 controls, one by one. That is mind boggling.

Thomas… please can we at least have the option of a computer editor? It is fantastic that you continue to add more depth to what is already a superb bit of kit. But unlocking all of the Drop’s potential is going to be quite challenging once this new firmware is released.

Best place to give Thomas feedback is on the official MW Neuzeit support forum!

https://www.modwiggler.com/forum/viewtopic.php?t=294505

3 Likes

Hi does anyone know the size of the barrel pin on the power supply, I’m trying to free up the other USB port and have found USB-C → Barrel cables but I’m traveling and don’t have the it with me.

Alos any good reason not to go this route? Power issues etc

It is a 2.1 5.5mm barrel with positive center.

2 Likes

I caught up with Thomas from Neuzeit about the 2.0.1 beta firmware and he showed me a preview of the, not yet released, motion recording feature he’s been working on. I’ve made a video of his demo for you all.

I’m impressed by the pace of firmware updates and new features while also spending the last year shipping it.

Thomas seems really pleased with how the Drop has been received and he mentioned it’s enabled them to move the business to new premises.

8 Likes

Pretty amazing stuff. Thanks. Thomas has nailed it really. Such a great bit of kit. I think it’s the absolute king of MIDI fader controllers now (not least because it’s so much more than a MIDI fader box). Can’t wait for v2 to come out of beta, having all those layers will be so useful. And built-in instrument definitions (Oxi-style)… excellent!

3 Likes