2.0.3 won't load saved patches

Apologies for another “help me fix a bug?” post BUT:

I’m running Windows 10 and when I try to load up a a larger / more complex patch Rack crashes. Upon reinitializing Rack tells me:

Rack crashed during the last session, possibly due to a buggy module in your patch. Clear your patch and start over?

It ran this patch with no glitches for about 25 hours straight, so I think the problem must be in loading the saved file. I uninstalled and reinstalled Rack and the result was the same. I’m running the provisional Stoermelder use-at-your own-risk build, but Rack will open some patches with these modules and not others. How can I figure out what’s causing this?

I’ll paste in the log entries from the Windows Event Viewer below. If there’s a better error log, I’m interested in where I might find it. THANKS VERY MUCH to anyone who might be able to steer me in the right direction!!!

Faulting application name: Rack.exe, version:, time stamp: 0x00000000
Faulting module name: libRack.dll, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000000ab6d1
Faulting process id: 0x21ac
Faulting application start time: 0x01d7f43cc92b8068
Faulting application path: C:\Program Files\VCV\Rack2Free\Rack.exe
Faulting module path: C:\Program Files\VCV\Rack2Free\libRack.dll
Report Id: e5fee064-7996-4dc4-978f-ebbaafe96968
Faulting package full name: 
Faulting package-relative application ID: 


Fault bucket 1858926238247732760, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Rack.exe
P3: 00000000
P4: libRack.dll
P6: 00000000
P7: c0000005
P8: 00000000000ab6d1

Attached files:

These files may be available here:

Analysis symbol: 
Rechecking for solution: 0
Report Id: e5fee064-7996-4dc4-978f-ebbaafe96968
Report Status: 268435456
Hashed bucket: d70c2fd09d0b6879c9cc3b908e68c618
Cab Guid: 0

Vcv Rack writes a log file in the Rack2 folder in your documents folder

1 Like

In that case here’s everything in the log from the patch load on. this instance crashed:

[5064.752 info src/patch.cpp:249 load] Loading patch C:\Users\stran\Desktop\somerville\RACK\V2 FILES\how square.vcv
[5064.756 info src/patch.cpp:265 load] Unarchived patch in 0.001069 seconds
[5064.756 info src/patch.cpp:319 loadAutosave] Loading autosave C:/Users/stran/Documents/Rack2/autosave/patch.json
[5064.769 info src/rtaudio.cpp:51 RtAudioDevice] Creating RtAudio WASAPI context
[5064.772 info src/rtaudio.cpp:119 openStream] Opening RtAudio WASAPI device 0: Speakers (Scarlett 2i2 USB) (0 in, 2 out, 44100 sample rate, 512 block size)
[5064.778 info src/rtaudio.cpp:131 openStream] Starting RtAudio WASAPI device 0
[5064.778 info src/rtaudio.cpp:141 openStream] Opened RtAudio WASAPI device 0

…and upon re-opening, and receiving the same error message as above, the new log file included only one “warn” message:

[0.135 info src/plugin.cpp:120 loadPlugin] Loading plugin from C:/Users/stran/Documents/Rack2/plugins/Rack-SDK
[0.135 warn src/plugin.cpp:173 loadPlugin] Could not load plugin C:/Users/stran/Documents/Rack2/plugins/Rack-SDK: Manifest file C:/Users/stran/Documents/Rack2/plugins/Rack-SDK/plugin.json does not exist

Rack-SDK should not be in plugins

only .vcvplugin binary plugin distribution files - and the plugin dirs that Rack extracts from those.

1 Like

I deleted this folder and the stoermelder plugin folder and the patch loaded right up. Looks like this is a “wait for legitimate plugin release” problem

No need to give up, if you allready built plugins from source.

You just need to move the Rack-SDK out of the Rack plugins dir.

move Rack-SDK to C:/Users/stran/Documents/Rack2 for example - just avoid any dirs that Rack2 scans for content.

When you build plugins under Rack-SDK\plugins\%slugname%, make install copies the built .vcvplugin to Rack2\plugins

Done - this doesn’t seem to make a difference. With the Stoermelder-P1 plugin installed, Rack crashes upon loading a patch; without it, Rack loads the same patch, obviously without the Stoermelder-P1 modules

UPTADE. I found that Rack 2.0.3 will not open my recent, larger, Stoermelder-inclusive patches, BUT I can save the entire contents of a patch as a “selection” and they load right up, no problem :sunglasses:

1 Like

Haha. That’s awesome. Shades earned.

1 Like