Lancaster ODR-1 sim crashes Cantabile (and everything else)

Related
1

Hi all!

I have just purchased the Lancaster ODR-1 pedal simulation.

The plugin is recognized and loaded in all the DAWs I usually use, including Cantabile (the others are Nembrini Nexus and Cakewalk by Bandlab).

When I open the plugin GUI, I am asked to activate it by entering the serial number (which I received via email). Well, I enter the SN and as soon as I click the “Activate” button the whole DAW crashes. This happens with all of the mentioned DAWs.

I have had a look at Cantabile’s log, but it seems that it is missing the final section (maybe it was not closed correctly).

I know there are a few guitar players here…have you ever used this plugin or heard about it? I have searched the net but I have not found anyone having the same problem (at least on windows…I have found a youtube comment saying that it does not work in Logic and that Lancaster does not answer emails…we will see, I have just written to them!). Any idea about how to debug the crash?

TIA for any hint,

Gabriel

P.S. The crash happens also if I enter random letters instead of the correct key. If I enter an empty string I get an “Invalid serial number” message but no crash.

2

Replying to myself just to insert here a stack trace of the crash, obtained using vsthost

Unhandled exception 0xC0000005 at 00007FFF393BFAC7 reading from 0000000000000018

CS:RIP=33:00007FFF393BFAC7 SS:RSP=2B:000000000014F580 RBP=000000000014F680
Flags=0000000000010206 MXCSR=0000000000001FA0
DS =000000000000002B ES =000000000000002B FS =0000000000000053 GS =000000000000002B
RAX=000000000014F700 RBX=0000000000000000 RCX=000000000014F5F8 RDX=0000000039BC89D8
RSI=0000000011A00190 RDI=00000000FFFFFFFF
R8 =000000000000003C R9 =0000000000000000 R10=0000000011D1E8F0 R11=0000000000000008
R12=000000000014F728 R13=000000000014F778 R14=0000000000000000 R15=0000000039606098
Stack Trace:
00007FFF393BFAC7 (ODR-1): (file?): (function?)
00007FFF393C2133 (ODR-1): (file?): (function?)
00007FFF3933391C (ODR-1): (file?): (function?)
00007FFF395009C1 (ODR-1): VSTPluginMain + 0xd41c1
00007FFF3932BD27 (ODR-1): (file?): (function?)
00007FFF3932B997 (ODR-1): (file?): (function?)
00007FFF6BAFE7E8 (USER32): CallWindowProcW + 0x3f8
00007FFF6BB3FFB4 (USER32): LoadMenuA + 0x124
00007FFF6BB405FB (USER32): CallWindowProcA + 0x1b
00000001401CA8D5 (vsthost): _AfxActivationWndProc + 0x16d
00007FFF6BAFE7E8 (USER32): CallWindowProcW + 0x3f8
00007FFF6BAFE229 (USER32): DispatchMessageW + 0x259
00000001401DBDEE (vsthost): AfxInternalPumpMessage + 0x52
00000001401DB8AB (vsthost): CWinThread::Run + 0x6f
000000014026F087 (vsthost): AfxWinMain + 0xab
000000014023B411 (vsthost): set_abort_behavior + 0x21d
00007FFF6A2F7614 (KERNEL32): BaseThreadInitThunk + 0x14
00007FFF6BF426A1 (ntdll): RtlUserThreadStart + 0x21

Maybe @brad could have a look at what’s happening. My hope is that if I get through the activation procedure, then the plugin will start working.

Gabriel