MASCHINE and KOMPLETE KONTROL Development Updates

Myself I would have thought seeing as how it so affects everything, Automation should have been a major priority. I do think it will have to be attended to soon.

Do any music programmes actually use hyper threading at the moment? I have a feeling that I read somewhere it is generally considered, too much work for too little return though I could easily have got mixed up about that.

 

Really off topic but what the heck:
Yes, every software I own that requires efficiency has hyperthreading, I'm not shy about trying software trials either... Unfortunately, computer benchmarks and comparisons are all extremely geared towards gAmInG so there's not much info online about Audio and even when there is it's often contradictory. When this technology was new a lot of people claimed it did nothing or gave worst results, those claims still float around a lot but have mostly been disproven by evidence.

I've tested Maschine VS Ableton with Serum (since people complain it's CPU intensive), loaded a preset, activated all fx, put some notes down and duplicated it over and over... Ableton is stable with around 33 instances and Maschine is stable with 20, thats quite a difference. I can't say this difference is only because of hyperthreading, the efficiency of an application depends on how it's developed. I guess i could disable Hyperthreading in my Bios and retest Ableton but I dont see much point.

The return depends on the use case and can be considerable but maybe not exactly what people expect, since threads (generally) double the CPU cores people often expect double the performance, in reality, it's should be around 20% more. If the user claims simple projects are unplayable then there's deeper problem and hyperthreading won't fix anything. AFAIK HT is not something you add, the application has to be built from the ground up with it in mind, meaning if it ever happens for Maschine it will be in a major update.

 

Hi,

isn’t it time for a build in virtual keyboard?
I have this on my wish list.
there is not always room for the controller and only just to move light is a pleasant feeling.(smile)
I think this could definitely be worth implementing, right?

This update will allow us finally to drag our audio trough the timeline.
Does this come in a warp type of way?
I can’t wait to edit my vocals Extensively On this new update.

I Also hope to see New build in plugin like auto tune in maschine software.
and auto slice for the sample.
More build in plugin to fix vocal/audio problems.

 

Automation curves it s really necessary

 

Thank you! The sooner the better! I cannot wait for the day Maschine is my primary DAW. Love the workflow with my MK3!

 

I also often think and fin weird that you can open preference menu with CMD+, but once open, you can't even navigate in the preference panel using tab and arrows.. would make sense though.

 

1000% this. I agree. I understand the concern that making Patterns freely movable won't work - but at the very least then Clips should be "shared" or "linked" so a change in a clip can be automatically applied everywhere. This is really, really, really essential. Maybe make it an option so folks can work with every clip "unique" by default, but not being able to have linked (or alias or shared) clips and not being able to have patterns freely movable is just going to be frustrating. It's so close to having the best of both worlds but the gap between the two is a real bummer.

 

Thank you for the update Kai! I'm really looking forward to getting hands on and testing the new features in my workflow. Very curious to see how this will work on the mk3 hardware.

 

I'm excited about the new developments.

The ability to write/type in the velocities of midi notes would be tight. Smoother automation curves would also be appreciated.

 

Understandable. My opinion on this though is it is better to still add a feature even if it absolutely can’t be integrated with the controller.

 

Agree, if it allows me to add transitions, and patterns/audio of arbitrary length and position, then a non-perfect hardware workflow, or a Maschine-software only workflow, is still significantly simpler than, and infinitely preferable to (IMO), exporting stems and/or running Maschine as a VST in some other DAW.

 

I'm really happy with this news. The new clips feature seems a good way of adding functionality without disrupting the existing workflow. I'm sure the devs will work on the software first and then, once the features have been finalized, they will update the firmware to control them from the hardware.

As others have mentioned, the automation needs work- an ability to manually add points from the hardware and then apply an adjustable curve between them would be a good way of implementing automation editing in much the same way as other DAWs. A knob to scroll between points, a knob to adjust height, another knob to adjust curvature and a couple of buttons to add/delete points. An ability to automate mute and FX bypass settings would be good too.

 

Absolutely just offsets wouldn't be enough and multiple Patterns per Section would be an excellent and elegant way to go that would have a simple accessible way to use and not over-complicate the arranger/timeline. And, frankly, I simply don't accept it's not possible for technical reasons: one straightforward way it could work is for the multiple Patterns selected for a Section/Group to be treated as one "Section Pattern" in the background and outwardly seen as multiple Patterns. From any way I look and think about it, though, enhancing Patterns is a more straightforward option than Clips, which, still to me, seem like a decent idea on the surface, but have multiple gotchas and potential issues down the line.

Or if everything was just in a Pattern, there'd be no need for complications of overlay/ghost features and the workflow would be simplified but (potentially) equally as powerful (arguably more powerful if it's simpler).

As discussed above and elsewhere, I really don't see this as a problem or, at least, not one that isn't solvable and, importantly, to work fluidly (and with the MASCHINE hardware).

To me, this depends very much on the feature: if it's really something that wouldn't be especially beneficial on the hardware but would fit with the MASCHINE workflow, sure, but on the whole, MASCHINE is a hardware-software hybrid and its virtues and success has largely come, I'd argue, from that hardware integration - to now depart from that would be a massive mistake. All new features and enhancements should be considered and implemented with the hardware firmly in mind.

 

"Later This Year" or Later Next Year ?? lol
I love how all of the last updates features work
but I honestly can't wait for these new features
I really think you should just push the updates out
and update them as you go , we sit in the dark too long
hoping something is actually being worked on
don't get me wrong its really exciting ! and this news is good
but I won't hold my breath , all n all keep up the good work

 

I would upgrade just for this

 

great news, but i like the pattern/scene/section workflow. when i want more, i go to plugin mode.
clips is another thing, i can understand why it is difficult to implement it with the pattern workflow. still there is an example that hasn't problems with it..

the question is already in a post or 2.

how will clips be managed from maschine mk3 (and jam....), i.e. how will the workflow be on the controller(s).
if the controller can work with clips, that is the whole point, about maschine, the integration with the controller(s).

jam is discontinued, i hope it will for users, that have bought the jam, clips can also be used via jam.

i like the workflow of maschine with the controllers. as already said, you don't have to use clips.. but i am wondering..

 

Love the direction. Now, If we could somehow be able to drag and drop the whole arrangement in one shot into a daw like the Midi and Audio drag and drop, that would be sick.

 

Happy to see there is some great movement in the development. However, like others brought up already, I do think the strongest point of the Maschine is the hardware <-> software integration, and am less interested in features that focus mainly on the software. The main reason being that there are already a dozen DAW's that offer these kind of features. If I want a full DAW workflow by clicking around on the screen, I can choose one (or more) of these. Of course I do think Maschine can use improvements on these levels, but think the hardware <-> software workflow should remain the focus.

At the same time, there is much room for improvement on the hardware workflow, especially considering live performance. More on the fly pattern / event editing is something I would love to see improved for use of the Maschine in a live setting. For example, being able to change the length of a pattern by changing the distance (double / half / more fine tuned) between all (!) events in a pattern at once would greatly improve the workflow. Like this:



Also stuff like mirroring patterns, changing pitch distances etc. would help a lot. Renoise is a good example of a DAW where you can do these kinds of things with the press of a button. Having such functionality under Events in the Maschine hardware would be awesome.

Creating pattern events (under Variation) with different algorithms (other than just 'random'), that you can then finetune with a knob or two is also something I would like to see.

I suspect these kind of features would be relatively easy to implement (as they hardly interfere with existing functionality), while adding a lot to the workflow.

 

Hey Kai @ NI , thank you for giving us an update and some transparency on what's in the works! Very much appreciated.

Question for you — will this "background scanning" feature in Komplete Kontrol speed up the load time of the plugin? You may have seen threads on this forum already, but in large Kontakt databases with many libraries, the Komplete Kontrol plug-in takes 10+ seconds to load per instance, which is a non-starter for those of us who work in large projects and with templates. It would be great to be able to use the performance functionality and light guide on my S61, but Komplete Kontrol's instantiation time compared to plain old Kontakt prevents me from doing so.

My hope is that this "background scanning" you mentioned will allow the KK plugin to load quickly while any library scanning it needs to do can continue in the background. Is this the correct interpretation?

Thanks!

 

I'm sure I'm not the only one thinking this, but at the end of 2019 when NI started talking about 'One Native' they weren't making it clear they were just talking about Maschine.

It would be great to see some actual updates for Komplete Kontrol, because not all of us want to make Hip Hop or Electro.