I’ve left a note for Robert on github but haven’t got a reply yet.
It’s such a cool plugin. I miss it. 
I will be back in VCV land in a couple of months. For now priorities are somewhere else.
3 Likes
In the meanwhile I discovered the projectM-SDL viewer at projectM Music Visualizer by codav, available for Linux, MacOS, and Windows. It works nicely with a Mac Mini M1 here, though of course it’s not quite so nicely integrated as the Visualizer. But it’ll do in the interim.
I have been able to build all architectures using the latest toolchain and also have (at least during my tests) improved the resizing of the module. As I am not able to test on any Mac architecture, it would be great if some people can test and send me the results preferably in github. Or you can do here if you don’t want to create a github account.
You can get the latest versions from here: LowFatMilk - Google Drive
check thy github 
An issue was spotted and raised by @fractalgee that was in the module for a long time. So if you were testing, make sure you grab the latest version ( 2.1.12) from here LowFatMilk - Google Drive
1 Like
Getting occasional Rack crashes. new to testing so let me know what parts of the log , or where to find them ?
occasional crashes describes lot of rack modules Could be totally unrelated to visualizer. Of course look in the manual and find where the crash log is on your platform.
1 Like
That’s true…seems I can reproduce it when switching to a different mode of Prok hats 
It’s super tempting to assume it’s the “new” module. In my experience it’s usually some other module with an intermittent crash.
1 Like
I can reliably crash VCV with just the visualiser outputting onto a seperate display, and then maximising the visualiser …boom!
So based on what you are describing, I assume you are trying the Full version? Do you have issues with the embedded version too? And on what architecture are you running? Are you able to send me the output of the Rack log file after it crashed?
Hi Robert,
Yes the full version…the embedded seems to be working fine…
This is on the Arm64 build on a M1 Pro
[22.758 fatal adapters/standalone.cpp:49 fatalSignalHandler] Fatal signal 6. Stack trace: 28: Rack(fatalSignalHandler(int)+40) 27: libsystem_platform.dylib(_sigtramp+56) 26: libsystem_pthread.dylib(pthread_kill+288) 25: libsystem_c.dylib(abort+180) 24: libc++abi.dylib(__cxxabiv1::__aligned_malloc_with_fallback(unsigned long)+0) 23: libc++abi.dylib(demangling_terminate_handler()+348) 22: libobjc.A.dylib(_objc_terminate()+144) 21: libc++abi.dylib(std::__terminate(void (*)())+16) 20: libc++abi.dylib(__cxa_rethrow+148) 19: libobjc.A.dylib(objc_exception_rethrow+44) 18: AppKit(NSPerformVisuallyAtomicChange+144) 17: AppKit(-[NSWindow setStyleMask:]+176) 16: libRack.dylib(_glfwSetWindowDecoratedCocoa+100) 15: plugin.dylib(ProjectMRenderer::setNoFrames(bool)+120) 14: plugin.dylib(BaseProjectMWidget::step()+384) 13: libRack.dylib(rack::widget::Widget::step()+64) 12: libRack.dylib(rack::widget::Widget::step()+64) 11: libRack.dylib(rack::widget::Widget::step()+64) 10: libRack.dylib(rack::widget::Widget::step()+64) 9: libRack.dylib(rack::widget::Widget::step()+64) 8: libRack.dylib(rack::widget::Widget::step()+64) 7: libRack.dylib(rack::ui::ScrollWidget::step()+24) 6: libRack.dylib(rack::app::RackScrollWidget::step()+560) 5: libRack.dylib(rack::widget::Widget::step()+64) 4: libRack.dylib(rack::app::Scene::step()+340) 3: libRack.dylib(rack::window::Window::step()+1596) 2: libRack.dylib(rack::window::Window::run()+40) 1: Rack(main+3428) 0: dyld(start+2360)
The full version doesn’t crash until the moment I try and maximise, or resize, the window - this is happening with or without an external monitor
I have uploaded new versions 2.1.13 Can you see if this fixes anything? It looks like this is a specific Mac issue (and maybe arm, I don’t know yet as I need more information from mac users to test this). It would be great if both arm and non-arm mac users can this scenario as described by @user94 .
The full windowed version doesn’t crash until the moment I try and maximise, or resize, the window - this is happening with or without an external monitor
I can now resize it for a short amount of time before it crashes…maximising is an instant kapow
arm64 fullscreening the windowed version in LFM 2.1.13 crashes here with this backtrace:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1a259c744 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1a25d3c28 pthread_kill + 288
2 libsystem_c.dylib 0x1a24e1ae8 abort + 180
3 libc++abi.dylib 0x1a258cb84 abort_message + 132
4 libc++abi.dylib 0x1a257c3d0 demangling_terminate_handler() + 348
5 libobjc.A.dylib 0x1a2252e58 _objc_terminate() + 144
6 libc++abi.dylib 0x1a258bf48 std::__terminate(void (*)()) + 16
7 libc++abi.dylib 0x1a258ef44 __cxa_rethrow + 148
8 libobjc.A.dylib 0x1a22655cc objc_exception_rethrow + 44
9 AppKit 0x1a591b254 NSPerformVisuallyAtomicChange + 144
10 AppKit 0x1a591b0e4 -[NSWindow setStyleMask:] + 188
11 libRack.dylib 0x104eb8c5c _glfwSetWindowDecoratedCocoa + 100
12 plugin.dylib 0x11089f27c ProjectMRenderer::setNoFrames(bool) + 120
13 plugin.dylib 0x11089a3a0 BaseProjectMWidget::step() + 384
14 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
15 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
16 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
17 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
18 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
19 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
20 libRack.dylib 0x104de64c8 rack::ui::ScrollWidget::step() + 24
21 libRack.dylib 0x104da3278 rack::app::RackScrollWidget::step() + 560
22 libRack.dylib 0x104ded6e8 rack::widget::Widget::step() + 64
23 libRack.dylib 0x104dae0a0 rack::app::Scene::step() + 340
24 libRack.dylib 0x104df265c rack::window::Window::step() + 1596
25 libRack.dylib 0x104df2008 rack::window::Window::run() + 40
26 Rack 0x10430e7e0 main + 3428
27 dyld 0x1a227bf28 start + 2236
I think it is related to: Resizing on M1 has race crashes when main and draw are different threads · Issue #1997 · glfw/glfw · GitHub
I will have a look later today…
I have uploaded a changed version (version number is still the same). Can this please be tested on the mac again? I am curious if resizing crashed rack. I don’t expect the resizing to work, but just want to find out what exactly causes the crash.
sadly still crashes Rack on fullscreening the windowed one:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1a259c744 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1a25d3c28 pthread_kill + 288
2 libsystem_c.dylib 0x1a24e1ae8 abort + 180
3 libc++abi.dylib 0x1a258cb84 abort_message + 132
4 libc++abi.dylib 0x1a257c3d0 demangling_terminate_handler() + 348
5 libobjc.A.dylib 0x1a2252e58 _objc_terminate() + 144
6 libc++abi.dylib 0x1a258bf48 std::__terminate(void (*)()) + 16
7 libc++abi.dylib 0x1a258ef44 __cxa_rethrow + 148
8 libobjc.A.dylib 0x1a22655cc objc_exception_rethrow + 44
9 AppKit 0x1a591b254 NSPerformVisuallyAtomicChange + 144
10 AppKit 0x1a591b0e4 -[NSWindow setStyleMask:] + 188
11 libRack.dylib 0x100e4cc5c _glfwSetWindowDecoratedCocoa + 100
12 plugin.dylib 0x10c833318 ProjectMRenderer::setNoFrames(bool) + 120
13 plugin.dylib 0x10c82e43c BaseProjectMWidget::step() + 384
14 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
15 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
16 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
17 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
18 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
19 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
20 libRack.dylib 0x100d7a4c8 rack::ui::ScrollWidget::step() + 24
21 libRack.dylib 0x100d37278 rack::app::RackScrollWidget::step() + 560
22 libRack.dylib 0x100d816e8 rack::widget::Widget::step() + 64
23 libRack.dylib 0x100d420a0 rack::app::Scene::step() + 340
24 libRack.dylib 0x100d8665c rack::window::Window::step() + 1596
25 libRack.dylib 0x100d86008 rack::window::Window::run() + 40
26 Rack 0x1002a27e0 main + 3428
27 dyld 0x1a227bf28 start + 2236
Can you please see what the latest version is doing for you? It is on the same location and same version number.