Access violation loading Retrologue.vst3

for all your technical questions

Return to “Technical Support (FL Studio & Plugins)”

Forum rules
IMPORTANT: Provide step-by-step DETAILS about your problem and how to reproduce it. A VIDEO is highly recommended (get a free recorder here - upload .swf format videos direct to the forum). Bugs will be fixed much faster if you follow these suggestions. NOTE: Technical Support is ONLY available Monday - Friday (9 am to 11 pm CET), thank you.
[You can only see part of this thread as you are not logged in to the forums]
Horizon-F
Sun Jul 09, 2017 8:58 pm

0 x

Re: Access violation loading Retrologue.vst3

reflex wrote:
Horizon-F wrote:
reflex wrote:Does it work in FL 32bit btw?

I tested it a few times, here are the results:

1st time: No crashes.
2nd time: One instance of Retrologue failed to open ("Failed to send settings to plugin Retrologue" or something along those lines)
3rd time: No crashes.
4th time: No crashes :o
5th time: No crashes :shock:

This is actually quite interesting. It seems that the project opens much better in the 32 bit version.


Is the plugin bridged at any time?

What happens if you bridge it manually?


The project I use to test this issue has all 64 bit native Retrologues, it seems. Those crash too.
However, some of them are VST2 and some are VST 3.5.1.
One instance that is VST 3 resets it's channel name in an odd way once the project loads. In the Channel Rack I've named the synth "Big Wave", but once the projects opens, it sets the name to "VST - User factory/factory/Big Wave". Big Wave is the name of the preset in Retrologue. This instance sometimes crashes, but most of the time works. But the renaming is a bit concerning.

And if by manually bridging you mean to load a 64bit version of Retrologue in FL32, it bridges just fine. I saved the project and opened it in FL12 32bit and FL12.5 beta [build 50] and FL12 64bit and the last one was the only one in which it crashed.



Return to “Technical Support (FL Studio & Plugins)”