KK Registry error & ScanApp failed

Tombolino · 2023-03-07T22:42:21+00:00

There was an error rendering this rich post.

Good Morning. As I have been updating NI, I launched Komplete Kontrol standalone and get this error.

KK seems to scan non NI apps. Im not sure if the error is about KK or other apps? It seems to come up when it scans Sample Tank? (SampleTank, like version 2, old is in my computer, I never used it, Id rather not have to delete it/Uninstall). If Sample Tank is the issue, can KK bypass trying to read it?

Then I get another about Scan App. It hit ok a few times and then KK finishes opening and works fine, but of course getting this message every time is not sustainable and I need to fix it. Thanks in advance for any help!

Seb

Screen Shot 2023-03-07 at 10.09.04 AM.png

Screen Shot 2023-03-07 at 10.06.36 AM.png

Find more posts tagged with

Komplete Kontrol SW

Accepted answers

Jeremy_NI

No news from you for a while. We’re closing this thread now. If you still need assistance on that topic, please get in touch here: http://bit.ly/NIsupport_KKontrol

All comments

Tombolino

Nope? Thanks

JesterMgee

https://community.native-instruments.com/discussion/comment/57215#Comment_57215

You may have to wait longer than an hour for someone that has any idea of your issue to reply. Might help if you posted your actual computer specs and OS version since it's not even filled in on your profile either....

If it stops and quits on Sampletank, why not try and simply remove that plugin from your VST plugin folder and see if it resolves your issue? There is no way to tell KK to not scan a specific plugin, you can cancel the scan by pressing ESC during the load splash. Likely if you have old plugins you have not updated in a while,, that will be the issue. macOS doesnt play nice with anything old, you kind of have to get rid of things or update them.

Tombolino

Thank you Jester!

Tombolino

The registry error went away bc I removed some old VST that no longer work on m Mac.

But Im still getting this mssg. KK is up to date.

Further below is a long report generated

Screen Shot 2023-03-24 at 6.41.07 PM.png

Process: ScanApp [28373]

Path: /Library/Application Support/Native Instruments/*/ScanApp.app/Contents/MacOS/ScanApp

Identifier: com.native-instruments.ScanApp

Code Type: X86-64 (Native)

Parent Process: Komplete Kontrol [28370]

Responsible: Komplete Kontrol [28370]

User ID: 501

Date/Time: 2023-03-24 18:43:54.101 -0400

OS Version: Mac OS X 10.15.7 (19H1419)

Report Version: 12

Anonymous UUID: 6E70135F-4EEF-125D-F0BD-18E016B046E7

Time Awake Since Boot: 250000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [28373]

VM Regions Near 0:

-->

__TEXT 000000010718b000-00000001074ef000 [ 3472K] r-x/r-x SM=COW /Library/Application Support/Native Instruments/*/ScanApp.app/Contents/MacOS/ScanApp

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.toontrack.ezdrummer2 0x000000010a72e826 VSTPluginMain + 303552

1 com.toontrack.ezdrummer2 0x000000010a789838 VSTPluginMain + 676306

2 com.toontrack.ezdrummer2 0x000000010a78a01a VSTPluginMain + 678324

3 com.toontrack.ezdrummer2 0x000000010a736ad4 VSTPluginMain + 337006

4 com.toontrack.ezdrummer2 0x000000010a737fff VSTPluginMain + 342425

5 com.toontrack.ezdrummer2 0x000000010a7368c8 VSTPluginMain + 336482

6 com.native-instruments.ScanApp 0x00000001071ec5e7 NI::HOSTING::VST2Plugin::loadPlugin(NI::HOSTING::VST2PluginDescriptor const&) + 407

7 com.native-instruments.ScanApp 0x00000001071ec139 NI::HOSTING::VST2Plugin::VST2Plugin(NI::HOSTING::VST2PluginDescriptor const&, NI::HOSTING::HostInfo) + 313

8 com.native-instruments.ScanApp 0x00000001071f07df NI::HOSTING::discoverVST2Plugins(boost::filesystem::path const&, NI::HOSTING::HostInfo) + 175

9 com.native-instruments.ScanApp 0x00000001071d8eae NI::HOSTING::discoverVSTPlugins(boost::filesystem::path const&, NI::HOSTING::HostInfo) + 126

10 com.native-instruments.ScanApp 0x0000000107193071 NI::MASCHINE::HOSTING::ScanEventLoop::getDescriptors() + 209

