Can you believe Native Access 2 uses a *.bat file to update Native Access.
it was the way in 1995 when DOS was the OS.

i can't believe either the quicklaunch box (kontakt) is behaving like window 3.1 when creating or moving folders or copying and pasting entries.
Also quicklaucn box will not update itself if you save/add an instrument into the folder.
Pretty bad system definitly not to 2025 standards.

i could understand that "if it's not broken, don't fix it".
but *.bat files i think is a big security issue.
and the quicklaunch box is very annoying to use.

(I'll add few other things when i remember them. I can't recall for now.i know there's more)

 

Last edited: May 6, 2025

Geeze. Wow.

 

bat(ch) files from trusted sources, or ones you write yourself; are not a security concern more than any other executable file. You can open them in a text editor and they are generally not obfuscated or encrypted, unless deliberately. You can read every line of commands in plain text, and you could even run each command one by one.

 

Batch files/command scripts are no more security risk than any other executable you run on your computer. Besides, they're still in very wide use all over Windows and the ecosystem on the whole.

What does this say about Windows or computing in general? Scripting is handy as fuck. That's all it says.

 

100%

 

if you use windows and don't occasionally use batch files, your life is likely harder than it needs to be

that said, I do miss native instruments when it was cutting edge

 

wtf. is Native access anyway?

 

Upgrading your Komplete seems like such good value, until you realize how little of it you actually use.

 

It's Native Intruments licences and downloads manager.

 

Also these tiny font everywhere from the pixelfont era in nearly all products.
And often the terrible usability....

 

I never use Kontakt "quick-launch" so, don't know, can't say... Although if you are having issues with libs showing up in the menu it's always been a standing rule that one re-starts Kontakt when ever a new lib is added. Then it shows up in the list.

Batch (.bat) and Command Scripts (.cmd) are executable yes - but so is an ".exe" or ".com". There are also ".ps1" scripts executable by power shell. Scripts are no more a security risk than text files because you as a human have the ability to observe the code directly and visually see what the script does. The ".exe/.com" executables are compiled code that is gibberish to a human - if you're going to cite a security risk the ".exe" or ".com" file is way more of a risk because humans cannot parse them - you can scan them for anomalies (with an A/V or malware scanning tool) but that's really about it.