Kontakt Updates (current version: 7.10.5) - Page 84 (2024)

Thomekk said:

An actual bad example - still from this year: Hitfilm was a great movie fx software driven by good people. Then it was sold to Artlist - this year they closed / deleted the forums and made it subscription only without asking. Now it seems to be dead.

Click to expand...

Not to forget that they sold extensions to Hitfilm Express and then after the Artlist purchase renamed it Hitfilm Free and told the customers Express would not be updated anymore and that Free is a completely different product (and the purchased plugins do not work in it). Artlist also destroyed Motion Array.

But it's great some companies still listen!

IFM said:

And don’t forget Avid, and a few years, has now backtracked and offers perpetual licenses and you can update whenever you want too.

Click to expand...

Yep. Avid's case was riddled with greed. It's not that they couldn't offer perpetual, it's that they shafted their loyal users to either subscribe, or c ya. After so many users ditched ship to alternatives like Logic, Nuendo, etc, I'm sure Avid felt that backlash and now, clearly we have seen the power of what customers can do to businesses. Now they offer Perpetual as if it doesn't even affect their current business model, but we all clearly know what happened there...

Waves too. That was a vivid one there. They make subscription announcement, people get super angry, boom, CTO is posting apologies and we see changes reverted. Funny how that works.

Without a customer = no business

EvilDragon said:

It works perfectly fine over here... Registry only contains info like what's the position of the library in Libraries tab and last known path for the content, which you don't really need to worry about.

Click to expand...

have you ever tried uninstalling something and then reinstalling it on the same pc because that's when i have to manually remove reg files or it doesn't work install right

• IMPROVED Double-clicking a preset in Files tab, Libraries tab or Quick-Load will now replace the preset loaded in the currently selected slot, instead of adding it to the Rack

Click to expand...

I may be in the minority here, but I liked the new browser/library/whatever because of the ability to get all my Kontakt libraries to one place. My biggest gripe about using it (and the reason I started avoiding it) was that I had to manually close the previous instrument I was using, causing unnecessary amount of clicks. So this is a great improvement to my workflow.

• IMPROVED Double-clicking a preset in Files tab, Libraries tab or Quick-Load will now replace the preset loaded in the currently selected slot, instead of adding it to the Rack

Click to expand...

This is a tricky one, I can see pros and cons. I've lost a lot of work in Opus which has this behaviour. If you'd changed the preset, I'd hope you'd now get a pop up warning "unsaved changes, are you sure you want to replace"?

Guy Rowland said:

This is a tricky one, I can see pros and cons. I've lost a lot of work in Opus which has this behaviour. If you'd changed the preset, I'd hope you'd now get a pop up warning "unsaved changes, are you sure you want to replace"?

Click to expand...

I believe you can toggle that in the settings - if it is Kontakt you are talking about (and not Opus)

peterharket said:

I believe you can toggle that in the settings - if it is Kontakt you are talking about (and not Opus)

Click to expand...

One would assume so, but unfortunately there won't be such setting.

Mr Greg G said:

One would assume so, but unfortunately there won't be such setting.

Click to expand...

(options->loading)

(edit: nevermind, seems there's actually a bug and this option screws with double-click loading even further)

halfwalk said:

(options->loading)

Click to expand...

That's certainly helpful, but I think fundamentally the user should have the choice of double click behaviour.

For those working monotimbral it makes more sense to replace, but for multitimbral it makes more sense to add. We should just have a preference to choose according to how we work.

All round 7.7 is a pretty dubious release. Have started a new NI forum thread requesting this preference.

Guy Rowland said:

That's certainly helpful, but I think fundamentally the user should have the choice of double click behaviour.

For those working monotimbral it makes more sense to replace, but for multitimbral it makes more sense to add. We should just have a preference to choose according to how we work.

All round 7.7 is a pretty dubious release. Have started a new NI forum thread requesting this preference.

Kontakt 7.7 - preference for double clicking file behaviour

This behaviour has changed in 7.7 so double clicking an nki replaces the existing instrument, rather than adding to it.

community.native-instruments.com

Click to expand...

Double clicking still works fine, it's just now there's an extra click sometimes (to deselect a selected instrument first). Just mind the little orange indicator (or rather, the lack of it) before double-clicking your next nki.

halfwalk said:

Double clicking still works fine, it's just now there's an extra click sometimes (to deselect a selected instrument first). Just mind the little orange indicator (or rather, the lack of it) before double-clicking your next nki.

Click to expand...

Yeah, I'm never going to be able to remember that in a million years...

A simple preference for how different people like to work. Job done.

Guy Rowland said:

Yeah, I'm never going to be able to remember that in a million years...

A simple preference for how different people like to work. Job done.

Click to expand...

Understood, and ultimately agreed. I just wanted to point it out because your post on the NI forum says:

This behaviour has changed in 7.7 so double clicking an nki replaces the existing instrument, rather than adding to it.

Click to expand...

which is only sometimes true, i.e. it's only true when there is an instrument already selected.

Anyway, sorry to bother, and good luck!

Guy Rowland said:

Yeah, I'm never going to be able to remember that in a million years...

A simple preference for how different people like to work. Job done.

Click to expand...

I am 100% in agreement with Guy here. I loaded up Kontakt after the new update, went to start a track as I usually do by loading a bunch of instruments into a multitimbral K7 instance, and was immediately very confused and annoyed by the new instrument-replacing behavior. Naturally, I came looking here to plumb the depths of this unnecessary mystery.

Having NI impose a new workflow on me that adds extra speedbumps preventing me from getting work done is not a welcome development. An option switch that enables the 'classic' behavior would fix this.

I really hope that NI's drive to expand their audience doesn't continue to degrade Kontakt's usability for people who require it in daily use and have well-established practices.

Guy Rowland said:

7.7 - it's finally happened. Never mind ads in Native Access, we now have ads in Kontakt itself - the New Instruments For you section in the main browser. You can minimise, but the headline still takes up space.

Sheesh, who'd have thought we'd live to see the day.

Shall we get the petition going good and early to remove it completely?

Click to expand...

I guess I should stop updating NI wares on autopilot and start reading the release notes first :-(

Delio Roman said:

Yep. Avid's case was riddled with greed. It's not that they couldn't offer perpetual, it's that they shafted their loyal users to either subscribe, or c ya. After so many users ditched ship to alternatives like Logic, Nuendo, etc, I'm sure Avid felt that backlash and now, clearly we have seen the power of what customers can do to businesses. Now they offer Perpetual as if it doesn't even affect their current business model, but we all clearly know what happened there...

Waves too. That was a vivid one there. They make subscription announcement, people get super angry, boom, CTO is posting apologies and we see changes reverted. Funny how that works.

Without a customer = no business

Click to expand...

and then Unity game software lol, the CEO just resigned. I think the board memebers told him he has to. He literally said a year ago that developers who don't want to have microtransactions in their games are stupid.. he has no idea how the game industry works. he's done. We are still waiting for Unity to come with a 2nd backtrack, they already backtracked once in the last couple weeks.

seems like 2023 is the year of tech companies making bad choices. ppl took it so far with the unity boycott that the developer of the game Terraria has pledged 100k donation plus a monthly donation to another software which is free donation software called Godot..

It's like every company is doing bad decisions this year. really not smart of them.

MapleFoxx said:

have you ever tried uninstalling something and then reinstalling it on the same pc because that's when i have to manually remove reg files or it doesn't work install right

Click to expand...

Yes I have, it works perfectly fine over here.

cedricm said:

I guess I should stop updating NI wares on autopilot and start reading the release notes first :-(

Click to expand...

TBH everyone should do this (reading the release notes) with ANY update from ANYONE. MHO.

Guy Rowland said:

A simple preference for how different people like to work. Job done.

Click to expand...

NI cannot be doing this forever (adding preferences for every little thing). Drag&drop still works. Can also be done with the Instrument Navigator if you don't have empty rack space available immediately (so you don't need to scroll a lot and doing additional clicks).

Let me explain a bit the thinking behind this change. Previously, Kontakt had a very dubious and sometimes even appearing-as-broken slot selection concept (and they're not really even "firm" slots, since when you drag-drop-reorder instruments, slot indices actually change, which is horrible). Considering there is now hardware which connects directly to Kontakt and navigates the rack externally, there has to be a move to a more firm slot selection concept (which is why you now see the orange strip almost at all times, whereas previously you didn't necessarily know which instrument was selected, yet you still saw virtual keyboard showing keycolors for SOME instrument you had to guess... horrible UX - now if you unselect the instrument you don't see anything on VKB which is good and as it should've been in the first place, logically). Hence, now that you see the orange strip and know at all times which instrument is selected, it is only logical that all file loading operations should be executed on that very slot. This is also how other software works in the same situation (i.e. Falcon and HALion).

And so that's why this change. This will be further refined until we don't have any edge cases left anymore. But we cannot be adding a checkbox for every little change along the way until we get there. I doubt everyone would want for Kontakt to turn into Reaper in this regard

I suppose let's see if there is going to be a huge outcry about this change. If not, we can safely say it was the right change overall.

@EvilDragon - I follow the logic just fine, and there are clear improvements when it comes to making the focused instrument more obvious.

Where - unsurprisingly - we disagree is that changing the way of working after 20+ years for professional composers is something we all have to just shrug over. I can see that not every possible option should have a preference, but this really is a pretty basic one.

So how about this is a proposal - don't add a new preference, change one. "Double clicking loads instrument" - what is the point of having that as a preference? If you don't want double clicking to do anything, don't bloody double click! It's a really stupid preference to have. Since preferences are precious, replace it with a choice that is actually meaningful - "double click opens instrument in next empty slot". The default replaces the active instrument.

I actually agree we should probably be removing some options that don't really make sense on a modern machine. For example:

Interface -> Show mapping and keyswitches on keyboard (should be always enabled)
Interface -> Auto-refresh Files browser (why would anyone want this disabled?)
Handling -> Files browser: Double click audio file loads instrument (as you suggested)
Loading -> Load samples in background (we all want this enabled forever, right?)

However, we need to challenge our assumptions here first. Hence this wouldn't be a swift change that happens in 7.7.1.

EvilDragon said:

I actually agree we should probably be removing some options that don't really make sense on a modern machine. For example:

Interface -> Show mapping and keyswitches on keyboard (should be always enabled)
Interface -> Auto-refresh Files browser (why would anyone want this disabled?)
Handling -> Files browser: Double click audio file loads instrument (as you suggested)
Loading -> Load samples in background (we all want this enabled forever, right?)

However, we need to challenge our assumptions here first. Hence this wouldn't be a swift change that happens in 7.7.1.

Click to expand...

Interesting - quite agree on 3 of those, auto-refresh files browser, does that have any CPU hit?

But that's well worth looking at. 3 or 4 new useful preferences potentially.