11 com.native-instruments.ScanApp 0x00000001071927a0 NI::MASCHINE::HOSTING::ScanEventLoop::enterEventLoop() + 96

12 com.native-instruments.ScanApp 0x0000000107194b9d NI::MASCHINE::HOSTING::ScanPluginsApplication::doScanning() + 1309

13 com.native-instruments.ScanApp 0x000000010719560e non-virtual thunk to NI::MASCHINE::HOSTING::ScanPluginsApplication::onEvent(unsigned int, NI::UIA::EventData*) + 62

14 com.native-instruments.ScanApp 0x0000000107234992 NI::UIA::Application::sendEvent(unsigned int, NI::UIA::EventData*) + 34

15 com.native-instruments.ScanApp 0x000000010727850a NI::UIA::EventTimerManager::notifySubscribers() + 154

16 com.apple.Foundation 0x00007fff3c1fed5a __NSFireTimer + 67

17 com.apple.CoreFoundation 0x00007fff39afbce8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20

18 com.apple.CoreFoundation 0x00007fff39afb84e __CFRunLoopDoTimer + 872

19 com.apple.CoreFoundation 0x00007fff39afb339 __CFRunLoopDoTimers + 322

20 com.apple.CoreFoundation 0x00007fff39adff9d __CFRunLoopRun + 1885

21 com.apple.CoreFoundation 0x00007fff39adf1e3 CFRunLoopRunSpecific + 466

22 com.apple.HIToolbox 0x00007fff386faabd RunCurrentEventLoopInMode + 292

23 com.apple.HIToolbox 0x00007fff386fa7d5 ReceiveNextEventCommon + 584

24 com.apple.HIToolbox 0x00007fff386fa579 _BlockUntilNextEventMatchingListInModeWithFilter + 64

25 com.apple.AppKit 0x00007fff36d43669 _DPSNextEvent + 883

26 com.apple.AppKit 0x00007fff36d41eb0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352

27 com.apple.AppKit 0x00007fff36d33bbe -[NSApplication run] + 658

28 com.apple.Foundation 0x00007fff3c18df01 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 950

29 com.apple.Foundation 0x00007fff3c18d9e2 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 124

30 com.native-instruments.ScanApp 0x0000000107192709 main + 121

31 libdyld.dylib 0x00007fff73ac3cc9 start + 1

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 163798

thread_create: 0

thread_set_state: 0

VM Region Summary:

ReadOnly portion of Libraries: Total=657.8M resident=0K(0%) swapped_out_or_unallocated=657.8M(100%)

Writable regions: Total=156.6M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=156.6M(100%)

VIRTUAL REGION

REGION TYPE SIZE COUNT (non-coalesced)

=========== ======= =======

Activity Tracing 256K 1

CG image 4K 1

CoreServices 100K 1

Dispatch continuations 8192K 1

Kernel Alloc Once 8K 1

MALLOC 42.0M 30

MALLOC guard page 32K 7

MALLOC_LARGE (reserved) 95.4M 1 reserved VM address space (unallocated)

STACK GUARD 56.0M 6

Stack 10.5M 6

VM_ALLOCATE 64K 4

__DATA 30.2M 304

__DATA_CONST 393K 4

__FONT_DATA 4K 1

__LINKEDIT 390.0M 4

__OBJC_RO 32.3M 1

__OBJC_RW 1904K 1

__TEXT 267.7M 303

__UNICODE 564K 1

mapped file 38.9M 9

shared memory 632K 14

=========== ======= =======

TOTAL 975.0M 701

TOTAL, minus reserved VM space 879.6M 701

JesterMgee

Well I see this: toontrack.ezdrummer2

And since it seems to be a thread for VST2 then I would have a guess that plugin is either outdated or has an issue maybe?

Are you on an M1 system?

Tombolino

The registry error went away bc I removed some old VST that no longer work on m Mac.

But Im still getting this mssg. KK is up to date.

Further below is a long report generated

till getting a ScanApp fail message. Just made sure KK was updated. Not

Kymeia

macOS doesn’t have a registry

Tombolino

Thank you! Not M1.

Updated EZ Drummer but no dice. Otherwise KK works fine.

Jeremy_NI

@Tombolino Do you still get this issue?

Jeremy_NI

No news from you for a while. We’re closing this thread now. If you still need assistance on that topic, please get in touch here: http://bit.ly/NIsupport_KKontrol

Quick links

Unanswered questions