5.50c Crash with 32-bit Quilcom plugin (flowstone) easily reproducible

[functionform]

http://flowstoners.com/quilcom

Bear with me, these are all beautiful synths, but the easiest one to cause this issue is with the "ASS" (Analogue Synth Simulator) synth at the bottom.

After loading it into a project, toggling the Digital/Analogue switch at the top will cause Reaper to crash.

I have Windows 10, 16 gig, SoundBlaster, Reaper 64, 5.50c.

What I find remarkable is that Reaper is rock solid with absolutely every 32 bit synth I use and I use a lot- maybe 55% of my vst4free gems are 32 bit. This is why I believe it must be flowstone related as these Quilcom synths are all flowstone and SE seems to be more popular.

Logs:

Faulting application name: reaper_host32.exe, version: 0.0.0.0, time stamp: 0x59bc1300
Faulting module name: Quilcom ASS v1.051.dll, version: 0.0.0.0, time stamp: 0x55379c8d
Exception code: 0xc0000005
Fault offset: 0x0007ca3c
Faulting process id: 0x1d54
Faulting application start time: 0x01d3315927cb13dc
Faulting application path: C:\Program Files\REAPER (x64)\Plugins\reaper_host32.exe
Faulting module path: C:\Vst64\Quilcom\Quilcom ASS v 1.051\Quilcom ASS v1.051.dll
Report Id: fd5e948d-779e-499f-8578-6ab09499f3ef
Faulting package full name:
Faulting package-relative application ID:


Fault bucket 109150476576, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: reaper_host32.exe
P2: 0.0.0.0
P3: 59bc1300
P4: Quilcom ASS v1.051.dll
P5: 0.0.0.0
P6: 55379c8d
P7: c0000005
P8: 0007ca3c
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4 5DF.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4 63E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4 64C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4 65D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive \AppCrash_reaper_host32.ex_131f3f155a3052c9471575a 7664cc9d5cc171c9_017bb28b_1c2a7868

Analysis symbol:
Rechecking for solution: 0
Report Id: fd5e948d-779e-499f-8578-6ab09499f3ef
Report Status: 134217729
Hashed bucket: 4e80b124b1fe560a43d45280d329d42a

[ivansc]

Have you contacted the flowstone devs?

Also have you tried using 32 bit reaper to see if they behave any better in that? Could be as simple as aa 32/64 bit bridging issue.

And for what its worth the Synthedit stuff is even flakier in 64bit-anything for most people, myself included.

[functionform]

I have, no response from him yet. I will try again on flowstone forums. He says he does test with 64 bit Reaper as well.

[functionform]

No update on this from dev yet, but I did see his notes on hosting in Reaper.

http://flowstoners.com/about-plugins...with-flowstone

He says to use minimal undo states as these are complex plugins (not sure if the word complex has any special meaning there). Using this does seem to keep responsiveness of his plugins better, so far no crashes just yet, but will update thread if it occurs.

[Justin]

Originally Posted by functionform

No update on this from dev yet, but I did see his notes on hosting in Reaper.

http://flowstoners.com/about-plugins...with-flowstone

He says to use minimal undo states as these are complex plugins (not sure if the word complex has any special meaning there). Using this does seem to keep responsiveness of his plugins better, so far no crashes just yet, but will update thread if it occurs.

Based on this, I would avoid using these plug-ins (personally). If the plug-in can't save state efficiently, I avoid it (among other requirements). Again I emphasize this is a personal preference, obviously officially we do try to make REAPER work well with as many plug-ins as possible.