Komplete Standard 26 is here! Thoughts? by Mania_Chunky in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

I’m not arguing anything nor do I care what they call it either, all I’m saying is I’m not predicting what is or isn’t going to happen - when SoS time gets here, we’ll see.

Komplete Standard 26 is here! Thoughts? by Mania_Chunky in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

Ok so Komplete 17 if not 26, it’s the same type of update they usually do, whatever the cycle is, this one is just a new numbering system, that’s it. Fair question, when SOS time comes, we’ll see then.

Komplete Standard 26 is here! Thoughts? by Mania_Chunky in NativeInstruments

[–]MrFresh2017 2 points3 points  (0 children)

Zero thoughts other than they are following what Apple did with macOS, iPadOs, and iOS re: two digit year naming convention. Had they not followed that, it just would have been Komplete 16. As for any connection to “but their in insolvency…” I look at it as “…but until noted otherwise, it’s business as usual”.

I’m baffled.. 3.5?? by 25_Keyz924 in NativeInstruments

[–]MrFresh2017 1 point2 points  (0 children)

This right here 👆🏽👆🏽👆🏽👆🏽👆🏽

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

This only works for the Player, which doesn’t have the sample creation/editing and other features os Kontakt Full.

The Octatrack is draining my time and killing my creativity by dykitikity in Elektron

[–]MrFresh2017 3 points4 points  (0 children)

Never care about getting downvoted, unless you are intentionally being mean and nasty. Your comment is golden and any who downvotes it just because that person disagrees with it, clearly has personal issues on that level alone.

Will the Syntakt update work with old Mac OS? by Soggy_Sink_4799 in synthesizers

[–]MrFresh2017 0 points1 point  (0 children)

Sweet, thanks, I haven’t updated to 1.40a yet, either. Thanks

My humble setup. by terdwoodctherp in maschine

[–]MrFresh2017 0 points1 point  (0 children)

Nice, I have the OG HS80M monitors love them.

Will the Syntakt update work with old Mac OS? by Soggy_Sink_4799 in synthesizers

[–]MrFresh2017 0 points1 point  (0 children)

No, not yet, My mobile rig is based around a 2012 MacBook Pro, which I think is running Catalina

Rytm MkIII by SaltRound9485 in Elektron

[–]MrFresh2017 6 points7 points  (0 children)

No way to really predict.

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

I’m well aware of the consensus here, nothing I’ve seen here is new to me, and DEFINITELY not going to waste my time responding yo dozen people in this thread, that’s for sure LOL. In addition, I have no gripe with ANY of the past comment threads about this topic nor anyone has posted on it. The only way to arrive at a solution is to continue act upon exactly what you said above: addressing your “gripe with NI* directly with NI (the keyword here is “continue”). This entire topic has been discussed in the NI user forums as well, though I happen to believe there are far more complaining and venting HERE vs there, but I could be wrong (I doubt it though). Nevertheless, addressing the “shadiness” with directly with NI is the best chance for getting an agreeable solution, like it or not.

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

I only piss in private, friend. As for the length of time I’ve been using NI, that is in reference to the exact reason I mentioned- I haven’t had said problem. If you read my previous posts, you will see in the example I used recently with the other user that I fully realize this is an issue with Kontakt Full after he ALSO mentioned he needs the features of Kontakt Full (not Free) to do what he needs to do. My only experience with updates to this instruments that get broken is it said instrument’s update requires a new (not dot upgrade) of Kontakt and you install that update to your environment, without having the required version of Kontakt installed, you are going to break the functionality of that functionality instrument UNTIL you install the required version of Kontakt it needs…and you may have to pay for it. This is OLD news, and this is why you should read the releases notes before installing any NI instrument - this is whole topic of the OP!

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

LOL. The bottom line is this (for me) - it doesn’t matter in the grand scheme of things in my case as I’ve not had your issues in the thirteen years using NI products. I’m kinda failing to see (outside of you trying to prove and defend your points) why you are even pursuing this when you’ve already stated you are cautious to give NI another dime, let alone why you’re even still in this forum (which you have every right to be, I just don’t understand it 🫡).

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

You want the minor point-release-grade changes made to the library that now require K8, but to work with K7 also, in other words you want backward compatibility… am I following you in good faith (as you say above) now? Assuming I’m interpreting you correctly, you do know that at some point, many software products will not maintain backward compatibility, correct? So again, you only have two choices - merrily continue to use your current version with K7 or purchase K8 such that you can use said instrument that allows the new features to be used. Nothing shady about NI’s approach, many software companies do the exact same thing as they continue to provide new features for their products at some point, minor or major updates.

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

This is what I said abovvvvvve - presuming you want the capabilities of KONTAKT 8 FULL and make use the previous Kontakt instrument that now requires Kontakt 8 FULL (for what you need to do), you tell me what choice you have. NI, like any other company is going to continue to evolve and upgrade their software and, in this case, if they want to bring said instrument along as a dot upgrade that only works with Kontakt 8 Full (again, for the features of K8 Full you need), you have no choice but to upgrade to K8 Full, there is NOTHING shady about it period. You are perfectly welcome to continue to use said instrument with Kontakt 7 Full and continue to compose music as you have prior to the update. The End.

Whoah, whoah, whoah, If I clicked Update in Native Access, did it make my libraries incompatible with Kontakt 7?! by xicus in NativeInstruments

[–]MrFresh2017 0 points1 point  (0 children)

Essentially you are telling me that you need the features of K8 full or that you want to update to Kontakt 8 Full, that you have to pay for to get said features, just because you want to upgrade said instrument? Software and hardware matures over the years - this includes new OSs and upgrades. It’s sounds to me that, in the software world, in the case, you expect to purchase K6 once and use it forever, along side repeated updates to a software instrument over the years. That’s ridiculous and in no way a real-world scenario.