![]() I said what I said because it was what I met when thorougly testing it for the last weeks, after upgradingĬlicking on the Kontakt 7 icon I have placed on the taskbar opens it within 3 seconds.įanless system with Windows 11 Pro, 13th Gen Intel(R) Core(TM) i9-13900T, 128 GB DDR4 CAS 12, 2x Corsair MP600 PRO NH 8TB.Ĭlicking on the "vertical books" (Library Browser) shows all my libraries instantly, as soon as I release the finger I clicked with, showing a horizontal line with 14 instruments, 8 complete rows, plus another one with just 4 instruments, total 116, 279 according to Native Access 3.4, and the window anounces 19119 presets on the lower right corner.Ĭlicking on a heavy instrument, Amati Viola, Stradivari Cello, Guarneri Viola, loads them instantly. I'm looking forward to the migration feature in REAPER, but personally, I don't see myself replacing K6 with K7 anytime soon. I would definitely recommend to you check for the points above on your system. opening the GUI takes 5 seconds, should be instant So by making a side-by-side install, it enables people to work with their existing projects without introducing unnecessary troubleshooting and new variables into the equation during a project, yet still allows checking out new version with new features etc.Īs much as I would love to agree, this is definitely not the case (here). The main reason for new major version not overwriting older versions is simply safety, since there's always a period of bugfixes after a major release, and there can be unintended regressions lurking. Kontakt is fully backwards compatible all the way back to Kontakt 1, those old patches still open and sound the same as they did 20+ years ago. In Kontakt's case it's not a problem of backwards compatibility. Full backwards compatibility is the exception, not the norm. In my experience many plugins and other software have major updates that are not backwards compatible. That is good news moving forward!Įven if that was not the case, I don't think it is fair to say the fact it does not automatically overwrite previous versions makes it 'crap' or a 'rip off'. (By the way, there are extremely good reasons for new major versions of Kontakt NOT overwriting your existing version.) Holler at them and tell them this is important, I guess. Cockos just needs to finish the migration capability. So, there can be a very easy path for all your existing projects to migrate to K7 automatically. I have raised this point multiple times already and asked devs what's up but there was no reply. ![]() REAPER didn't yet fully implement this, unfortunately. It currently only works in Cubendo, Maschine and Komplete Kontrol, to my knowledge. However this also needs additional implementation from host side in order to work. In this case NI did all the due diligence and implemented VST3 migration capability, so that all previous versions of Kontakt, be they VST2 or VST3 regardless, can be automatically replaced with K7 VST3 instances. This is such a bad and inconvenient thing when plugin devs don't think about making a seamless experience when switching to a newer version of their product.Īctually, I am going to correct you regarding this statement. Reaper isn't spoiling you as such, it's fundamentally based on less crap policies. The sad thing is, it ain't just image-line. A "clean" smartphone OS install, and it's nearly 20gb while having a terrible interface, is horribly inefficient, some really dumb basic design decisions, etc.ītw, check out image-line's history and uh, connect some dots to many of those plugins (and their developers), pretty sure they even seed trojan pirate versions of their software. Like what was the deal with FL studio going from version 12 to 20, is that like indicative of how many years that crap stagnated and got more bloated? Have you seen how atrocious say, android, is? Yet people adopt that (yes, I was stupid enough to try FL studio and I saw how they treated, personally, an "All plugins" license user). Make no mistake, most of those companies really REALLY don't care and just want to rip you off. ![]() Nah the thing is, standards, policies and consideration are mostly lacking. Maybe the REAPER Devs spoil us by setting unrealistic expectations for other companies? I bet that the unforeseen errors popping up by trying to keep all versions backward compatible would be an even bigger inconvenience for users. ![]() It is standard not to overwrite whole number revisions, and not just for plugins. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |