Hi there!
I downloaded the latest update from the app store today, on my MacBook Pro (16-inch, 2019). It's version 4.7.5. The previous version worked fine for me.
The crash happens after the app opens and shows the main screen (4.7.5 ENTER). If I click fast enough I actually can see the "watermark removed" and click on the keyboard to see it response - but it crashed right after that. (Or crashes on the main screen if I don't click anything).
This is the crash log I see pop up after clicking on "Report" Process: SeeMusic [44981]
Path: /Applications/SeeMusic.app/Contents/MacOS/SeeMusic
Identifier: com.VisualMusicDesign.SeeMusicUnity
Version: 4.7.5 (201)
App Item ID: 1494196015
App External ID: 848193809
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: SeeMusic [44981]
User ID: 501
Date/Time: 2022-04-08 21:39:15.174 +0300
OS Version: macOS 11.6 (20G165)
Report Version: 12
Bridge OS Version: 5.5 (18P4759a)
Anonymous UUID: 9F4A4A3E-FFF7-4E51-BF22-CC45AC88F384
Sleep/Wake UUID: C4290CD3-35DA-4666-B7F1-3E240B7DD3A6
Time Awake Since Boot: 390000 seconds
Time Since Wake: 5500 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.renderheads.AVPro.Video-Core.12345 0x0000000134bb05a8 0x134b80000 + 198056
1 com.renderheads.AVPro.Video-Core.12345 0x0000000134b99ff8 0x134b80000 + 106488
2 com.renderheads.AVPro.Video-Core.12345 0x0000000134b9a188 0x134b80000 + 106888
3 GameAssembly.dylib 0x000000012456c158 0x124017000 + 5591384
4 GameAssembly.dylib 0x000000012456b398 0x124017000 + 5587864
5 GameAssembly.dylib 0x00000001251b0a8e 0x124017000 + 18455182
6 GameAssembly.dylib 0x000000012431c454 0x124017000 + 3167316
7 GameAssembly.dylib 0x000000012431c2ce 0x124017000 + 3166926
8 UnityPlayer.dylib 0x000000010f17ebfc 0x10eb29000 + 6642684
9 UnityPlayer.dylib 0x000000010f184b80 0x10eb29000 + 6667136
10 UnityPlayer.dylib 0x000000010f1a1a76 0x10eb29000 + 6785654
11 UnityPlayer.dylib 0x000000010ee4b06b 0x10eb29000 + 3285099
12 UnityPlayer.dylib 0x000000010efc7895 0x10eb29000 + 4843669
13 UnityPlayer.dylib 0x000000010efc78f4 0x10eb29000 + 4843764
14 UnityPlayer.dylib 0x000000010efc7b73 0x10eb29000 + 4844403
15 UnityPlayer.dylib 0x000000010fab92ad 0x10eb29000 + 16319149
16 com.apple.Foundation 0x00007fff213c2e0f __NSFireTimer + 67
17 com.apple.CoreFoundation 0x00007fff2060abe9 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
18 com.apple.CoreFoundation 0x00007fff2060a6dd __CFRunLoopDoTimer + 927
19 com.apple.CoreFoundation 0x00007fff2060a23a __CFRunLoopDoTimers + 307
20 com.apple.CoreFoundation 0x00007fff205f0e13 __CFRunLoopRun + 1988
21 com.apple.CoreFoundation 0x00007fff205eff8c CFRunLoopRunSpecific + 563
22 com.apple.HIToolbox 0x00007fff288381f3 RunCurrentEventLoopInMode + 292
23 com.apple.HIToolbox 0x00007fff28837f55 ReceiveNextEventCommon + 587
24 com.apple.HIToolbox 0x00007fff28837cf3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
25 com.apple.AppKit 0x00007fff22df9172 _DPSNextEvent + 864
26 com.apple.AppKit 0x00007fff22df7945 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1364
27 com.apple.AppKit 0x00007fff22de9c69 -[NSApplication run] + 586
28 com.apple.AppKit 0x00007fff22dbde6c NSApplicationMain + 816
29 UnityPlayer.dylib 0x000000010fabc91d PlayerMain(int, char const**) + 989
30 libdyld.dylib 0x00007fff20515f3d start + 1
4.7.7 is now available for MacOS from the App Store and should fix the issue.
Amazing - thank you very much. The new version (4.7.7) works for me without crashing!
Absolutely - thank you for making this amazing app! :)
Thank you for reporting the issue.
A few other users have reported the issue and I’m working on it as fast as possible. The current version worked fine on my devices and passed Apple’s testing, and the current version continues to work for my main computer when downloaded from the App Store. It’s very strange. I am able to replicate the issue on my secondary laptop. I hope to have a fixed version uploaded to the App Store as soon as possible. Thank you for your patience.